From Another CRM

Migration is a free acquisition tool in PrimoCRM, not a paid feature. You can move your audience in on day one. This page covers migrating from another CRM rather than a plain spreadsheet.

Direct source migration

PrimoCRM’s migration engine has a provider model. Each provider knows how to read one source and normalize it into PrimoCRM contacts, lists, tags, and custom fields. Out of the box the Free plugin includes:

• CSV: the universal path, works with an export from any tool. See Importing Contacts.
• FluentCRM: a direct in-place migration that brings across contacts, their lists and tags, and custom fields.

Additional source providers can be registered by add-ons and by PrimoCRM Pro, so the list of direct sources grows over time.

Migrating from FluentCRM

If FluentCRM is installed on the same site, choose it as the source in Migration. The engine reads your FluentCRM data directly and maps it to PrimoCRM:

• Contacts come across with their details and status.
• Lists and tags are recreated and reattached.
• Custom fields are registered and their values migrated. Migrated data is stored under PrimoCRM’s own native keys, so it is fully first-class in your new CRM.

Because migrated data becomes your data, there is no ongoing dependency on the old plugin once the migration is done.

Migrating from a tool without a direct provider

For a source without a built-in provider, such as Mailchimp, MailerLite, or ConvertKit, export a CSV from that tool and use the CSV import. Map its columns to PrimoCRM fields during import so names, tags, and custom data come across cleanly.

A typical path:

1. Export contacts from your current tool as CSV, including any tag or segment columns.
2. In PrimoCRM, start a CSV import and map columns to contact fields.
3. Apply lists and tags for the batch, or recreate segments as tags after import.

Safe by design

The migration engine is built to be safe on real data:

• It runs in the background in batches, so large lists do not time out.
• It matches existing contacts by email and enriches them rather than creating duplicates.
• It records what it changed so a migration can be reasoned about and, where supported, rolled back.

Tip

Do a small test first. Import a few hundred contacts, confirm the mapping and tags look right, then run the full migration.