Solutions4sf I build CRMs, and fix the ones that broke

Sales Cloud · required fields that do not break saves

You made a field required.
Now old deals will not save and the integration fails.

A field required at field level blocks every save that leaves it empty, including an edit to an old record and a write from an integration. Require it by stage with a validation rule instead, and on lead conversion with a rule that fires only as the lead converts, so the field is asked for when it matters. Below are the three levels and what each breaks, the setting conversion rules depend on, what conversion drops, and the build for an industrial services group, a holding and its operating companies.

Salesforce Help read on 16 November 2026. Reviewed 16 November 2026.

The cause

Why do old records stop saving after a field is made required?

Because a field required at field level is checked on every save, however the record is saved. An old deal with that field empty fails the next time anyone edits it, and so does every integration or import that does not send the field. Salesforce calls it the most restrictive of the ways to require a field.

The three levels and where each one is enforced are in Salesforce Help, How to Make a Custom Field Required in Salesforce. The table puts them side by side with what each one breaks.

Three ways to require a field in Salesforce and what each breaks: required on the field itself is enforced on every save, the screen, the API and imports, and breaks old records on their next edit; required on the page layout is enforced only on that page in the browser, so imports and integrations arrive without the value; a validation rule is enforced on every save whenever its condition is true and breaks only what the condition matches, which is how a field is required by stage. On conversion, a rule on ISCHANGED(IsConverted) runs only with Require Validation for Converted Leads switched on.
Three levels, three different failures. Only a validation rule can ask for a field at the stage, or the conversion, where it matters.

By stage

How do you require a field only from one opportunity stage onwards?

With one validation rule per field: the field is blank and the deal is at a stage where it is needed. One rule per field, not one per stage, so the error names exactly the field that is missing. Add a check that the stage has just changed if old deals already past that stage must stay editable.

A stage can only ask for a field if every seller reads the stage the same way. Shared stage definitions are the first of the eight checks in the Sales Cloud audit.

The rule below asks for a bid due date at every open stage after Engagement, so a deal can still be closed, won or lost, without one. The field name is an example. The last line is the choice that decides how many people complain on Monday: keep it, and an old deal stays editable until someone moves its stage; drop it, and every open deal past Engagement must be completed on its next edit.

AND( ISBLANK(Bid_Due_Date__c), NOT(IsClosed), NOT(ISPICKVAL(StageName, "New")), NOT(ISPICKVAL(StageName, "Engagement")), OR(ISNEW(), ISCHANGED(StageName)) )

Before switching a rule like this on, count the deals it would catch. Run this in the Developer Console query editor with your own field and stages; the number is how many deals stop saving on their next edit if you drop the last line.

SELECT COUNT() FROM Opportunity WHERE IsClosed = false AND StageName NOT IN ('New', 'Engagement') AND Bid_Due_Date__c = null

On conversion

How do you require fields only when a lead is converted?

With a validation rule on the lead that fires when IsConverted changes and the field is empty, and with Require Validation for Converted Leads switched on in Lead Settings. Without that setting the rule does not run during conversion. The lead can then be saved half empty while it is worked, and cannot become a deal half empty.

AND( ISCHANGED(IsConverted), ISBLANK(Bid_Due_Date__c) )

The dependency is stated in a Salesforce knowledge article, Validation rule not firing when converting Leads: to enforce a validation rule on conversion, Require Validation for Converted Leads has to be on. In Lightning Experience it is under Setup, Feature Settings, Marketing, Lead Settings. If the box is not there, the article sends you to Salesforce Support to enable Use Apex Lead Convert.

What conversion drops

A required field is no use if conversion loses it.

Salesforce Help, Considerations for Converting Leads, says standard lead fields map to standard account, contact and opportunity fields automatically, and custom lead fields go only where an administrator maps them, to custom fields. Anything not mapped stays behind on the converted lead, which nobody opens again.

The standard part has a trap of its own. The Lead Conversion Field Mapping table sends the lead’s Description to the contact’s Description and nowhere else. Where the lead becomes a deal, the notes a seller typed during qualification never reach the opportunity.

The guidelines for mapping custom lead fields add two facts that matter for planning: several field types map only to a custom field of the same type, and the mapping can be managed through the Metadata API or Salesforce CLI. The same page warns that the mapping screen can stop responding above 2,000 lead, account, contact and opportunity fields in total.

One build, from the inside

Required at the right moment, for an industrial services group.

An industrial services group, a holding and its operating companies, restarting Salesforce, where a lead is a tender rather than a person and the sales standard is a written document. Every rule below is declarative. The create screen that replaced the standard lead form, and why Salesforce insists on a company and a surname, are in the second Salesforce implementation case study.

  1. 01

    Nothing required at field level

    The first decision. The org already held records, more were due from the previous CRM, and an accounting integration was planned for a later phase. A field level requirement would have frozen old records on their next edit and failed any load that lacked the value, so every requirement went into a condition instead.

  2. 02

    One validation rule per field, keyed to the stage

    Eight stages, from New to four ways of closing. The bid due date and the products are required before a proposal is prepared, and a closed deal needs a reason from a list that depends on how it closed. Each rule checks one field, so the message tells the seller exactly what to fill in.

  3. 03

    Red asterisks, with the price said first

    Later the client asked for the asterisks as well, so people could see what was coming. Before the change the consequence was put in writing: some older deals would not save from the screen until someone completed them. They accepted it, and it went in knowing that.

  4. 04

    Conversion as a gate

    Active rules on the lead fire on ISCHANGED(IsConverted): no conversion without the bid due date, the company of the group and the service. A further rule, on country and registration number, stays switched off. Requiring country on the field would have stopped older leads without one from saving at all.

  5. 05

    The mapping counted before it was built

    Most of the lead fields that had to survive conversion had nowhere to go on the deal. Matching fields were added and mapped to the opportunity, and to the account where the value described the company. Notes moved to a custom field, because the standard Description would have landed on the contact.

  6. 06

    Proved by converting a lead, not by reading the screen

    The mapping was first noted as something only Setup could change. It turned out to be metadata, so it was retrieved and deployed with the fields it maps. It was accepted when a real lead was converted and every value was read back from the new deal.

Conversion is one of seven places a lead can stop moving; the other six are in lead management architecture. And a requirement is a cost to the person typing, so every field asked for should be used in a report or a decision, which is the argument of why a sales team will not use Salesforce.

Asked often enough to answer here

Questions

  • Q

    Does a field required on the page layout apply to imports and integrations?

    No. Salesforce documents that a page layout requirement applies only when the record is edited in the user interface, and updates through the API skip it. Records from an import or an integration arrive without the value. If a machine must send it too, use a validation rule.

  • Q

    Why does my validation rule not run when a lead converts?

    Because Require Validation for Converted Leads is off. Salesforce Help says the setting must be enabled for a validation rule to be enforced on conversion; it sits in Setup under Lead Settings. If the option is missing, Salesforce Support enables Use Apex Lead Convert first.

  • Q

    Can the lead Description be mapped to the opportunity?

    Not directly. Standard lead fields map to standard fields automatically, and the mapping table sends Description to the contact only. Custom lead fields can be mapped to custom fields of a matching type, so a custom notes field on both objects carries the text to the deal.

  • Q

    Should the integration user be exempt from the rule?

    Only if someone owns the gap. A condition on the running user can exempt an integration, and its records then arrive without the field, exactly as with a page layout. Decide per field which source must send it, and test the integration against the rule before it goes live.

The base package covers stages with exit criteria and lead and opportunity conversion, up to 25 seats. Which field each stage asks for is written down and agreed before the first rule is built.

Serhii Skrypnyk · Senior Salesforce Administrator · 7 Salesforce certifications · on the platform since 2018. Reviewed 16 November 2026.

Read next

  1. 01

    Case: Group of companies, second rollout

    A holding and its operating companies came back to Salesforce after a first rollout stalled: tenders as leads, one customer record in either alphabet, access proved as the users.

  2. 02

    Salesforce Lead Management: Seven Layers

    Seven layers where leads are lost between a form and a closed deal, what breaks in each, and why fixing the scoring model does not fix the handoff to sales.

  3. 03

    Sales Cloud Audit: Eight Checks, €650 Day

    A Sales Cloud audit in eight checks your admin can run, or a €650 data quality check in one day against your exports, €4,875 to fix all eight.