Import FAQs 
 
1. What to do when you get an Invalid error in the ort file? 
 
This error mostly comes up when you’re importing contacts and accounts together and if you’ve mapped a account field in the sheet to a contact field inside CRM and the vice-versa. Make sure you’ve mapped all the fields properly and the issue error should be resolved. 

2. What to do when you get “Invalid date format” during import? 
 
Please note that the below are the supported Date formats during import: 
 
A screenshot of a computer

AI-generated content may be incorrect. 

So please make sure you follow the same if you have any Date values in the import file. If that is done properly, then ensure that you choose the right format option at the time on import. If all of it is done right and if you’re still getting the same error, please check if you have entered a valid date. If the issue persists, please raise L2. 
 

3.What to do when the Import progress tab is stuck? 
 
Usually this can happen if the imported is Queued in the backend. We can check the logs and raise an L2 to unblock the Queue post which the issue should be resolved.  

4. What to do when while mapping the fields you get different characters in the field value preview which is not present in the file?  
 
This can mean your file is corrupted. You can import this import file in Google Sheets, remove all the empty columns, select all the records and click on Format – Clear formatting. Once done, export that file and you should be able to import it without any hassle. 

5. What to do when the import file size exceeds 5 MB? 
 
The only way to overcome this situation is to split the file into two csv’s and perform import twice. The current behavior supports only import files less than 5 MB. 

6. How to import linkedin profile? 

Please note that While adding LinkedIn profile of a contact, enter only the profile name instead of adding the entire URL. For example, if the contact's LinkedIn URL is https://www.linkedin.com/john-doe, enter only john-doe. 
 

7. How to import the owner details for a record during import? 

While mapping a contact/account to the Sales Owner, ensure that the CSV file has the email address of the sales owner in the column 'Sales owner' and NOT the name of sales owner. Adding the name will not map the sales owner to the record.  

8. How to import value to a lookup field? 
 
While entering the values into a lookup field which is present in the import file, you must use the record ID and note the name of the record. For example, related account is a lookup field in contacts module. To associate an existing account to a contact during import you must use the record ID of the account and not the account name. To fetch the record ID you can navigate to that account – expand the account and you’ll find the ID in the URL: 
 
 
 
Alternatively, you can perform an export and find the associated record ID for the same. 

 

9. What does “Too many requests” mean in the import error file? 

 
This usually comes up when the API limit is consumed in the backend for MCR sync. Please note that this API limit has no relevance to the accounts API limit. Please try to re-import and in the new error file you’ll be able to see the actual reasons.