Move an audience without the CSV relay race

Choose a source list and destination list, then let OpenContact stream contacts directly between connected providers while keeping a canonical copy and visible progress.

Plan a migration · Browse integrations

Provider to provider

Select a readable source resource and a writable destination resource. OpenContact:

1. reads contacts from the source list;
2. records each contact in the project with migration context;
3. sends the contact to the selected destination list;
4. tracks fetched, pushed, and failed totals.

The transfer stays inside the connected workflow instead of creating export files that must be cleaned, stored, and uploaded manually.

Isolated from everyday automations

A direct migration does not run ordinary sync rules or email verification. That separation prevents a provider move from activating welcome flows or sending contacts into unrelated destinations.

Useful beyond switching platforms

Use direct migration to:

• replace an email provider;
• consolidate several audiences;
• seed a new provider before launch;
• maintain both sides during a transition;
• copy a local OpenContact list into a connected destination.

Keep the long-term route separate

Migration handles the initial copy. Afterward, sync rules define how future contacts and changes should flow, while suppression policies keep opt-outs honored across the connected tools.

Next steps

Explore contact importing · Build ongoing sync rules · Read the migration guide