What People Say
"I must say that it has been a pleasure working with you on this migration. I think you have done an excellent job! I know it’s a really complex data migration to do! I tried some before we got in contact with you, and it almost made me insane!"
Hans Linder – Cinteros AB Sweden
"It’s a easy to use solution for the migration. The contact was very nice and fast. Altogether it’s a perfect customizable solution for migrating from on premise to online hosted CRM"
Benjamin Dodl - DM Dokumenten Management GmbH - Germany
How Does It Work
Using a backup of your existing on-premise CRM database, Echo examines your exact configuration and using the Dynamics CRM SDK intuitively determines the your unique enitity relationships before starting the migration.
Echo nativley supports the migration of ALL custom entities and their relationships.
Supported CRM Entities
Echo currently supports the migration of the following CRM entities:
- BulkOperation (Quick Campaign)
There are some exceptions, mostly due to records being migrated as part of the Dynamics CRM 2011 Solution. There are a number of lower priority entities (such as user views and user settings) which we are working to include over the next few functional releases.
Echo makes every effort to be error tolerant, specically:
- Connection / systemic dropouts are automatically retried.
- The process can be stopped and started at any point and the migration is resumes from where it left off.
- Detailed error and progroess logs are provided for troubleshooting.
Because the migration can inherently take a long time, sometime several days, we have developed a 'delta' process to manage the migration of a live system over 2 weekends.
The following scenario illutrates how this process can be managed using Echo to provide a seemless switch over.
- A backup of the live CRM organisation databse is taken on the Friday
- The initial migration is started
- The initial migration completes after 4 days on the following Tuesday (this a very large database)
- On the Saturday a new backup of the live organisation is taken, the 'delta' script is applied to this database which identifies any records that have changed or been added in the intervening period.
- The delta migration is started.
- The delta migration completes, typically in a matter of a few hours as subset of changed data is likley to relatively small
- On Monday morning, users are directed to use the migrated system - everything should look the same...