How to move your newsletter (and your subscribers) to a new tool without starting over

Moving a newsletter looks, from the outside, like a file export. In practice it is a short relocation project: you are changing the house your subscribers’ addresses live in, and sometimes the domain that sends to them. Done carefully, readers barely notice. Done hastily, you import problems you then have to explain — bounces, confused people, even spam complaints.

This guide is a checklist for moving without starting the relationship over. It assumes you already have permission to email the people you are taking with you. If you are building a list for the first time, you want why every creator needs an email list instead.

What you are actually moving

A healthy move has four parts:

1. The list — addresses, names if you have them, and how each person joined if your old tool recorded it.
2. The permission — evidence that these people asked to hear from you, not a pile of comments or purchased names.
3. The sending identity — the From name, From address and the authentication (SPF, DKIM, DMARC) that prove you are allowed to use that domain.
4. The conversations — welcome notes, regular cadence, unpaid promises (“I write on Sundays”) and any sequences that should not fire again by accident.

Archives of old issues are nice to have. They are not required to continue. Your readers care more that next Sunday still feels like you.

Decide what “done” looks like before you export

Write down, in a few lines:

• The date you want the first issue to leave the new tool.
• Whether the From address will stay the same.
• Whether you will keep the old account around for a couple of weeks as a safety net.
• Who should not be imported (unsubscribes, complainers, confirmed-invalid addresses).

If the From address stays the same and your domain’s authentication will point at the new sender, readers will mostly experience a seamless handoff. If you are also changing domains (from a shared workspace address to mail on your own domain, for example), plan extra time. Inbox providers treat a new sending domain like a newcomer, even if you have been writing for years.

The technical pieces of that newcomer period overlap with deliverability: authenticate the domain, keep complaints low, and do not suddenly blast a cold list from a domain that has never sent before.

Export more than a column of emails

From the old tool, download:

• All subscribers you are still allowed to email.
• A separate export of unsubscribes and, if available, spam complainers. You will use this as a blocklist so those people are not resurrected.
• Any fields you rely on: first name, signup date, source, tags that actually change what you send.
• Recent bounce or “invalid” reports, so you can leave those rows out.

Open the file on your computer and look at it with your eyes. Sort by signup date. Spot-check a few rows. If you see addresses you do not recognize from signups — a scraped-looking set, a leftover workshop sheet you never asked, a column of personal contacts who never opted in — stop and clean before you import. Moving is not a chance to launder a sloppy list.

Save a dated copy of the export somewhere you control. If an import goes wrong, you want the original file, not a second export you have already edited beyond recognition.

Clean before you import

Do the unglamorous work in a spreadsheet:

• Remove duplicates.
• Remove anyone who unsubscribed or complained in the old system.
• Remove obvious typos you cannot fix (gmail.con without a known correction).
• Remove role addresses if you never had them as real readers (info@, admin@) and they only produce trouble.
• Keep a column that says they came from the previous tool, so you remember this cohort later.

You do not need to pay a mysterious “list validation” service unless you already know the file is old and damaged. If the list is years stale and engagement was near zero, consider a re-permission email from the old tool first: “I am moving my notes to a new setup — click if you still want them.” Import only the people who click. That is slower and much safer than dragging a silent list onto a new sending domain.

Import with the right story attached

Most tools, including Contact Concert, let you bring subscribers in from a CSV. The important part is what you assert during that import: you are saying you have permission to email these people.

Import them as already-subscribed only if they already confirmed and never opted out. Do not run your full welcome sequence on people who have been reading you for two years. Either suppress welcome automations for the imported group, or write a different “we moved” note (below) and leave it at that.

If your new tool offers double opt-in for new signups, leave it on for the public form. That setting should not force every imported person to confirm again unless you chose a re-permission campaign on purpose.

Tell people you moved, once, clearly

When the list is in place and a test email to yourself looks right, send a short issue from the new tool:

• You are still you.
• The email address they know (or the new one, if it changed) is now sending from a new setup.
• The cadence and promise stay the same.
• How to unsubscribe, which should already be easy.
• A useful piece of content, so the message is not only administrative.

Subject lines should be plain: “A quick note about these emails” is better than a teaser. For more on honest subjects, see subject lines and preview text.

Send that note to a portion of the list first if the list is large or the sending domain is new — your most recent, most engaged readers — then widen. This is often called warming: you show inbox providers that real people who asked for the mail are interacting with it. It is not a growth hack. It is how you avoid looking like a stranger who suddenly acquired ten thousand addresses.

Authentication and domains

If you use your own domain (recommended as you grow), update DNS so SPF, DKIM and DMARC describe the new sending service. Remove or update old records that still authorize a tool you no longer use, or you can end up with overlapping instructions.

Send tests to an address you read in Gmail, one in Outlook or Microsoft 365 if you have it, and one on a phone with Apple Mail. Check that:

• The From name looks like you.
• Links work, including unsubscribe.
• Images, if you use them, load.
• The message does not arrive as a scary “via some unexpected path” if you can avoid it.

Keep the old tool’s sending paused once you go live, so nobody gets two copies of the same issue.

Sequences, forms and public links

Walk through every public door into the list:

• Bio links, YouTube descriptions, profile links and printed URLs should point at the new signup page. If you use Contact Concert, that is contactconcert.com/@yourname or an embed on your site.
• Old landing pages should redirect or display the new form, not keep writing to the retired database.
• Welcome and leftover automations in the old tool should be turned off.
• Paid or membership extras that mentioned “you’ll get an email from X” should be updated so you are not making a promise the old server still tries to keep.

If you collect subscribers from YouTube or from Instagram and TikTok, update those links in the same sitting. A mixed week, where half your mentions still feed the old tool, is how lists diverge.

What not to do

Do not buy a list to “replace engagement” after a move. That is how you inherit complaints.

Do not import unsubscribes “just in case they change their mind.” They already told you no. Under US commercial email rules you must honor opt-outs promptly (within 10 business days of the request under 15 U.S.C. § 7704), and re-adding them during a migration is a good way to earn spam reports.

Do not send six catch-up issues in two days to show the new system works. Send the normal cadence.

Do not change your voice, your promise and your tool in the same week unless you have to. Readers can absorb one change at a time.

Do not delete the old account the same afternoon. Keep read-only access long enough to confirm exports were complete and no stray automation is still firing.

A day-by-day outline

A few days before

• Export subscribers, unsubscribes and complaints.
• Clean the file.
• Set up the new account, domain authentication and a test list that contains only you.

Moving day

• Import the cleaned file with welcomes suppressed for that group.
• Send yourself a full test issue.
• Point your main public signup link at the new page.

The next send

• Tell readers you moved, in one short section of an otherwise normal issue — or a standalone note if the From address changed.
• Watch bounces, complaints and replies more closely than usual, using the lens in newsletter metrics that actually matter.

Two weeks later

• Confirm no new signups are landing in the old tool.
• Turn the old sending fully off.
• Keep the export files stored safely.

Frequently asked questions

Will I lose my subscribers if I switch tools?

Not if you export them, exclude people who opted out, and import only addresses you have permission to use. The risk is not the spreadsheet; it is sending from a new place without authentication, warming or a clear note about what changed.

Should imported subscribers confirm their email again?

Not automatically. Confirmation is for new signups and for true re-permission campaigns. Asking loyal readers to opt in again “because we switched software” will shrink a healthy list for no good reason.

Can I move in the middle of a welcome sequence?

Yes, but finish or pause that sequence deliberately. Either let those few people complete it in the old tool, or recreate the remaining emails in the new one. Do not let both systems send.

What if my old tool will not export everyone?

Export what you can, document the gap, and put a notice on your old signup page and in one public post: how to join the new list. Do not attempt to reconstruct addresses from invoices, comments or DMs.

Does Contact Concert support bringing a list over?

Yes. You can import a CSV from another platform, and double opt-in remains available for new subscribers. Details are on the features page. You are still responsible for having permission to email the people in the file.

Move the house, keep the relationship

A migration is successful when next week’s issue arrives, looking like you, for the same people who asked to get it. The software in the middle should feel like plumbing.

If you are ready to bring a clean, permissioned list into Contact Concert, you can start a free trial, compare plans or read how imports and hosted signup pages work on the features page. For help with the product, write to hi@contactconcert.com.