The Data Import Wizard uses page layouts and field-level security to determine the fields available on import.
In order for a field to be visible within the Data Import Wizard, it must be available to the user within the associated page layout and field-level security. This applies to end users as well as users with a System Administrator profile
If Users report that fields are no longer available for mapping in the Data Import Wizard, ensure that the affected user has access to the missing fields.
Field Access: Confirm the affected user has access to the missing fields.
Profile and Record Type: Ensure the user's profile has at least one assigned record type, and the corresponding page layout includes the missing fields.
Field-Level Security: If the fields are on the page layout, double-check the user's profile's field-level security settings. Verify they have access to the field. You can review field access by field, profile, or record type in Setup by searching for "Field Accessibility."
Regarding custom Master-Detail and Lookup relationships: They're fundamentally similar, except Master-Detail fields are always required, while Lookups are optional. The screenshot below shows a custom object import with a custom lookup field. During import, Standard lookups can be matched using either the Salesforce record ID or the record name. We need to ensure this same flexibility (matching by ID or name) is available for our custom lookup fields as well.
Import Data with the Data Import Wizard
Trailblazer Community: Custom Fields not available in data import wizard
Trailblazer Community: Fields not available for mapping when you use the Data Import Wizard
Trailblazer Community: Data Import Field - Map your field
Verify Access for a Particular Field
How is record type access specified?
Can I import into fields that are not on my page layout?
Field Mapping for Importing Leads
004333175

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.