FAQ
- Why not use the Data Migration Manager (DMM)?
- Quite simply, it doesn't really work. You'll spend more time more time trying to get it to work than is reasonable.
- What if some record fail?
- The import can be an iterative process - if a record fails, it retained in a local database and the import can be re-tried. Problems can be fixed by editing the data, or by modifying the CRM implementation.
- Why do I get the error 'Generic SQL error.'?
- If you've extended the address fields for a customer or a lead and not made the address fields in 'Address' (CustomerAddress) at least as long then you'll get this error - Thanks to AFNA Crm for solving this.
- Does it work with Hosted or On-Premise implementations?
- Both - of course! Simply select which type the URL points to.
- Will it succesfully import attachments?
- Attachments are uploaded as part of the standard process - even to hosted implementations.
- What abount description fields that are more than 2000 characters in SalesForce?
- CRM has a maximum field size of 2000 characters, and this cannot be increased. To get around this, descriptions are converted into notes and attached to the entity. This can be done either for all items, or only for problem items.
- Will it map custom fields?
- Yes, custom fields and entites can be mapped. Fields are not automaticaly created. This was a conscious decision based on the fact that for a CRM implmentation to be a success the data should be considered rather than just shoved into the new system.
- Will it map custom entities?
- Yes, custom entities can be easliy mapped.
- What about relationships between custom entities?
- CRMMigrate uses the relationship defined in the destination Microsoft CRM system to determine how the data should be imported. This means that the custom entities are related to their parent objects automatically.
