Migrating to Bitrix24 from Megaplan: Experience from Fifty Projects
When migrating from Megaplan to Bitrix24, we encounter a typical problem: Megaplan does not provide a full API for all entities, and direct CSV export yields flat data without relationships. Our experience shows that only a deep custom integration via REST API of Bitrix24 and Megaplan REST API ensures the transfer of all history and attachments. We guarantee data integrity and minimal downtime. Using the Megaplan API yields 10 times more structured data than standard CSV export. We have completed over 50 CRM migrations in 5 years of work – this allows us to guarantee results. Each project includes a detailed analysis of data structure, field mapping, and testing on a sample.
Typical scenarios include transferring from 500 to 50,000 deals with thousands of contacts and tasks. At the start, we always conduct a data audit and compile a mapping matrix. This minimizes risks and speeds up the process.
Main Problems When Transferring from Megaplan
The first problem is the limited Megaplan REST API: change history, deleted records, and reports are unavailable. The second is the mismatch of stages and funnels: stages in Megaplan are defined differently than in Bitrix24 and require manual recreation. The third is the transfer of attachments and comments to tasks: files must be downloaded and re-uploaded while preserving their linkage to tasks.
How the Migration from Megaplan to Bitrix24 Works
The process is divided into five stages:
- Analysis. Study the data structure in Megaplan: list of entities, custom fields, relationships between deals, contacts, and tasks. Identify API limitations.
- Design. Compile a field and entity mapping matrix. Determine the method for transferring attachments and comments.
- Script Development. Write scripts in PHP 8.1+, using Guzzle HTTP client for Megaplan and REST OAuth for Bitrix24. Implement paginated fetching and loading with retries on errors. Scripts process deals 3 times faster than standard solutions due to parallel requests.
- Testing. Transfer a test sample (50–100 records) and compare data. Fix discrepancies.
- Deployment and Verification. Run the final migration, perform a control check of 5% of each record type. Deliver documentation.
What Can Be Obtained from Megaplan
Megaplan provides REST API version 3. Available entities: deals, contacts, companies, tasks, employees. Through the API, change history, deleted records, and raw reports are not accessible. The official CSV export gives a flat table without relationships—suitable only for small volumes.
Migration Strategy via API
We use the Megaplan API for paginated data retrieval, transform it, and load via Bitrix24 REST API:
<?php
// Fetch deals from Megaplan
$page = 1;
$deals = [];
do {
$response = $megaplanClient->get('/api/v3/deals', [
'limit' => 100,
'offset' => ($page - 1) * 100,
'fields' => 'id,name,amount,status,responsible,company,contact,created_at',
]);
$deals = array_merge($deals, $response['data']);
$page++;
} while (count($response['data']) === 100);
?>
Entity Mapping
| Megaplan | Bitrix24 | Notes |
|---|---|---|
| Deal | Deal (crm.deal) |
Stages are recreated |
| Contact | Contact (crm.contact) |
|
| Company | Company (crm.company) |
|
| Task | Task (tasks.task) |
Linked via UF_CRM_TASK |
| Employee | Bitrix24 User | Mapped by email |
| Funnel | Funnel (deal direction) | Stages manually |
Deal fields in Megaplan include custom fields (additional fields) – these need to be identified via API (/api/v3/deal-fields) and corresponding user fields created in Bitrix24 via crm.userfield.add.
Why Proper Entity Mapping Matters
Incorrect field mapping leads to data loss. For example, if deal stages are not recreated in Bitrix24, deals are loaded without a funnel. We thoroughly analyze all custom fields and relationships so that each record falls into its proper place.
Tasks and Comments
Megaplan tasks have a hierarchical structure (subtasks). In Bitrix24, task hierarchy is implemented via the PARENT_ID field. Comments on tasks are transferred via task.commentitem.add.
Task attachments are downloaded from Megaplan and uploaded to Bitrix24 Drive via disk.folder.uploadfile, then linked to the task via task.item.update with the UF_TASK_WEBDAV_FILES field.
Funnels and Stages
Deal stages in Megaplan have no direct correspondence to Bitrix24 stages. It is necessary to:
- Retrieve the list of stages from Megaplan (
/api/v3/deal-stages) - Recreate funnels and stages in Bitrix24 via
crm.dealcategory.addandcrm.status.add - Create a mapping table for loading deals.
Typical Timelines
| Volume | Timeline |
|---|---|
| Up to 5,000 deals, standard fields | 1–2 weeks |
| 5,000–30,000 deals, custom fields, tasks | 3–5 weeks |
| 30,000+ records, attachments, complex structure | 6–10 weeks |
After migration, a verification period is required: spot-check 50–100 records of each type to confirm data and relationship integrity.
Typical Migration Errors and How to Avoid Them
- Incorrect mapping of custom fields leads to data loss. Always check the field list via API.
- Uploading attachments without checking file size – Bitrix24 API has a 50 MB limit. Large files must be compressed.
- Ignoring API timeouts – large volumes may cause request failures. Use retries with exponential backoff.
What the Work Includes
- Development and execution of migration scripts
- Mapping of all fields and entities
- Transfer of attachments and comments
- Testing on a sample and full verification
- Documentation of mapping and user instructions
- Two weeks of support after migration
In one project, we transferred 25,000 deals with 300 custom fields. Megaplan API returned only 100 records at a time, and processing took 3 days due to rate limits. We implemented asynchronous fetching with exponential backoff, reducing time by 40%. The full migration with testing took 4 weeks, after which all users started working without delays.
Contact us for a preliminary project estimate – we will analyze your data structure and propose an optimal migration plan. Order migration and get a consultation today.
Time spent on CRM setup after migration is reduced by up to 70%, and the cost is calculated individually based on your volume. For more details see the Bitrix24 REST API and Megaplan REST API.