# Switch to Migaru without starting over. Import your accounts, contacts and deals from a CSV export, connect your mailbox and calendar, and Migaru fills in the conversations around them. - **Four steps** from the first export to a connected inbox. - **A minute or two** to import a file of tens of thousands of rows. - **Two years** of email and meetings, read back from each mailbox. - **Undo** any import from its history, if a column went to the wrong field. ## The record only works if someone keeps it. ### You keep the record by hand Every call logged, every stage moved and every note typed by whoever has a spare minute. Most weeks, nobody has one. ### Calls leave nothing behind What they said about budget, and who makes the decision, was clear on the day. Two weeks later it lives in one person’s memory, if anywhere. ### Promises go unkept Nothing reminds anyone who was promised what, or by when, so the follow-up goes out late or not at all. ### Nobody can say what’s working Which deals slipped, which accounts went quiet, where the pipeline really stands: the answers are in there somewhere, and getting them out takes an afternoon. ## With Migaru, it keeps itself. ### Conversations file themselves Migaru files every outside email conversation once both sides have written, and every external meeting, on the contacts and accounts involved, and keeps last-contact dates and summaries current. ### Promises become tasks Commitments made on the calls Migaru records or the transcripts you upload, and in email if you allow it, become tasks. Overdue ones can be drafted into follow-ups for you to send. ### The context sits on the account Summaries, transcripts and the threads around each meeting are on the account, and the agent answers questions about them with links to where each answer came from. ### You can see what moved Ask which deals slipped and why, how many accounts have gone quiet, or how win rates compare by industry, and get numbers counted from your records rather than estimated. ## What comes across, and what doesn’t ### An import brings across - Accounts, contacts, deals, tasks, notes and your own objects, one CSV per object, up to 50,000 rows a file. - Every column you map onto a field. - Each contact’s company, linked to that company’s account, which is made if it doesn’t exist yet. - Accounts and contacts already in Migaru, matched by website and email address and filled in rather than duplicated. ### It leaves behind - Email history. Migaru reads it from each person’s mailbox instead, up to two years back. - From a file, links between records other than a contact’s company. Connected, HubSpot’s, Pipedrive’s and Attio’s come across. - Automations. Describe each rule in a sentence and it is rebuilt as a workflow, on Pro and above. - Fields and stages. Create them first: the importer maps onto what exists. ## Four steps from any CRM 1. **Export your records.** Export each object from your old CRM as its own CSV file: accounts, contacts and deals, and any others you keep. Nothing connects to your old CRM, so nothing there changes while you move. 2. **Set up your stages and fields.** Create the custom fields you need and name your deal stages to match your old pipeline. The importer maps onto fields that already exist, and a stage only comes across if Migaru has one spelled exactly the same way. 3. **Import each file.** Import each file into its object, up to 50,000 rows at a time. Columns named like one of your fields map themselves, and where it can, Migaru suggests a field for the rest for you to check. Every import is logged and can be undone. 4. **Connect your mailbox and calendar.** Each person connects Gmail or Outlook along with its calendar, and Migaru reads back up to two years. Conversations land on the records you imported: contacts are matched on email address and accounts on the domain of their website, so https://www.acme.com and acme.com are the same account. Anything that still looks like a duplicate is flagged for you to merge. ### After the move, if you want - **Turn on the notetaker.** Each person turns it on in Settings → Mail and calendar, for their external meetings or all of them, and from their next Google Meet, Zoom or Teams call Migaru records it and files the transcript on the meeting. Zoom calls need their Zoom account connected too. - **Add your old call transcripts.** Drop in the transcripts your old recorder exported, several at a time. Migaru files each one on the meeting it belongs to, making one when your calendar never had it, or on the account or contact when it can’t be sure, and lists any it can’t place for you to attach. It reads each one for commitments, unless the person who uploaded it keeps only who and when. - **Rebuild the automations you still need.** Describe each rule in a sentence: what triggers it, the conditions, and what to do, such as set a field, create a task or notify someone. Migaru reads the rule back to you before it is created. Workflows come with Pro and above. ## Your CRM, in its own words - [Switch from HubSpot](https://www.migaru.ai/migration/hubspot.md): Move from HubSpot to Migaru in four steps: connect it read-only, bring companies, contacts, deals, notes and tasks with their links, and connect your inbox. - [Switch from Salesforce](https://www.migaru.ai/migration/salesforce.md): Move from Salesforce to Migaru in four steps: export accounts, contacts and opportunities, import each file, and connect your inbox for two years of history. - [Switch from Pipedrive](https://www.migaru.ai/migration/pipedrive.md): Move from Pipedrive to Migaru in four steps: connect it, bring organisations, people, deals, notes and activities with their links, and connect your inbox. - [Switch from Close](https://www.migaru.ai/migration/close.md): Move from Close to Migaru in four steps: export leads, contacts and opportunities, import each file in a minute or two, and connect your inbox. - [Switch from Copper](https://www.migaru.ai/migration/copper.md): Move from Copper to Migaru in four steps: export people, companies and opportunities, import each file, and connect Gmail or Outlook. - [Switch from Lightfield](https://www.migaru.ai/migration/lightfield.md): Move from Lightfield to Migaru in four steps: export accounts, contacts and opportunities, import each file, and connect your inbox for two years of history. - [Switch from Attio](https://www.migaru.ai/migration/attio.md): Move from Attio to Migaru in four steps: connect it read-only, bring companies, people, deals, notes and tasks with their links, and connect your inbox. - [Switch from folk](https://www.migaru.ai/migration/folk.md): Move from folk to Migaru in four steps: export each group as a CSV, import its people and companies, and connect your inbox for two years of history. - [Switch from Day.ai](https://www.migaru.ai/migration/day-ai.md): Move from Day.ai to Migaru in four steps: bring companies, contacts and deals as CSV files, and rebuild the context from two years of email. - [Switch from Clarify](https://www.migaru.ai/migration/clarify.md): Move from Clarify to Migaru in four steps: bring companies, people and deals as CSV files, import each, and connect your mailbox and calendar. ## Questions ### Which CRMs can I switch from? Any that can export CSV, or a spreadsheet you’ve kept by hand. Export each object as its own file and import it into the matching object in Migaru. HubSpot, Pipedrive and Attio can be connected instead, read-only, to bring their records with the links between them. HubSpot, Salesforce, Pipedrive and seven more each have a page with the steps in their own words. ### What comes across in an import? Records for any object, whether accounts, contacts, deals, tasks, notes or your own objects, with every column you map to a field. A company column on a contact file links each contact to that company’s account, and makes the account if there isn’t one; other links between records don’t come across. Email history isn’t imported either; Migaru reads it from each person’s mailbox instead. ### How long does it take? Four steps. An import runs as soon as the columns are mapped, and takes up to a minute or two for a file of tens of thousands of rows; one over 50,000 needs splitting first. Reading two years of mail and calendar takes longer, and carries on in the background, a batch every fifteen minutes, while you work. ### My CRM exports several files. Does that work? Yes, one file at a time, each imported into the object it belongs to. ### Should I tidy my data before importing? It helps. An account already in Migaru is matched by its website, and a contact by email address, so importing them again fills in empty fields rather than making a second copy. Deals and other records are matched by the ID column your CRM’s export gives each row, or the id in an export from Migaru; a file without one creates them again, and that run can be undone from import history. Rows without a name are skipped, and a dropdown value that matches none of the field’s options is left empty. Afterwards, Migaru flags records that look like the same company or person for you to merge. ### Can I keep using my old CRM for a while? Yes. Nothing in your old CRM changes while your team moves across: Migaru imports the files it exports, and HubSpot, if you connect it, is only read. There is no sync between the two either, so pick a day to stop entering data in the old one. ### Do my automations come across? They don’t import. Recreate the ones you still need by describing each rule in a sentence: what triggers it, the conditions, and what to do, such as set a field, create a task or notify someone. Migaru reads the rule back to you before it is created. Workflows come with Pro and above. ### Can I get my data out again? Yes. Export any view as CSV, Excel or JSON, up to 50,000 rows a file, or read every record back out through the API, a page at a time. [Start free trial](https://app.migaru.ai/sign-up) or [request a demo](https://www.migaru.ai/book-demo). --- Canonical page: https://www.migaru.ai/migration Last updated: 2026-10-29