Almost every business we work with starts in the same place: a sales spreadsheet that's grown over the years, a few shared inboxes, and a lot of knowledge that lives in people's heads. Sometimes there's an old CRM nobody really uses. It works, sort of, until the business grows and things start falling through the cracks.
A Bitrix24 migration is the fix, but the move itself is where many projects stumble. Import a messy spreadsheet and you get a messy CRM. This Bitrix24 migration guide walks through the step-by-step process we use with Australian clients to get it right the first time.
✓ Clean your data before you import it, not after.
✓ Decide your CRM structure first, then map your columns to it.
✓ Always run a small test import before the full one.
✓ Plan a clear switch-over date so the team stops using the old system.
Step 1: Take stock of what you have
Start by listing every place customer information lives today. It's usually more than you think:
• sales or quoting spreadsheets
• an old CRM or contact manager
• your accounting system, such as Xero or MYOB
• email inboxes and Outlook or Google contacts
• phones belonging to your sales team
Decide which of these is the "source of truth" for each type of data. For example, your accounting system might be the most reliable source for company names, ABNs and billing addresses, while your spreadsheet has the sales history.
Step 2: Decide what's worth bringing across
This is a good moment to let go of data you don't need. Contacts who haven't engaged in years, duplicate entries and half-finished records just add noise. Under Australian privacy principles, you also shouldn't keep personal information longer than you need it, so a clean-out is good practice as well as good housekeeping. Our Privacy Act guide covers this in more detail.
Step 3: Design your Bitrix24 structure
Before you import anything, decide how your CRM will be organised. In Bitrix24, the main building blocks are:
• Leads for new, unqualified enquiries (many small businesses skip leads and work directly with deals)
• Contacts for people
• Companies for the businesses they work for
• Deals for sales opportunities, organised into pipelines and stages
Then list the custom fields you need, such as ABN, industry, lead source or state. Keep it lean. Every field you add is one more thing your team has to fill in.
Step 4: Clean and format your data
Export everything into spreadsheets and tidy it up. This step takes the longest, but it's the one that pays off most. Focus on:
• Removing duplicates. Look for the same person or company entered more than once.
• Splitting names. Put first and last names in separate columns.
• Consistent phone numbers. Use one format, ideally international (+61 4xx xxx xxx), so click-to-call and SMS work.
• Australian addresses. Keep suburb, state and postcode in their own columns, and use standard state abbreviations (NSW, VIC, QLD, WA, SA, TAS, ACT, NT).
• Dates. Make sure dates are in one format. A mix of DD/MM/YYYY and MM/DD/YYYY is a classic source of errors when data has passed through US-built tools.
• Marketing consent. Add a column showing whether each contact has agreed to receive marketing, so you stay within the Spam Act from day one.
Step 5: Map your columns for the Bitrix24 migration
Bitrix24 can import contacts, companies, leads and deals from CSV files, and it lets you match each column in your file to a field in the CRM during the import. Write the mapping down first so nothing gets missed. If you're moving from another CRM, check the Migration to Bitrix24 section of the Bitrix24 Market, which has apps for moving data across from other systems. Bitrix24's own migration and import guide explains the options.
Step 6: Run a test import
Import 20 to 50 records first, then check them carefully. Are the names, phone numbers and addresses in the right fields? Are companies linked to the right contacts? Do deals sit in the correct stages? Fix any problems in your file and test again. It's far easier to correct a small sample than to clean up thousands of records later.
Step 7: Do the full import and check it
Once the test looks right, import the rest. Import companies first, then contacts, then deals, so the links between them work. Afterwards, spot-check a selection of records and compare totals against your source files.
Step 8: Switch over and train the team
Pick a go-live date and stick to it. From that day, the old spreadsheet becomes read-only and all new activity goes into Bitrix24. Run a short training session for each role so salespeople, managers and admins know exactly what they need to do. If people keep "just updating the spreadsheet", the CRM will never become the source of truth.
Common mistakes to avoid
• Importing everything "just in case" instead of cleaning first.
• Creating dozens of custom fields nobody fills in.
• Skipping the test import.
• Leaving the old spreadsheet open for edits after go-live.
• Forgetting to connect your website forms and email, so new leads keep landing in the old places.
Need a hand with your Bitrix24 migration?
If you'd rather not spend your weekends cleaning spreadsheets, SalesAid can handle the migration for you, from data clean-up to import, testing and training. SalesAid is a certified Bitrix24 Gold Partner working with Australian businesses. See our Bitrix24 implementation services or book a free consultation.
Frequently asked questions
Can I import an Excel spreadsheet into Bitrix24?
Yes. Save your spreadsheet as a CSV file and use Bitrix24's CRM import, where you can match each column to a CRM field. Clean and format the data first for the best result.
Can I move data from another CRM to Bitrix24?
Yes. You can export data from your current CRM to CSV and import it, or use one of the migration apps in the Bitrix24 Market for supported systems.
What order should I import data in?
Import companies first, then contacts, then deals. That way, contacts can be linked to their companies and deals can be linked to both.
How long does a CRM migration take?
It depends mostly on how clean your data is. A small, tidy spreadsheet can be moved quickly, while larger datasets from several sources need more time for cleaning, testing and checking.