Moving your email list without losing contacts

Changing email platforms is more than copying names and addresses. This guide explains how to migrate your email list from one platform to another while preserving consent, segmentation and deliverability, especially for Australian businesses sending to customers on mobile devices.

A controlled sequence—export, cleanse, map, test, launch and retire—reduces the risk of duplicate campaigns, broken automations or an unexpected privacy breach. It also gives you a clear rollback plan if the new platform behaves differently.

Audit the source platform

Begin with a complete inventory of the current platform: subscribers, active and inactive segments, custom fields, tags, sign-up sources, consent dates, automations, templates, integrations, transactional email and historical engagement. Separate marketing contacts from customers who must receive service messages.

Search results can mix current documentation with stale or unrelated material. If a result such as this unrelated-looking page appears, verify the publisher, date and claims against official platform guidance before acting.

Record list size, bounce rate, spam-complaint rate, unsubscribe rate and engagement by segment. Export a snapshot before changing anything, and note which records carry proof of permission to receive email.

Confirm Australian privacy and consent

Australian senders should follow the anti-spam rules in the Spam Act 2003, while organisations covered by the Privacy Act 1988 must assess the Australian Privacy Principles. A commercial email generally needs clear consent, accurate sender identification and a working unsubscribe mechanism.

Do not treat every address on an old list as automatically reusable. Check why each person subscribed, whether that permission covers your current message type, and where the consent evidence is stored. Keep suppression and unsubscribe records intact rather than recreating them as new active subscribers. If permission cannot be established, leave those contacts inactive or suppressed rather than assuming a new commercial campaign is allowed.

Also confirm how personal information moves to the new service provider, restrict staff access and align retention periods with your business and legal obligations. For a small Australian retailer, a simple consent audit is often more practical than importing thousands of unverified contacts.

Choose the migration route

Choose between a direct integration, a structured file transfer or an API-assisted process. The right route depends on how much segmentation and history you need to preserve, not simply on subscriber count.

Migration route	Best suited to	Main advantage	Main limitation
Native or partner transfer	Platforms with a supported importer	Fast and usually preserves core fields	May not transfer consent history, automations or advanced segmentation
CSV export and import	Most established or custom lists	Flexible and easy to inspect	Requires cleaning, field mapping and duplicate prevention
API-assisted transfer	Large, complex or frequently updated lists	Automates repeatable field and segment mapping	Needs technical testing and ongoing maintenance

Common choices in the Australian market include Mailchimp, Klaviyo, HubSpot, Brevo and Campaign Monitor. A broad email service comparison can help shortlist options by linking to external providers, but check each provider’s current import guide and privacy terms before selecting one.

A Sydney retailer with sophisticated loyalty segments may need field-level control, while a hobby seller can often use a simple CSV route. The decisive factors are data quality, consent quality and the features your team will actually maintain.

Clean and map the data

Export in a stable format such as UTF-8 CSV, using consistent column names and dates. Keep first name, last name, email address, country, state or territory, language, segment, source, consent date and consent method only where those details are genuinely required.

Remove duplicate and invalid addresses, standardise capitalisation and resolve conflicting records against your authoritative customer database. A person entered as “Jane@example.com” and “jane@example.com” should not become two campaign recipients.

Map old fields to the new platform’s defaults, document every transformation and preserve the source field where permitted. Do not assume imports carry over form triggers, revenue data, predictive segments, email activity, SPF or DKIM records; recreate the ones the business still needs.

Import in a controlled pilot

Import a small, representative test group first, then send internal and seed tests through the new platform. Check mobile rendering in popular apps, image blocking, personalised links, footer content and unsubscribe behaviour across Australian mobile inboxes.

Authentication belongs to the sending domain, so configure SPF, DKIM and DMARC for the new platform and verify them before a commercial campaign. Repoint tracking links and campaign URLs, test automations one by one, and keep transactional email separate from promotional campaigns.

A staged campaign can reveal duplicate records, missing fields or broken links before a full launch. Australians commonly read email on phones while commuting or shopping, so a fast, legible message is a useful test of the migrated setup.

Cut over and monitor results

Once results are reliable, pause routine sends from the old platform and schedule the final export and import during a low-risk window. Account for Australian operating hours and time zones: a support team in Perth may be starting while teams in Sydney, Melbourne and Brisbane are already well into the afternoon.

Monitor delivery, bounces, complaints, unsubscribes, engagement and segment counts closely for the first several campaigns. Compare them with the source platform’s baseline rather than reacting to a single unusually busy or quiet day.

Keep the old system read-only for an agreed rollback period, then remove unnecessary copies and revoke integrations. Retain consent evidence and transactional records for the period required by your policies and law. If something fails, redirect sending to the verified old platform and correct the import before trying again.