What Gets Migrated and Where
The migration tool imports customers, deals, and activity history from Bitrix24 or amoCRM into Mavibot CRM.
To access it, go to CRM → Pipeline Settings (gear icon) → "CRM Migration" → "Open".
If your project doesn't have any pipelines yet, you'll see a "Migrate your data" link on the empty CRM screen.
| Data | Bitrix24 | amoCRM | Destination in Mavibot |
|---|---|---|---|
| Customers | Contacts | Contacts | CRM customers |
| Companies | Including company details and banking information | Including details from the "Legal Entity" field | Customer companies |
| Deals | All pipelines | All pipelines | Deals in selected pipelines |
| Closed deals | Optional | Optional | "Won" and "Lost" statuses |
| Leads | Optional, imported into a separate pipeline | amoCRM has no separate leads | "Leads (Bitrix24)" pipeline |
| Tasks | Activities and tasks | Tasks | CRM tasks |
| Comments | Timeline comments | Notes and SMS | Notes in customer conversations |
| Calls | Including recording links | Including recording links | Call records in customer conversations |
| Conversations | Open Channels, optionally including files | Not available: amoCRM does not provide conversations through its API | Customer conversations |
| Custom fields | Contact, deal, and lead fields | Contact and deal fields | Customer and deal variables |
| Assigned employees | Through employee mapping | Through employee mapping | Project team members |
| Tags | Contact type and source | Tags | Customer tags |
Before You Start
Only employees with permission to edit CRM data in Mavibot can start a migration.
In your previous CRM, the access credentials must be created by an administrator. The migration tool can only access data that the person who created the credentials is authorized to view.
- Your previous CRM remains unchanged. The migration tool only reads data. You can continue working in Bitrix24 or amoCRM as usual.
- No duplicate customers. If a customer with the same phone number or email address already exists in Mavibot (for example, someone who previously contacted you through WhatsApp), their existing profile will be updated. Only empty fields are filled in; existing values remain unchanged.
- No messages are sent to customers. CRM automations, bots, and campaigns are not triggered during migration. Imported customers are not moved to the top of the conversation list.
- You can safely run the migration again. Previously imported records are updated or skipped, and only new data is added.
Before starting, you must check the box confirming:
"The data belongs to our company, and we authorize Mavibot to migrate it."
The migration cannot start without this confirmation.
Migrating from Bitrix24
To connect Bitrix24, you need an incoming webhook. Creating one takes approximately two minutes.
Create the webhook using a Bitrix24 administrator account so the migration can access all deals and conversations.
- In Bitrix24, go to Developers → Other → Incoming Webhook.
- Select the permissions listed in the table below. Only CRM is strictly required, but without the other permissions, some data will not be imported.
- Click Save and copy the URL from the "Webhook to call REST API" field. It looks like this:
https://your-portal.bitrix24.ru/rest/1/xxxxxxxxxxxx/. - In Mavibot, open CRM Migration, select the Bitrix24 tab, and paste the URL into the "Incoming Webhook URL" field.
- Confirm that you own the data and click "Check Access and Discover Data". Then follow the migration wizard steps described below.
| Webhook Permission | What It Provides | Without It |
|---|---|---|
| CRM | Customers, companies, deals, leads, activities, comments | Migration cannot start |
| Users (Basic) | Employee list for mapping | Deals will have no assigned employees |
| Open Channels | Customer conversations | Conversations will not be imported |
| Tasks | Tasks from the Tasks module | Only CRM activities will be imported |
| Telephony | Call duration and recording links | Calls will have no duration or recording links |
| Drive | Files from conversations | Some files will remain as links in messages |
If any permission is missing, the wizard will display a warning during the "Data Found" step.
Add the required permission in your Bitrix24 webhook settings and click "Discover Again".
Bitrix24 allows no more than two requests per second, so collecting data from a large portal may take longer.
You can close the page while the migration runs in the background.
Connection Errors
| Error Message | What to Do |
|---|---|
| "This is not a webhook URL" | You entered a portal address or email. Copy the URL from the "Webhook to call REST API" field |
| "The webhook URL must start with https://" | Copy the complete URL, including https://
|
| "Bitrix24 rejected the webhook" | The webhook was deleted or the URL was copied incorrectly. Create a new webhook |
| "The webhook does not have CRM permission" | Enable the CRM permission in the webhook settings |
| "Bitrix24 is not responding" | Check the portal address in the webhook URL and try again |
| "Bitrix24 has not lifted the request rate limit" | The portal may be busy with other integrations. Try again later |
If the Developers section is missing from your Bitrix24 menu or you cannot save a webhook, check your Bitrix24 subscription plan.
Webhooks may not be available on the free Bitrix24 plan.
Migrating from amoCRM
To connect amoCRM, you need your account address and a long-term token from an external integration.
Only an account administrator can generate the token.
When creating the integration, amoCRM sends a verification code to the administrator's email address, so make sure you have access to that inbox.
- In amoCRM, open amoMarket → ⋯ (top-right corner) → Create Integration → External Integration → Create.
- Fill in the form:
- Redirect URL — any HTTPS address, such as your website. It is not used for the token.
- Grant Access — select "Access to Account Data". No other permissions are required.
- Name and description — for example, "Migration to Mavibot".
- Logo — any 400×272 image. Without a logo, amoCRM may not save the integration.
- Click Save. amoCRM will ask you to confirm the integration. Click Send Code, enter the six-digit code from the email, and click Confirm.
- Open the created integration and go to Keys and Access → Generate Long-Term Token. Select an expiration period. One month is usually enough for migration.
- Copy the token immediately. amoCRM displays it only once.
- In Mavibot, open CRM Migration and select the amoCRM tab. Enter
company.amocrm.ruor simplycompanyin the "Account Address" field. The addresscompany.amocrm.comis also supported. Paste your token into the "Long-Term Token" field. - Confirm that you own the data and click "Check Access and Discover Data". Then follow the wizard steps described below.
The account address and token are stored in encrypted form and deleted when the migration record is removed.
amoCRM does not provide access to conversations through its API. The migration wizard displays a warning about this before migration starts.
Connection Errors
| Error Message | What to Do |
|---|---|
| Verification code not received | The code is sent to the email associated with your amoCRM account. Check your Spam folder or create the integration using another administrator account |
| "The account address must be a domain such as company.amocrm.ru, not an email address" | Enter the domain shown in your browser's address bar when amoCRM is open |
| "amoCRM rejected the token" | The token was copied incorrectly, has expired, or was revoked. Generate a new one |
| "amoCRM subscription has expired" | Data may still be accessible for 30 days after expiration. Renew your subscription or contact amoCRM |
| "amoCRM has blocked access" | The integration may be missing the "Access to Account Data" permission, or the account may be temporarily blocked due to excessive requests. Check access and try again later |
| "amoCRM is not responding" or "amoCRM could not find…" | Check the account address and try again |
Migration Wizard Steps
After connecting your CRM, the migration process is the same for Bitrix24 and amoCRM.
No data is written to Mavibot until you reach the "Migrate" step.
1. Data Collection
The wizard retrieves data from your previous CRM and shows which section is currently being processed.
You can close the page while data collection continues in the background.
2. "Data Found"
The wizard displays the number of pipelines, deals, contacts, companies, tasks, calls, and employees found.
The "Things to Review" section shows which data cannot be migrated and why, such as missing webhook permissions.
3. Mapping
Configure how data from your previous CRM should be mapped to Mavibot.
Pipelines and Stages
For each source pipeline, select an existing Mavibot pipeline or choose "Create New Pipeline".
Stages with matching names are mapped automatically. Missing stages are created in the same order as in your previous CRM.
Employees
Employees with matching email addresses are mapped automatically and marked "Matched by Email".
For everyone else, select the appropriate employee or leave "Unassigned".
Fields to Variables
Select the custom fields you want to migrate and review their variable keys.
You can immediately use these variable keys in bots and campaigns.
What to Migrate
Configure the following options:
- Include closed deals.
- Import only data created after a specified date.
- For Bitrix24, optionally include unconverted leads, Open Channel conversations, and conversation files.
When a date filter is selected, all customers and companies are imported, while deals, tasks, comments, calls, and conversations are imported only from the specified date onward.
Click "Save Mapping" when finished.
4. "Review"
The wizard calculates what will happen during migration without writing any data.
For each data category, it displays:
- Will Create — records that will be added.
- Already Exists — records already found in Mavibot.
- Skipped — records that cannot be imported.
For customers, "Already Exists" means that a matching phone number or email address was found in Mavibot.
You can adjust the mapping and run the review again.
5. "Migrate"
The migration runs in the background, so you can close the page.
The Stop button interrupts the process.
Records already imported remain in Mavibot, and running the migration again continues without creating duplicates.
6. Migration Results
The final screen displays a table with:
- Created
- Already Exists
- Skipped
It also includes a list of skipped records with explanations.
To download the complete report, click "Download CSV Report".
To view the imported records, click "Open CRM".
Importing New Data Later
If your team continues working in the previous CRM, you can use "Migrate New Data" to import recent changes.
New records will be added, while previously imported deals will have their stages, amounts, and assigned employees updated.
The "Discover Again" button only refreshes the collected data, for example after adding new permissions to a webhook.
What Cannot Be Migrated
Any data that cannot be imported appears in the migration report along with the reason.
The following limitations are known in advance:
- amoCRM conversations. amoCRM does not provide conversation history through its API. Notes, SMS messages, and calls can still be imported.
- amoCRM files. Notes containing files are imported with the file name, but the actual files remain in amoCRM. Custom fields of the "File" type cannot be imported from either CRM.
- Custom company fields. Mavibot stores only the company name and company details.
- amoCRM system history. Stage changes and messages sent by automation robots are not imported.
- Converted Bitrix24 leads. The original lead is skipped, but the deal and contact created from that lead are imported.
- Records without a valid relationship. For example, a deal belonging to a deleted pipeline or a task linked to a deleted deal. Deals without contacts are not lost: they are linked to a company profile or a "No Contact" profile.
- Call recordings. Only links to recordings in the previous CRM are imported. These links may stop working after the old portal or account is disconnected.
Phone Numbers and Email Addresses
The first phone number and first email address are added to the customer's main profile fields.
Additional phone numbers, complete numbers with extensions, and values that do not match standard phone or email formats are saved in the "Phone Numbers" and "Email Addresses" variables.
After Migration
Imported deals appear in your Mavibot CRM pipelines.
Customer activity history is displayed in customer conversations, including notes, calls, and imported messages with their original dates.
Customer profile variables contain the "Bitrix24 ID" or "amoCRM ID", as well as additional information such as:
- Source
- Currency
- Closing date
- Lost deal reason
- Tags
At the bottom of the migration wizard, you'll find a "Migrations" list.
It displays the status of each migration and the number of customers and deals imported into Mavibot.
Disconnect Your Previous CRM
Once migration is complete, revoke access to your previous CRM.
Bitrix24
Delete the webhook in Developers → Integrations.
amoCRM
Go to amoMarket → Your Integration → Revoke Access.
Mavibot
You can click "Delete Migration" to remove the webhook URL or token and the collected migration data.
Imported customers and deals will remain in Mavibot.
Frequently Asked Questions
Can I run the migration again?
Yes. Use the "Migrate New Data" button.
No duplicate records will be created. Previously imported records will be updated, and new records will be added.
A customer has already contacted us through a messenger. Will a duplicate profile be created?
No.
Mavibot automatically finds existing customers with matching phone numbers or email addresses.
Their existing profiles are updated, and imported deals are linked to those profiles.
Why are some deals missing assigned employees?
The employee may not have been mapped, or the Bitrix24 webhook may not have the Users permission.
Add the employee to your Mavibot project, select them in the mapping settings, and click "Migrate New Data".
The assigned employee will be updated.
Where can I see which records were not imported?
Open the migration results and review the list of skipped records.
You can also download the CSV report.
Each skipped record includes an explanation.
Will CRM robots and campaigns run for imported deals?
No.
Migration runs silently. CRM automations, bots, and campaigns are not triggered, and customers do not receive any messages.
What if I migrated data to the wrong project? Can I undo it?
There is no automatic rollback.
Imported customers and deals remain in Mavibot even after you click "Delete Migration".
Before starting, make sure you have selected the correct project and carefully review the results in the "Review" step.