web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested Answer

Unable to map Company Name and custom Contact field during CSV import in Dynamics 365 Sales

(0) ShareShare
ReportReport
Posted on by

Hi everyone,

I’m new to Dynamics 365 Sales and currently migrating data from a third-party CRM.

Here’s what I’ve done so far:

  • Exported data from the existing CRM to CSV

  • Cleaned and validated the CSV

  • Created a custom field on the Contact table in Dynamics 365

  • Confirmed that both Company Name and the custom field:

    • Exist on the Contact form

    • Are published

    • Are marked as Business Required

Issue:
When I import the CSV and reach the field mapping step, I’m unable to find:

  • Company Name

  • My custom custom field

These fields do not appear in the list of available fields for mapping, even though they clearly exist on the Contact table and are visible on the form.

What I’ve already checked:

  • Fields are added to the Contact form

  • Fields are published

  • Field-level security is not enabled

  • Fields are set to Business Required

  • Correct table (Contact) is selected during import

Questions:

  1. Why would Company Name and a custom Contact field not appear during CSV field mapping?

  2. Are there specific field types or settings that prevent fields from being available for import?

  3. Do I need to use a different import method (Data Import Wizard vs Power Platform Dataflows)?

  4. Is there a delay or additional publish step required after creating new fields?

Any guidance or best practices for CRM-to-Dynamics migration would be greatly appreciated.

Thanks in advance!

I have the same question (0)
  • Suggested answer
    Tom_Gioielli Profile Picture
    3,017 Super User 2026 Season 1 on at
    Sounds like an interesting issue. A few things about imports.
     
    1) The field does not need to be required or on a form to allow for importing, it simply needs to exist on the table.
    2) Fields with Column-Level-Security are also fine for import, provided you are logged in as a user with the proper permissions.
     
    You briefly mention dataflows in your post. Is that the primary way you are attempting to import the records? Dataflows are great for large number of records but can have a few quirks. If you are under 10,000 records you would be fine to use the classic import tool (it will be slower, but it also pretty dependable).
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
ManoVerse Profile Picture

ManoVerse 60 Super User 2026 Season 1

#2
Eugen Podkorytov Profile Picture

Eugen Podkorytov 49

#3
Tom_Gioielli Profile Picture

Tom_Gioielli 44 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans