Start with an export you can trust
Export each object separately, typically companies, contacts and deals, rather than one flat file. Keep the original files untouched and work on copies.
Clean before you import
Most migration problems are data problems that existed already. A short pass beforehand saves a lot of rework.
- Remove duplicate contacts and companies.
- Standardise stage names, owner names and date formats.
- Decide which old records are worth bringing across.
- Make sure every row has a stable identifier you can match on, such as an email address or an external ID.
Map fields to your pipeline
Write down how each source column maps to a FlowCRM field and each source stage to a pipeline stage. Decide early what to do with fields that have no equivalent: create a custom field, or leave them out.
Test with a small file
Import a sample of about fifty rows first. Check that owners, stages, dates and linked records came through as expected, then fix the mapping rather than the data by hand.
Import in order, then verify
Import companies first, then contacts, then deals, so that links resolve. Afterwards compare record counts with your export and spot check a handful of deals end to end.
The self-serve import wizard for Sheets, CSV and HubSpot is in build (Soon) and included in every plan. Until it ships, guided onboarding runs these steps with you.
If you would rather not do it alone
Guided onboarding covers mapping, validation, migration and training with a FlowCRM specialist. The migration page explains the process and is the easiest way to start that conversation.