There are two main scenarios when you may need to consider custom CRM data migration.
The first case of custom data migration into CRM is transferring a significant amount of file attachments. In this case, standard settings in amoCRM don't allow you to massively transfer files into the system. Our company uses third-party products that include cloud-based services like Google or Dropbox. We will locate all your files into the cloud and equivalently transfer them to each corresponding field in the system.
Transferring data with long activity history that includes call records and email messages will also require a custom CRM data migration. The implementation of data migration, in this case, depends on your old CRM. Our experts usually negotiate all specifics and requirements if any needed during the meeting before the implementation process.
Here are core steps for successful CRM data migrating: 1. Determine what data is needed to be transferred and the exporting method for this data.
In this stage, our experts learn more about your software, its type and version, the different systems may require different exporting methods, which will demand different amounts and types of data. 2. Create an amoCRM account.
The second vital stage in new CRM implementation is learning more about the software. You should become an expert in your CRM. For this reason, we recommend utilizing a free trial period
when you can define your sales funnels, create digital pipelines, and arrange statuses for each stage of the sales process.
A turning point for any business is developing entities and fields for its sales process, such as "Lead," "Customer," "Contact," and "Company." You can learn more about amoCRM entities here.
It is crucial to think over what data you would like to transfer and what entities and fields you will need: a common mistake for many businesses, from our experience, is when they try to store all their data about their sales in "Contact" or "Company" fields. amoCRM differentiates these entities and allows to locate different data under one "Lead." 3. Determine the data maps for migrating, which include corresponding entities and fields in amoCRM for each of your existing data (link to the description of the main fields in amoCRM).
It may happen that some of your data entities do not correspond to the standard fields of amoCRM. In this case, our experts will help you create additional custom fields, develop custom Add-ons or integrate third-party software into your CRM system. 4. Signing NDA (A non-disclosure agreement) agreement is recommended.
Please feel free to request a template of NDA agreement from us. 5. Estimate the cost and timing.
After all the steps of data migration defined we can make an accurate estimation for this process. In most cases, it's required to get access to both new and old systems for testing the technical capabilities and compatibilities of both systems for data migrating.
6. Data migration timing and its variations.
After all migrating terms determined, our developers will be ready to start extracting and importing data. Usually, it takes 1-2 business days. For data migration through the API or in other complex data connecting cases, the implementation of data migration may take 2-4 weeks.