---
schema_version: "1"
id: d93ae8f8adfcada44749fe127ad0c36c2a88988b68ecb657362b6b3586eb14b3
title: Migrate a Record Page to Dynamic Forms
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/dynamic_forms_migrate.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.dynamic_forms_migrate.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: d1533bc0a09588f60368a15d14d6d18ee55fd3a9aa044b1ff591d8ba511143dc
description: Some pages have Dynamic Forms enabled by default. For those that don't, you can migrate the fields and sections from your existing record pages as individual components in the Lightning App Builder. Then you can configure them the same way as the other components on the page, so that your users get only the fields and sections that they want. If you have save options on your account, case, or lead record pages, they are migrated.
products:
  - Salesforce Platform
  - Security
release: "264"
---
# Migrate a Record Page to Dynamic Forms

Some pages have Dynamic Forms enabled by default. For those that don't, you can migrate the fields and sections from your existing record pages as individual components in the Lightning App Builder. Then you can configure them the same way as the other components on the page, so that your users get only the fields and sections that they want. If you have save options on your account, case, or lead record pages, they are migrated.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
        <colgroup>
          <col>
        </colgroup>
        <tbody>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">Lightning App Builder available in: Salesforce Classic (not available in all
              orgs) and Lightning Experience</td>

          </tr>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">Lightning pages and Dynamic Forms available in: Lightning Experience and the
              Salesforce mobile app</td>

          </tr>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">
              <p style="margin-bottom:0;">Available in: <strong>Group</strong>
                <strong>Essentials</strong>, <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>,
                <strong>Unlimited</strong>, and <strong>Developer</strong> Editions
              </p>
            </td>

          </tr>
        </tbody>
      </table> <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d144663e91">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d144663e91 ">To create and save Lightning pages in the Lightning App Builder:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d144663e91 ">Customize Application</td>

          </tr>
        </tbody>
      </table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/images/icon_note.png)

Note Dynamic Forms (desktop and mobile) is supported for most but not all standard LWC-enabled objects. For a list of LWC-enabled objects, see [LWC Migration for Record Home Pages](https://developer.salesforce.com/docs/component-library/documentation/en/lwc/migrate_lwc). If you open a record page for an object in the Lightning App Builder and don't see a Fields tab in the component panel, then Dynamic Forms isn't supported for that object. As an example, the Note object doesn’t support Dynamic Forms because it has a fixed layout. Dynamic Forms isn’t supported on objects that aren’t LWC-enabled. For example, Products, Events, and Tasks, which aren’t LWC-enabled, use information from the object page layout.

1. Open a Dynamic Forms-supported object record page for Lightning Experience in one of these ways.
    1. From the Setup menu on a record page, select **Edit Page**.
        
        ![Edit Page](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/extend_click/images/lex_lab_edit_page.png)
        
        When you select **Edit Page** for the first time, Salesforce makes a copy of the standard page. You edit this copy in the Lightning App Builder. If a customized page exists and is active, selecting Edit Page opens that page to edit.
    2. From the Object Manager in Setup, open a Dynamic Forms-supported object, then select **Lightning Record Pages**.
    3. Open a record page for a Dynamic Forms-supported object from the Lightning App Builder list page in Setup. To find it, enter App Builder in the Quick Find box, and then select **Lightning App Builder**.
2. Click the Record Detail component.
3. In the component detail pane, click **Upgrade Now** to start the Dynamic Forms migration wizard.
    
    ![Record Detail Upgrade Now button](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/extend_click/images/dynamic_forms_upgradenow_properties.png)
4. Walk through the wizard and select the page layout that has the fields that you want to migrate to the page.
    
    Why select a page layout when the Fields tab has all the fields that you need? The upgrade wizard takes the fields, sections, and save options from the page layout that you choose and automatically adds them to your page. As long as a field is inside a Field Section component, you can put it anywhere on the page, even inside tabs.

During migration, the Record Detail component is removed from the page and is replaced with fields and sections that you can configure and place anywhere you like.

![Adding a field to a Field Section component](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-extend_click-264-0-0-production-enus/5f7d9219-b7b1-4552-8891-f1aba9b289fc/extend_click/images/dynamic_forms_add_field.png)

If you haven't opted in to Dynamic Forms on Mobile, and your record page supports the Phone form factor, a Record Detail - Mobile component is added to your page as part of the migration. This component is unique to Dynamic Forms. It shows the standard record detail fields and sections to your users when they view the page on a mobile device.

If you have opted in to Dynamic Forms on Mobile, the Record Detail - Mobile component isn’t added to pages you migrate to Dynamic Forms. The Dynamic Forms content is visible on mobile without the need of the Record Detail - Mobile component.

#### See Also

- [Dynamic Forms and Mobile Using the Record Detail - Mobile Component](https://help.salesforce.com/s/articleView?id=platform.dynamic_forms_mobile.htm&release=264.0.0&type=5 "The Dynamic Forms Field Section component and the Field components that go inside were previously only available on desktop. To support mobile users, the Record Detail - Mobile component gives your mobile users a way to see the record details on their mobile devices on a Dynamic Forms-enabled page.")
- [Break Up Your Record Details with Dynamic Forms](https://help.salesforce.com/s/articleView?id=platform.dynamic_forms_overview.htm&release=264.0.0&type=5 "The more fields that there are on your page layout, the more that the Record Detail component becomes a monolithic block of fields that you can’t customize. With Dynamic Forms, you can migrate the fields and sections from your page layout to individual components in Lightning App Builder. Then you can configure them the same way as the other components on the page - spreading them out across multiple columns and tabs, and dynamically showing and hiding them based on record data, user details, and device type, so that your users get only the fields and sections that they want.")