I have a CSV file with 20,000 rows and 300+ columns. It will not import into MS CRM. It never gets past the first screen that says something like "uploading file..." Any ideas?
Joe
*This post is locked for comments
Joe,
It is probably too large. You will need to break it down in to several smaller files.
http://rc.crm.dynamics.com/rc/2011/en-us/online/5.0/Help/source_imp_preparefile.htm
By default, the maximum size of the files that you can import is 8 megabytes (MB). This means: •Any .csv, .txt, or .xml file must not exceed 8 MB in size. •The total size of the .zip file with the attachment folder cannot exceed 32 MB.The total size of the extracted files must not exceed 200 MB.
Jerry, Microsoft Dynamics CRM MVPCRM InnovationNeed a solution for CRM to help you manage Events or Email Marketing?Follow me on TwitterIf this post answers your question, please click "Mark As Answer" on the post and "Mark as Helpful"
Have you tried importing it as a Zipped file?
I'm new to this. I have not tried it as a zip. I'll give it a try. Thanks.
Here is a really good video that will teach you how to do it step by step:
Well, zip didn't work. I got an error saying that the containing file was too large. So I broke up the file into 4 meg pieces. Those don't import either. I get an generic error say that there was problem. I can, however, import 50 records at a time. I have 20k accountst and 150k contacts to import. Is there a third party data loader out there what works better than this?
I don't think the amount of records matter too much, last week we imported over 500,000 records as part of a SalesForce convertion without any issues.
If you split the document in pieces and then import as Zip, it should work.
please refer to this kb article and change your system settings:
support.microsoft.com/.../en-us
After hours of banging my head in the wall I discovered the real problem. Yes, my initial file was over 8 megs. After splitting I was still not getting successful imports. The error was different and it told me nothing. The problem turned out to be that there were special characters embedded in the export from Salesforce. HEX 0E, and HEX 19. Indeed, after I found the records using a HEX editor in the CSV file I found the corresponding records in Salesforce. I could see the goofy characters in the strings in question. I fixed them in SF so this wouldn't happen again. Thanks everyone for your replies.
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.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
HR-09070029-0 2
UllrSki 2
ED-30091530-0 1