If your deals already live in a spreadsheet or another CRM, you do not have to enter them again by hand. WazzaBee CRM imports deals from an Excel or CSV file, from an amoCRM export and from a Bitrix24 migration file. Before importing, the CRM shows what the result will be, and only then adds the deals to the board.
Where to find the import
- Open “Settings”.
- Go to the “Data transfer” tab.
- The tab has cards: “Move from Bitrix24”, “Deals from Excel or CSV”, “Deals from amoCRM” and the client import.
Prepare the file
An export from another CRM or a manager’s own spreadsheet will do. Requirements:
| What | Requirement |
|---|---|
| Format | CSV, XLSX or XLS |
| Size | Up to 10 MB |
| First row | Column headers. Data starts from the second row |
| Required column | Client. Rows without a client name are skipped |
| Amount | Any format works: 1 250 000, $2,813, 1,250,000.50. An empty amount is not an error, the deal will have “No amount” |
| Created on | For example 12.03.2026, 2026-03-12 or 12/03/2026 14:30 |
Not sure how to lay out the table? On the “Deals from Excel or CSV” card, click “Download a sample”. The sample has the same columns the CRM expects and two example rows. The amoCRM card has its own sample with columns named as in an amoCRM export.
Importing from Excel or CSV: four steps
On the “Deals from Excel or CSV” card, click “Import deals”. The “Import deals from a file” window opens, and the top shows which step you are on.
Step 1. File
- Drag the file into the window, or click and pick it on your computer.
- The CRM reads the file and shows how many rows with data it has.
- Click “Next”. If you picked the wrong file, click “Choose another file”.
Step 2. Columns
CRM fields are on the left, your file’s columns on the right. Columns the CRM recognised are already selected, with an example value from the file next to them.
| CRM field | What goes into it |
|---|---|
| Client | The name of the client or company. Required |
| Phone | The CRM uses it to find clients who are already in the database |
| Deal name | If there is no such column, the client name becomes the deal name |
| Amount | The deal amount |
| Stage | The stage from your file, on step three you link it to a pipeline stage |
| Owner | Who handles the deal. If the column is empty, the person importing the file becomes the owner |
| Source | Where the client came from |
| Comment | A note for the deal |
| Created on | When the deal appeared |
| Lost reason | If filled in, the deal is imported as lost and goes to the “Lost” tab |
- Check that each field has the right column. If a column is not needed, choose “Do not import”.
- The client column is required: without it the CRM will not let you continue.
- Click “Next”.
Step 3. Stages
This step appears if the file has a stage column. Stages from your file, for example “Invoice issued” or “Thinking”, are on the left, your pipeline stages on the right.
- For each stage in the file, pick the matching pipeline stage.
- Anything you leave unset goes to the first stage of the pipeline.
- Click “Next”.
Step 4. Check
The CRM tells you in words what will happen after the import:
- “Deals to import: …”;
- “New client cards to be created: …”;
- “Deals going to clients already in the CRM: …” (matched by phone);
- “Rows to skip (no client): …”;
- which stages you left unmatched and where those deals will go;
- “How they land by stage” and “This is how the first deals will look”.
If everything is right, click “Import” with the number of deals. If not, click “Back” and fix it. After the import the CRM says “Deals imported: …”, and the deals are already on the board of the selected pipeline and behave like ones entered by hand.
Importing from amoCRM
- In amoCRM open Leads, select the deals you need or all of them and click Export. You get an XLSX file.
- In WazzaBee CRM open “Settings → Data transfer” and on the “Deals from amoCRM” card click “Import from amoCRM”.
- Choose the file. The CRM recognises amoCRM columns (Budget, Lead stage, Primary contact and others) on its own.
- On the “stages” step, link the amoCRM stages to the stages of your pipeline.
- Check the result and click “Import”.
The CRM does not confuse the amoCRM “Pipeline” column with the stage: the stage is taken from the lead stage column.
Moving from Bitrix24
More than deals can be moved from Bitrix24: pipelines, deals, clients, history and tasks come in one migration file in JSON format, and open line conversations come in a second file. Both files are produced by the export of your Bitrix24 portal.
- On the “Move from Bitrix24” card, click “Choose files”.
- Click “Choose migration file” and pick the .json file. The file must be no larger than 80 MB.
- The CRM shows what is in the file: the portal, deals in progress, won and lost deals, contacts, history records, tasks and a list of pipelines with the number of stages, lost reasons and deals.
- If the file has leads, tick “Move leads as a separate “Leads” pipeline”. Leads that have already become deals are not moved again.
- If money in Bitrix24 is kept in a custom field, pick it in the “If a deal has no amount, take it from the field” list. Revenue will then be calculated for these deals.
- Choose how to import: “Import into the CRM” or “Just have a look”.
- Click “Load”. After the import the Deals screen opens.
| Mode | What happens |
|---|---|
| “Import into the CRM” | Deals and clients stay in the CRM for good: they survive a page refresh and behave like ordinary ones |
| “Just have a look” | Nothing is saved: the data is visible only in this browser tab until you refresh the page. This lets you see in advance how everything lands |
How the CRM lays out Bitrix24 data
- Loss stages become lost reasons, and lost deals go to the “Lost” tab with a filter by reason.
- The won stage becomes “Paid”.
- Custom deal fields appear in the deal card in the “Bitrix24 fields” block.
- Deal history goes to the feed marked “Call”, “Email”, “Meeting”, “Stage change” or “Activity”.
- A lost deal from the move can be viewed but not changed until you return it to work.
Open line conversations
- First choose the migration file with the deals: the conversations are linked to them.
- Click “Choose conversations file” and pick the second export file (…-chats.json).
- Click “Load conversations”.
Chats are linked to their deals, and if there is no deal, to the contact’s latest deal or to the client card. Service messages of open lines are hidden, you can show them in the chat. The conversations are visible on the deal’s “Chat” tab and in “Chats”, read only. If conversations were already loaded, the new file replaces them: the CRM warns you about it.
After the import
The “Data transfer” tab shows a “Loaded from file” block: the portal, the number of deals, lost deals and contacts, and how many chats and messages there are. Next to it are the buttons “Open deals”, “Load conversations” or “Replace conversations”. For data loaded in the “Just have a look” mode there is a “Restore CRM data” button: the data from the files disappears from the tab and your CRM from the database opens.
Frequently asked questions
Will clients be duplicated if they are already in the CRM?
Not when importing from Excel, CSV or amoCRM: if the client’s phone is already in the CRM, the deal goes to that client and no new card is created. Clients without a phone count as new.
Why were some rows skipped?
Those rows have an empty client column. A deal without a name has nothing to show in its card, so the CRM skips such rows and shows their number on the check step.
Can I import deals that are already lost?
Yes. Map the column with the lost reason to the “Lost reason” field: such deals are imported into the “Lost” tab.
The file is larger than 10 MB. What should I do?
Split the table into several files and import them one by one. The limit for a Bitrix24 migration file is 80 MB.
Where do deals go if a stage in the file matches no pipeline stage?
To the first stage of the pipeline. On the check step the CRM shows in advance which stages are unmatched.
