Migrating data from Megaplan to Bitrix24

Data Migration from Megaplan to Bitrix24

Megaplan is a Russian CRM system focused on task and deal management. When moving to Bitrix24, companies often expect a "simple export", but Megaplan does not provide a complete API for extracting all data. Some entities are only available through the web interface or require a special request to support.

What Can Be Retrieved from Megaplan

Megaplan provides an API (REST, version 3.x). Main available entities:

• Deals (/api/v3/deals) — with fields, stages, and assignees
• Contacts (/api/v3/contacts) — individuals
• Companies (/api/v3/companies) — legal entities
• Tasks (/api/v3/tasks) — with comments and attachments
• Employees (/api/v3/employees) — for mapping assignees

What is unavailable through the API or restricted:

• Field change history
• Deleted records
• Raw reports
• Funnel configurations in detail

The official CSV export (via account settings) produces a flat table without relationships — suitable only for small volumes and simple structures.

Migration Strategy via API

Use the Megaplan API for paginated data retrieval, transform, and load via the Bitrix24 REST API:

// Retrieve 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

Deal fields in Megaplan include custom fields ("Additional fields") — these must be identified via the API (/api/v3/deal-fields) and corresponding user fields created in Bitrix24 via crm.userfield.add.

Tasks and Comments

Megaplan tasks have a hierarchical structure (subtasks). In Bitrix24, task hierarchy is implemented through the PARENT_ID field. Task comments are migrated via task.commentitem.add.

Attachments on tasks are downloaded from Megaplan and uploaded to Bitrix24 Drive via disk.folder.uploadfile, then linked to the task via task.item.update specifying UF_TASK_WEBDAV_FILES.

Funnels and Stages

Deal stages in Megaplan have no direct equivalent to Bitrix24 stages. Required steps:

1. Retrieve the list of Megaplan stages (/api/v3/deal-stages)
2. Recreate funnels and stages in Bitrix24 via crm.dealcategory.add and crm.status.add
3. Build a correspondence table for mapping during deal import

Typical Timelines

After migration, a verification period is required: spot-checking 50–100 records of each type to confirm the accuracy of data transfer and relationships.