Migrating your database from amoCRM or Bitrix24
The main obstacle to changing CRM is not features — it is the data. "We have three years of history, we cannot abandon it" comes up in almost every conversation.
The concern is fair, but the problem is smaller than it looks.
First: can the data be exported at all?
Check this before choosing the new system, not before the migration. If a vendor will not let you take your data out, that is not a feature — it is a trap, and it costs more than any capability.
What transfers
| Data | Transfers | Note |
|---|---|---|
| Contacts | ✅ fully | |
| Companies | ✅ fully | |
| Deals / leads | ✅ fully | Stages are mapped |
| Comments | ✅ usually | With dates |
| Tasks | ⚠️ partly | Open ones |
| Chat history | ⚠️ partly | API dependent |
| Call recordings | ❌ usually not | They stay in the PBX |
| Funnel settings, automations | ❌ | Rebuilt by hand |
Call recordings usually live in the PBX, not the CRM — so changing CRM does not lose them. Connect the new CRM to the same PBX.
Clean the data first
Old databases carry duplicates, phone numbers in inconsistent formats, long-closed deals and test records. Phone format matters most: a system sees +998901234567 and 998901234567 as two different people, which is exactly why duplicates never merge.
The order
- Full export, keep a separate copy
- Map old stages to new ones
- Test migration with 50–100 records
- Full migration, out of hours
- Two weeks running both systems — do not switch the old one off
- Only then cancel the old subscription
Step five is the one people skip, and it is the one that saves the most trouble.
In AsproCRM
We handle the migration — a one-time service, free with an annual Pro or Ultimate plan. Pricing: 190 000 / 590 000 / 1 290 000 UZS per month.