RetailCRM to Bitrix24 Migration: Preserving Orders and Loyalty
When migrating from RetailCRM to Bitrix24, the main challenge is the different data model: RetailCRM centers on orders, while Bitrix24 centers on deals. Without careful mapping, you lose statuses, payment history, and customer data. We've seen projects where 30% of deals ended up in wrong stages due to incorrect status mapping, and loyalty history was completely lost. Our team has completed over 50 migrations in 6 years, and we know how to avoid these pitfalls. We use RetailCRM API v5 for extraction and Bitrix24 REST API for writing. For large volumes we parallelize requests with a 5 RPS throttle, processing up to 50,000 orders per day. Our automated pipeline makes migration three times faster than manual Excel export.
Why Proper Mapping Is Fundamental
RetailCRM stores statuses in a multi-level structure with groups, while Bitrix24 uses flat deal stages. Without mapping, "Cancelled" can become "Won" and "In Progress" becomes "Lost". We automatically map statuses via a StatusMapper that respects business logic: e.g., "Return" in RetailCRM becomes "Deal lost" with reason preserved. In one project, 30% of deals were lost because the "Delivered" status wasn't transferred — after implementing the mapper, losses were eliminated.
What Data We Migrate
RetailCRM centers on Orders as the primary entity, while Bitrix24 is deal-oriented:
- Order — line items, status, delivery, payment
- Customer — individual or company
- Product — catalog item
- Task — internal tasks
- Note — comments on orders and customers
- Segment — marketing segments
- Loyalty — points, levels, history
All these entities we map to corresponding Bitrix24 objects. For example, orders become deals, customers become contacts, and loyalty becomes custom contact fields or the bonus points module.
Migration Process: Step by Step
- Data audit — export from RetailCRM, analyze structure and volume (1–3 days).
- Mapping design — field correspondences, status and business process decisions.
- Script development — PHP scripts using both APIs.
- Test migration — on a staging environment, verify checksums.
- Verification — compare totals: order counts per status, GMV.
- Production go-live — transfer to live, user training.
Migrating Orders with Status Preservation
RetailCRM's multi-level status structure maps to Bitrix24 deal stages. Our StatusMapper automatically matches statuses using business rules: e.g., "Cancelled" in RetailCRM becomes "Deal lost". Status change history is migrated to deal timeline events.
Handling the Loyalty Program
Loyalty data (points, levels, accrual history) goes to custom contact fields or the Bitrix24 bonus points module. We write a PHP script that recalculates balances as of migration time and loads operation history. If RetailCRM uses points expiry, we configure Bitrix24 agents for automatic write-offs.
Order Mapping Example
Mapping depends on whether the company uses a Bitrix online store:
- With store: orders may already be synced — we migrate only customers and history.
- Without store: orders become deals, customers become contacts and companies.
| RetailCRM | Bitrix24 (no store) | Bitrix24 (with store) |
|---|---|---|
| Customer | Contact / Company | Site user |
| Order | Deal | Order (b_sale_order) |
| Order Item | Deal line item | Basket item |
| Task | Task | Task |
| Note | Timeline comment | Comment |
| Segment | User group | CRM segment |
Typical Timelines and ROI
| Volume | Duration |
|---|---|
| Up to 10,000 orders, up to 5,000 customers | 2–3 weeks |
| 10,000–100,000 orders | 4–8 weeks |
| 100,000+ orders, loyalty, segments | 2–4 months |
Investment in migration pays back in 3–6 months through automation of routine operations. Cost is determined individually at the audit stage. Our certified specialists guarantee accurate mapping and data integrity.
What's Included in the Work
- Data audit — RetailCRM structure export, duplicate and anomaly analysis.
- Mapping design — detailed field correspondence scheme considering business processes.
- Script development — PHP scripts with API usage, custom logic possible.
- Test migration — on a staging environment, with checksum verification.
- User training — webinar or in-person session for new data usage.
- Documentation and source code — handed over to client.
- Post-migration support — 2 weeks of monitoring and bug fixes.
How to Avoid Migration Pitfalls
Use a test environment. Our engineers clone Bitrix24, rehearse scenarios there. Only after client approval do we transfer to production. We also write backward-compatible rollback scripts. We guarantee data integrity and 54-FZ compliance for fiscal data transfer. All source code and documentation are handed over.
Contact us for a preliminary audit — we will assess the volume and complexity for free. Get a consultation from a certified specialist.