2 posts / 0 new
Last post
What are the Limitations of the import utility in MSCRM
Total votes: 2218

The file size is limited to 8 MB (but can be increased)

 Owner and lookup mapping is limited to single value matching. If your source has

the full name of the owner in lastname, firstname format, and your target

environment has fullname in firstname lastname format, you will have to either

modify your source file to include the format found in the target environment or

have some alternative matching field in your source that exists on target records.

 The import utility can update existing records when importing a file that was

exported from the same environment with the “for re-import” checkbox checked. If

you are importing a file from another environment into your CRM organization, the

import utility will not update existing record.

 The import utility cannot import N:N relationship data.

 When creating new records, you cannot set the record ID’s of the new records to

match the other environment. This is a problem when moving data used in your

configurations, like lookup table data. Given that you may have views and workflow

processes that reference specific record GUID’s (like the afore mentioned country

lookup), if you import the record, but it has a different ID than Canada has in the

source environment, when your workflow that checks to see if the country field

equals Canada runs, it will not apply to the imported records, because the ID will be


 The import utility does not handle status reasons well. It will match on status reason

name, but you will have a problem if you use specific status reasons or have status

reasons with the same name for both Active and Inactive statuses. So say you have

a Status Reason value of “On Hold” that exists as an option for both active and

inactive records. When you match the option set values, the import utility won’t

know which to pick, and you will have to select the value in the mapping. The

problem will happen when it tries to import those records, as when it creates the

records as active; it may try to set the value of Status Reason to the Inactive version

of the status reason. This will cause a failure, because the specified status reason

will be invalid for the Active status.

You voted 3. Total votes: 2307