Skip to main content
Video walkthrough coming soon.
Moving CRM is usually the reason a migration stalls: the data comes across but the history does not, so nobody trusts it and everyone keeps the old tab open. Leadey imports the work, not just the records.

Start the import

SettingsImport from CRM. Connect the account you are moving from and Leadey pulls it across — the companies, the people, the opportunities and their stages, and the activity history attached to them.

What comes across

Run it more than once

A migration is rarely one pass. You import, notice something missing, fix the mapping and run it again. That is safe. Leadey keeps a map between each record and its id in the old system, so a second run updates what it already brought across rather than creating a second copy of everything. Re-running converges rather than duplicating.
This is the part worth testing before you commit. Run it once, check a handful of records you know well — an account with a long history, a contact who appears twice in the old system — and only then trust the whole thing.

What to check afterwards

  1. A contact you know is in the old system twice. They should be one person in Leadey with both histories.
  2. An opportunity mid-pipeline. Its stage should map to a Leadey stage that means the same thing — set your pipelines up first, under SettingsPipelines.
  3. Activity dates. History should be dated when it happened, not when it was imported.
  4. Owners. People need to exist in your workspace before their records can be assigned to them, so invite the team first.

Order of operations

  1. Invite your team, so owners can be assigned
  2. Build your pipelines and stages to match how you sell
  3. Set up lead statuses and any custom fields you rely on
  4. Run the import
  5. Check the four things above
  6. Re-run if the mapping needed changing

Part 1 — Set up your workspace

Team and permissions first — owners need to exist before records can be assigned.