Can I bring my old autoresponder's emails with me?

What systeme.io will move for you

Its migration service lists transferring emails and campaigns as one of the things it covers, alongside contacts, funnel pages, blogs, articles, courses and automations.

The service comes with the Unlimited plan or with any annual plan. Once subscribed, the request goes through support and into a queue.

How that actually works

By hand, by a person. systeme.io states that all content is migrated manually, that requests are taken first come first served, and that a migration takes 17 days on average, depending on how much there is and how complex it gets.

The team asks for the login details of your old account so they can copy the content across. Your old account is not changed, so you can keep using the other platform throughout. The one instruction is to leave your content alone while it is being copied.

You can work inside systeme.io during the migration as long as you do not edit the pages the team is currently building.

Doing it yourself

There is no import step. Moving an old sequence across means recreating it, and the structure lines up well enough that this is less work than it sounds.

• An old sequence becomes a campaign, and each email in it becomes an email inside that campaign with a delay set on it.
• Old broadcasts become newsletters.
• The subject line and the body text get copied over. systeme.io calls the classic editor the plainer of the two writing modes.

Pick the editor before you start pasting. Switching between the classic editor and the visual editor while working on an email loses whatever you had written in the one you left.

Leave the old HTML behind

Copying the words rather than the template is worth doing deliberately.

systeme.io names complex HTML, excessive fonts, heavy images and too many emojis as things that add weight to an email, and says that heavy emails are more likely to be flagged by spam filters or rejected outright by receiving servers.

An old template from another platform is exactly where that weight comes from, and it is the part of the old emails least worth keeping.

The contacts are a separate job

Emails and contacts do not travel together. If a contact list comes across as part of a migration, systeme.io runs a check before anything is allowed to send: a short form asking where the contacts came from and whether they consented.

A self-service import gets the same treatment. Sending can be paused after an import while the origin of the list, the condition of the addresses and the sending domain are examined.

Keeping the old tool instead

If the emails are staying where they are, systeme.io can be pointed at an outside autoresponder. Your own SendGrid account can do the sending, ActiveCampaign connects through an API integration, and other tools such as GetResponse or Brevo connect through Zapier.

None of that is required. The built-in autoresponder covers newsletters, campaigns and event-triggered emails on its own, and systeme.io states plainly that an external one is optional.