Switch from ActiveCampaign to GetResponse without losing scores or suppressions

What actually transfers

GetResponse has no direct ActiveCampaign connector in its self-serve import: you export CSV files from ActiveCampaign and import them from a file, one list at a time. ActiveCampaign lets you export a list filtered by status, Active, Unconfirmed, Unsubscribed, Bounced or Any, with a Status column and a Date Unsubscribed field. Use that filter: the active file becomes your import, the unsubscribed and bounced files become your suppressions.

On the GetResponse side you choose whether to add new contacts, update existing ones or both, assign each column to a custom field, and optionally start contacts in an autoresponder cycle on a chosen day. Every import is single opt-in, and you confirm you hold permission before it runs.

What breaks along the way

Three things do not survive as working objects. Lead and deal scores export as numbers, but GetResponse cannot apply a score during an import, only to contacts found by search afterwards, so carry each score in a custom field and rebuild the scoring rules. Tags arrive in one ActiveCampaign column while GetResponse reads one column per tag, with a limit of ten tags per import: split the column, then run extra imports that only update existing contacts if you have more. Contact notes cannot be exported at all, so copy anything you rely on before you close the account.

The CRM side is the larger loss. Deals, pipelines and site tracking history are not part of a contact export, and automations are not either. If your ActiveCampaign account hands leads to sales, decide where that handoff lives after the move before you cut over.

Object by object: what comes across

Read from each provider's own export and import documentation, listed under the table. We have not run this migration on a paid pair of accounts, so nothing here is a test result. Anything a provider does not document, we leave out rather than guess.

How the objects map

An ActiveCampaign list maps to a GetResponse list; if you ran several lists for one audience, consider importing them into one list and keeping the old list name as a tag, so one person is one contact, which matters because the GetResponse review shows a contact held on two lists is billed twice. The GetResponse plan ladder shows what each list size costs. Tags become GetResponse tags once the column is split. Custom fields map by type, so create them in GetResponse first and keep dates as dates. Segments become saved searches on those fields and tags. Automations become GetResponse workflows or, for a plain timed sequence, an autoresponder cycle. Branching depth is where the two differ most, so list every ActiveCampaign automation and mark which ones you rebuild, flatten or retire, as described in the GetResponse versus ActiveCampaign comparison.

Test before you cut over

Import the active file into a test list and hold it against the export: totals, tags populated, score field filled, role addresses dropped. Load the suppression list and confirm a suppressed address is excluded from a test newsletter. Rebuild one workflow, walk a real signup through a new form with a consent field, and check the contact lands in the right list with the right tag. On cost, price the same list on both: from $19/mo against from €16/mo, then run your own volume through the email cost calculator. Keep the ActiveCampaign account read-only for a billing cycle as your rollback. If part of your list lives in Mailchimp, the Mailchimp to GetResponse migration inventory shows how to bring that audience into the same account.

Try GetResponse →