How to Migrate to Kommo CRM from Spreadsheets, HubSpot, or Salesforce Without Losing Data

Q: How do you import contacts into Kommo CRM from a spreadsheet?

Kommo provides a native CSV import tool that lets you map spreadsheet columns to CRM fields. Export your Google Sheets or Excel file as a CSV, go to Leads > Import in Kommo, upload the file, and match columns like Name, Phone, Email, and Company to Kommo's standard fields. For custom fields (like Lead Source or Deal Size), create them first in Settings, then they'll appear in the mapping step. Most US businesses complete a basic import in under 30 minutes for up to 5,000 contacts.

Q: Can you migrate from HubSpot to Kommo without losing history?

Yes, but it requires a structured export and careful planning. HubSpot lets you export contacts, companies, deals, and notes as CSV files. You can import these into Kommo, but conversation history and email threads require additional steps—either exporting email logs separately and attaching them as notes, or using a migration partner who can script the transfer via both APIs. Activity timestamps and deal stages can be preserved if you map HubSpot's lifecycle stages to Kommo's pipeline stages during import.

Q: How long does a Kommo CRM migration take?

For a US small business with 1,000–10,000 contacts and a single sales pipeline, a DIY migration typically takes 1–3 days including data cleanup, import, and testing. More complex migrations from platforms like Salesforce or HubSpot—with multiple pipelines, custom objects, and historical activity—usually take 1–2 weeks with partner assistance. The timeline depends on data cleanliness, number of integrations (WhatsApp, email, etc.), and how much historical conversation data you need to preserve.

Q: What happens to WhatsApp conversations when you migrate to Kommo?

If you're connecting a new WhatsApp Business API number to Kommo, your future conversations will sync automatically. However, historical WhatsApp chats from another CRM or the regular WhatsApp app don't transfer—WhatsApp's API doesn't support exporting past messages. The workaround is to export chat logs manually and attach them as notes to lead cards in Kommo, or start fresh and brief your team on key context. Once connected, Kommo captures every incoming and outgoing WhatsApp message going forward.

Q: Do I need a partner to migrate to Kommo CRM?

Not for simple migrations. If you're moving from a spreadsheet or a basic CRM with clean data, Kommo's built-in import tools and documentation are enough for most US small businesses. However, if you have complex Salesforce automations, HubSpot workflows, custom objects, or you need to preserve years of conversation history, working with an Official Kommo Partner like Solve IT LLC saves time and prevents data loss. Partner-assisted migrations also include pipeline setup, automation configuration, and team training—typically a better ROI than spending 40+ hours figuring it out yourself.

You've outgrown your spreadsheet, or you're tired of paying $1,200/month for a HubSpot plan your five-person sales team barely uses. The decision to migrate to Kommo CRM is the easy part—what keeps US business owners up at night is the fear of losing years of customer data, breaking integrations, or having their sales team dead in the water for a week during the switch. This guide walks you through the exact steps to move your contacts, deals, and conversation history to Kommo without the chaos.

Why US Businesses Are Migrating to Kommo in 2026

The CRM market has bifurcated. On one end, you have enterprise-grade platforms like Salesforce charging $150–$300 per user per month with implementation costs that easily hit $20,000+. On the other, you have Kommo at $15–$45 per user per month with native WhatsApp, Instagram, and Facebook Messenger integrations built in—channels US consumers actually use for business communication.

Most of the businesses we work with aren't choosing Kommo because it's cheaper (though it is). They're choosing it because their sales process has shifted from email-first to messaging-first, and their old CRM wasn't built for that reality. If your team is already texting leads from personal phones or running WhatsApp conversations outside the CRM, you're losing visibility and compliance. Kommo centralizes all of that. Learn more about why Kommo fits US small businesses before diving into migration specifics.

Step 1: Audit Your Current Data Before Export

The biggest migration disasters happen before anyone touches the new CRM—they happen because of dirty data. Before you export anything, run a cleanup pass on your existing system.

Start by identifying duplicate contacts. If you're in a spreadsheet, use conditional formatting to highlight duplicate emails or phone numbers. In HubSpot, run the built-in deduplication tool. In Salesforce, use the "Potential Duplicates" report. Delete or merge duplicates before export—importing 8,000 contacts only to spend a week cleaning them up in Kommo defeats the purpose.

Next, standardize your data formats. US phone numbers should be in E.164 format (+1 followed by 10 digits) for WhatsApp integration. Email addresses should be lowercase. State abbreviations should be consistent (TX, not Texas). Deal values should be in USD with no currency symbols in the field—just numbers.

Solve IT Tip: Create a "Migration Status" column in your spreadsheet or a custom field in your old CRM before export. Mark each contact as "Active," "Inactive 6+ months," or "Do Not Migrate." This lets you import only your active pipeline first, then decide later if you need historical dead leads cluttering up your new system.

Step 2: Migrating from Google Sheets or Excel to Kommo

If you're moving from a spreadsheet, you're actually in the best position—no API complications, no workflow dependencies, just clean data transfer. Here's the process:

Export to CSV: In Google Sheets, go to File > Download > Comma-separated values. In Excel, Save As and choose CSV UTF-8 format. UTF-8 encoding prevents special characters (accents, emojis in notes) from breaking during import.

Map your columns to Kommo fields: Kommo's native import tool lets you match each CSV column to a standard field (Name, Email, Phone, Company) or a custom field you create beforehand. If you track "Lead Source" or "Industry" in your spreadsheet, create those as custom fields in Kommo's Settings > Fields before importing.

Assign to the right pipeline: During import, you'll choose which pipeline and stage each batch of leads enters. If you're importing cold leads separately from active deals, run two imports with different pipeline assignments.

For most US small businesses with under 5,000 contacts, the entire spreadsheet-to-Kommo migration takes 30–60 minutes including field mapping and verification.

Step 3: Migrating from HubSpot to Kommo CRM

HubSpot migrations are more complex because you're not just moving contacts—you're moving deals, companies, notes, and potentially years of email history. Here's how to approach it without losing critical data:

Export contacts and companies: In HubSpot, go to Contacts > Actions > Export. Choose CSV format and include all properties. Repeat for Companies. These exports include lifecycle stage, deal association, and custom properties.

Export deals separately: Go to Sales > Deals > Actions > Export. This gives you deal amounts, stages, close dates, and associated contacts. You'll need to reconcile contact IDs between exports to maintain relationships in Kommo.

Handle conversation history: This is where most teams get stuck. HubSpot doesn't export email threads as part of the contact CSV. You have two options: export the Communications report and attach key conversations as notes to Kommo lead cards, or use HubSpot's API to pull email activity programmatically. For most US businesses, option one is sufficient—you don't need every "Thanks for the info" email, just key decision points.

"The companies that struggle with HubSpot-to-Kommo migrations are the ones who try to replicate their old system exactly. The smarter move is migrating your active pipeline and last 90 days of history, then using the fresh start to build cleaner processes."
— The Solve IT LLC Team

Step 4: Migrating from Salesforce to Kommo

Salesforce migrations require more planning because most Salesforce orgs have custom objects, complex automations, and years of accumulated technical debt. The good news: if you're moving to Kommo, you probably don't need all of that complexity.

Use Data Export Service: In Salesforce, go to Setup > Data Export > Export Now. This gives you CSVs for all standard and custom objects. For cleaner exports, use Data Loader or a tool like Dataloader.io to pull specific objects with filters (e.g., only opportunities created in the last 18 months).

Decide what actually needs to migrate: Most Salesforce orgs have dozens of custom objects that no one uses anymore. Before migrating, ask: "Will my sales team reference this data in the next 6 months?" If not, archive it in a spreadsheet and don't import it to Kommo. A lean CRM is a useful CRM.

Rebuild workflows in Kommo's Digital Pipeline: Salesforce Process Builder flows and Apex triggers don't migrate. You'll need to recreate key automations using Kommo's Digital Pipeline (for lead routing and follow-up triggers) or external tools like n8n for complex multi-system workflows. The upside: Kommo's automation is visual and doesn't require a developer for most use cases.

What Happens to WhatsApp Conversations During Migration?

This question comes up constantly from US businesses already using WhatsApp for customer communication. The short answer: WhatsApp conversation history doesn't migrate between CRMs.

WhatsApp's Business API doesn't allow exporting message history—it's a platform limitation, not a Kommo limitation. If you're currently running WhatsApp through another CRM or through the regular WhatsApp Business app, those conversations stay in the old system.

Your options:

Export chat logs manually: In WhatsApp Business app, you can export individual chats as text files. For key accounts, export these and attach them as notes to the corresponding lead cards in Kommo.
Start fresh with context: Brief your sales team on key account history before cutover. The first message in Kommo can reference the prior conversation ("Following up on our discussion last week about the Q3 project...").
Run parallel systems temporarily: Keep the old WhatsApp connection active (read-only) for 30 days while all new conversations flow through Kommo. This gives reps access to history while transitioning.

Once your WhatsApp Business API number is connected to Kommo, every future message—incoming and outgoing—syncs automatically to the lead card with full timestamp and read receipt data.

Need Help with a Complex Migration?

As an Official Kommo Partner, we've migrated US businesses from spreadsheets, HubSpot, Salesforce, and legacy CRMs without data loss or sales downtime. Our migration packages start at $1,500 and include data cleanup, pipeline setup, WhatsApp integration, and team training.

Get a Migration Quote

How Long Does a Kommo CRM Migration Actually Take?

Migration timelines vary wildly based on data volume, source system complexity, and how much historical context you need to preserve. Here are realistic benchmarks for US small and mid-sized businesses:

Spreadsheet to Kommo (DIY): 1–3 days including data cleanup, import, pipeline configuration, and team walkthrough.

HubSpot to Kommo (DIY): 3–5 days if you're only migrating contacts and active deals. 1–2 weeks if you need full email history and workflow recreation.

Salesforce to Kommo (Partner-assisted): 1–3 weeks depending on custom object complexity, integration requirements, and historical data volume.

The biggest time sink isn't the import—it's deciding what to import. Every hour spent auditing and cleaning data beforehand saves three hours of cleanup afterward.

Frequently Asked Questions About Migrating to Kommo CRM

How do you import contacts into Kommo CRM from a spreadsheet?

Export your Google Sheets or Excel file as a CSV with UTF-8 encoding. In Kommo, go to Leads > Import, upload the CSV, and map each column to a Kommo field (Name, Phone, Email, Company, or custom fields you've created). Choose the target pipeline and stage, then run the import. For files under 5,000 rows, the import completes in under five minutes. Larger files may take 15–30 minutes and run in the background.

Can you migrate from HubSpot to Kommo without losing history?

Yes, with planning. Contact data, deal data, and notes export cleanly via HubSpot's CSV export. Email conversation history requires exporting the Communications report separately and attaching key threads as notes in Kommo. Activity timestamps preserve when deals were created and updated. For complex HubSpot orgs with extensive automation, working with a migration partner ensures nothing critical gets lost.

How long does a Kommo CRM migration take?

Simple spreadsheet migrations take 1–3 days. HubSpot migrations with moderate complexity take 3–7 days. Salesforce migrations with custom objects and integrations typically take 1–3 weeks with partner assistance. The timeline depends primarily on data cleanliness and how much historical context you need to preserve.

What happens to WhatsApp conversations when you migrate to Kommo?

Historical WhatsApp messages don't transfer—WhatsApp's API doesn't support exporting conversation history. Once you connect your WhatsApp Business API number to Kommo, all future conversations sync automatically. For key accounts, export chat logs from the old system and attach them as notes to Kommo lead cards.

Do I need a partner to migrate to Kommo CRM?

Not for simple migrations from spreadsheets or basic CRMs. Kommo's native import tools handle most scenarios. For migrations from Salesforce or HubSpot with complex workflows, years of history, or custom integrations, a partner like Solve IT LLC saves significant time and prevents data loss. Partner-assisted migrations also include pipeline optimization, automation setup, and team training—delivering ROI beyond just data transfer.