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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Advice Needed: Large Data Imports looking for best practices

(0) ShareShare
ReportReport
Posted on by

Hi guys, like I mentioned earlier we are migrating from GM to dynamics and I want to make sure my initial imports are done correctly. So, I have a couple of scenarios I would like to bounce off you all to see if you can steer me in the right direction. Feel free to just answered via number.

1. Customers - Our export we got from GM combines "first name" and "last name" to create "contact". Should I create separate fields or leave them as is (contact) upon import?

2. Customers - We have a customer ID field that will serve as a unique ID for identify customers.  I am guessing we can search on this field to located records correctly. Is there anything I should do in addition? Suggestions/experience welcome?

3. Customers - We have a lot of different information pertaining to software and configuration for each customer. Would I be wise to push this info in along with the original data or do afterwards (40 fields)?

thx everyone.

*This post is locked for comments

I have the same question (0)
  • Royal King Profile Picture
    27,686 on at

    The order of import is very important

    1.Import customer data first with all the data points in one go. You can use unique number field to be customer number in crm to identify as well to link any related data like relating customer with contact.

    2.Split the first name last name then import the data into crm to have proper names displayed in the dynamics.

    if your data is in excel or csv it will be very easy to use excel to separate first name and last name from full name. 

  • Community Member Profile Picture
    on at

    Hi Chitra, can you clarify the order of the import for me? Are you suggesting I import just customer specific information first? then apply configuration information? Or should I do all of this with one import? I have 112 fields total. 40 of those are config. info.

    thx

  • Royal King Profile Picture
    27,686 on at

    I'm not sure how you want to store customer config data in dynamics. But if you plan to keep it within account entity then import all 112 fields in one go including config data. If you plan to keep it another entity then import customer data first then config data. where you can use customer unique number to link config data.

  • Community Member Profile Picture
    on at

    Ok I will give it a shot in the morning. thx

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 > 🔒一 Microsoft Dynamics CRM (Archived)

#1
JS-09031509-0 Profile Picture

JS-09031509-0 3

#2
AS-17030037-0 Profile Picture

AS-17030037-0 2

#2
Mark Eckert Profile Picture

Mark Eckert 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans