How to Change Record Type of Existing Records in Salesforce

By: Agustín Carranza | Published: May 1, 2026 | 6 min read
You can change the record type of an existing record in Salesforce from the record page, or in bulk by updating the RecordTypeId field with Data Loader. But be careful: behind the scenes, some problems may arise, including access issues related to record type permissions, picklist limitations, behavior of the Master record type, missing required fields, and conflicts with automation.

What Changing a Record Type Really Means

A record type in Salesforce controls:

  • Page layouts: You can create specific and custom layouts for each Record Type without altering the record itself.
  • Available picklist values: You can select which picklist values you want to have available for each Record Type.
  • Business processes: You can customize and streamline your business processes by creating Record Types that reflect your needs in different situations.

Changing a record type does not actually create a new record, and it does not delete or modify any existing data.

It’s important to remember that a Record Type is not the same as a “Type” picklist field.

If you want to change a picklist value labeled “Type,” simply edit the record; that does not require changing the record type.

Method 1: Change Record Type in Lightning (Single Record)

You have a couple of ways of changing the record type of an existing record in Lightning:
  • Click the “Change Record Type” link next to the Record Type field on the record page;

  • Click on the “Change Record Type” action on the top right action bar:

If the “Change Record Type” action is not visible, or the Record Type field is not visible on your record, you can add it from:
Setup → Object Manager → [Object] → Page Layouts → Edit Layout
And then:
  • Add the “[Object] Record Type” field under Fields:
    Salesforce Page Layout editor showing how to add the Record Type field to a layout from the Fields section.
  • Add the “Change Record Type” Action under Mobile & Lightning Actions:

Now, to make sure it was correctly added:

  • Refresh the record’s page;
  • Check if the action and/or field were added to the record’s layout;
  • Ensure the user has access to more than one record type.
It is not necessary to delete and recreate the record. Existing records can be reassigned if permissions allow it.

 

Method 2: Bulk Change Record Type

Changing the Record Type of existing records in bulk requires updating the RecordTypeId field on each record with Data Loader or similar apps.

Steps

  1. 1

    Find the target RecordTypeId.
    Setup → Object Manager → [Object] → Record Types → Click the record type → Copy:

    Salesforce Setup showing Record Type page with RecordTypeId highlighted in the URL for copying the ID.
  2. 2

    Export the Record Id’s for the records you want to change;

  3. 3

    Update those records using Data Loader.

Existing Records Using Master Record Type

If you create new Record Types for existing records, those will remain assigned to the Master record until updated manually via RecordTypeId.

Permissions Checklist

Assigning Record Types permissions controls which Record Types your users can create or change. But this will not restrict read access to the actual records, so users will still be able to view and edit the records assigned to that Record Type, considering that they have record-level access to the object and record.
If you want your users to use Record Types on your org, they must have:
  • Edit access to the object. Users will not be able to modify their records regardless of Record Type assignment, meaning that the “Change Record Type” option will not be available.
  • Record-level access. If not assigned, users will not be able to create new records with that Record Type.
  • Access to the target Record Type via profile or permission sets. Without this, users will not be able to create or edit Record Types since the option will not be available.
Remember that in Lightning Experience, field-level settings on the Record Type field may not fully prevent changes. If you need to block record type updates, use validation rules instead.

Why Record Type Changes Sometimes Fail

Most failures fall into these predictable categories:

Picklist mismatch: Values must exist in the master picklist and be enabled for the target record type. If you assign a Record Type with a restricted picklist to a record that has an existing value no longer permitted there, the operation will fail. Always check your picklist values in Object Manager before switching record types in bulk.

Required fields: A field that was optional in the previous Record Type layout may become required in the new one. If that field does not contain a value, Salesforce will prevent the record from being saved, and there will be no error message or warning.
Salesforce record edit page showing validation error and required fields blocking record type change attempt.

Validation rules and automation: Flows, validation rules, and triggers run when a record is saved and may block a record type change if their conditions are not met.

This example shows a validation rule that defines those conditions:

Salesforce validation rule detail page showing rule conditions that can block record updates.

When those conditions are not met, users will see an error and won’t be able to save the record:

Warning icon

Tip

Always review active automation before performing bulk updates.

Sharing rules: If criteria-based sharing depends on Record Type, changing the Record Type of a record may prevent access to it by users after the update, and you may not be able to identify this until someone indicates they no longer have access to that record.

Business vs Person Account:
Changing between Business and Person Account record types requires API tools and cannot be done from the standard Lightning UI. This should be tested and handled with care in a Sandbox first.

One-way change issue:
If changing from Record Type A to B works, but B to A does not, check Record Type assignments and layout settings. The “Change Record Type” action may not have been included on the record’s layout, or a user may not have access to it. It’s recommended to check both when this type of issue appears.
Warning icon

Tip

Before bulk changes, test on a small batch in a sandbox and review automation behavior.

When Spreadsheet-Based Updates Are Safer

Using a CSV tool to update and bulk update Record Types may be both safer and more streamlined than working directly with the Salesforce UI. But bear in mind that managing CSV files will often require performing extra steps, and can increase the chance of formatting errors.
A tool like XL-Connector will provide you with visibility into Picklist restrictions and required fields, and you can work directly on your Excel file, avoiding the hassle of exporting and managing CSV files. For example, if you are bulk updating records and have a mismatch on your picklist, or you are missing information on a field, this will help you locate and fix the issue before pushing the changes; contrary to the UI method, where you will only see the error after the update fails.
If you want a step-by-step guide on updating existing records safely, you can check our article about Updating Existing Records in Salesforce.

Conclusion

Using the Salesforce UI is a reliable method for updating individual records, but managing larger datasets or needing advanced features makes an external tool like XL-Connector a significantly better option, especially for bulk updates where exporting the records and updating the RecordTypeId is required. Also, remember that most failures are caused by permission sets, picklist values, required fields, or automation steps – not by the record type itself; so always test before performing bulk updates.
|
Agustín Carranza

Agustín Carranza

Customer Support & Quality Assurance Specialist

About the Author

Agustín Carranza is a Customer Support and Quality Assurance Specialist at Xappex. With over 4 years of experience across customer service, technical support, backoffice operations, team leadership, and QA, he brings a well-rounded perspective to helping users solve real problems efficiently.

His background in Systems Engineering, combined with hands-on knowledge of programming, data analysis, MySQL, and Python, allows him to understand both the technical and human sides of support. He holds a Cambridge English certification, reflecting his commitment to clear and professional communication.

Agustín is dedicated to improving customer satisfaction and ensuring service excellence — values that guide both his support work and the content he creates for the Xappex blog.

flash-icon Xappex Blog

Explore More Insights & Stories