amoCRM to Bitrix24 migration
A 14-store apparel chain moved from amoCRM to Bitrix24 for end-to-end 1C integration and a unified product catalog. We moved 120,000 records in 2 days — with no duplicates and no broken links between entities.
The task
The client had run amoCRM for 4 years. By the time they reached out they had accumulated about 120,000 records: contacts, deals, companies, tasks, conversations. The decision to move to Bitrix24 came down to two factors: deep integration with 1C and a unified product catalog across the 14 stores.
The key requirement — do not lose the links. Every deal had to stay attached to its contact, company and conversation history. No duplicates.
The starting point
In amoCRM:
- ~45,000 contacts (with varying data completeness)
- ~30,000 companies
- ~38,000 deals across 5 pipelines
- ~7,000 tasks, ~3,000 calendar events
- Custom fields: 23 on contacts, 18 on deals
The typical third-party estimate for a migration like this — 2–3 weeks of work. Most of that would have gone into manual field mapping and duplicate handling.
What we did
We split preparation and migration into 2 phases.
Phase 1 — preparation (4 days):
- Export from amoCRM via the official API into an intermediate CSV layer
- Mapping of 41 custom fields to Bitrix24 user fields, signed off with the client
- Duplicate-merging algorithm: by normalized phone + email + tax ID where present
- Pre-creation of 5 pipelines and stages in Bitrix24
Phase 2 — the migration itself (2 days):
- Custom PHP script writing directly via the Bitrix24 REST API, in batches of 50
- Import in order: companies → contacts → deals → tasks → events (so links never broke)
- In parallel — export of conversation history into comments on the corresponding entities
- Control reconciliation of checksums per entity type after import
The outcome
On Monday morning the managers opened Bitrix24 and saw their deals at the familiar stages. Contacts — all of them. Duplicates — zero (merging worked). Conversation history — in comments, fully searchable.
All 5 pipelines came across without losses, including a non-standard one for product returns after delivery. All 41 custom fields preserved.
On the third day the client asked us to connect telephony and 1C — those became separate engagements, but the Bitrix24 foundation was already in place.
The client's name is withheld under NDA. Real names and details are shared at the brief.
A similar task?
Describe it briefly — within 1–2 days we'll come back with an analysis and an hourly estimate. If a packaged solution fits, we'll say so honestly.