Cleaning a list before it reaches Moosend

For price-conscious marketers wanting automation without a large bill.

Moosend accounts often carry several overlapping mailing lists inherited from a previous platform, and the same person appears in three of them. The export is per list, which makes the duplication invisible until you merge the files.

Getting the addresses out of Moosend

Mailing lists, choose the list, then the export option for members.

Before consolidating your lists, so you deduplicate and verify in one pass rather than untangling two sets of per-list statuses afterwards.

What Moosend does with the file you bring back

The import rules decide what a re-import actually changes, which is worth knowing before you upload.

The short version

  • Imports match on email within a list and update the existing member.
  • Bounced status is per list, so the same address can be active elsewhere in the account.
  • Custom fields import alongside the address.
  • Moosend's help center says billing counts unique addresses across all your lists, so overlap between lists costs you clarity rather than money. Statuses are still kept per list.

The mistake to avoid

Some addresses come back unresolved, and that is a fact about the receiving server rather than a gap in the check. We label those and never bill for them. What that means, and why roughly 28% of business addresses land there, is set out on our page about catch-all domains.

13,500 rows across three lists, 9,800 people

Picture a travel agency that moved to Moosend with three lists from its old tool: 6,000 newsletter readers, 4,500 past bookers and 3,000 brochure requests. That's 13,500 rows. Merge the exports and 9,800 unique addresses are left.

On billing, the overlap costs less than you'd fear. Moosend's help center says unique email addresses are counted once across all mailing lists, and that bounced, archived and unsubscribed members aren't counted at all. You'll find the figure under Billing, then Subscription Plan and Credits, shown as unique active subscribers. After an import it can take five to ten minutes to refresh, so don't panic at a stale number.

Where the overlap does cost you is in bounces, since a dead address on three lists can fail three times. Check the 9,800. Suppose 1,050 are invalid and 300 unknown. A 10,000 pack at $25 covers it, and we don't bill the 3,700 duplicate rows if you upload the merged file as it stands.

Archive, and the suppression list above your lists

Because a bounce is recorded per list, cleaning one list leaves the same address live on the others. Moosend's documentation describes a suppression list that sits outside the mailing lists. Read that page and confirm in your account how it applies across them. If it behaves as described, loading your 1,050 invalid addresses there stops any list, present or future, from mailing them.

Archiving is the other tool worth knowing. An archived member keeps their record and custom fields but drops out of sends and out of the billable count. For the 300 unknowns, archiving beats deleting, since you can restore them when you're ready to test that group with a small send.

Moosend also sells credits for occasional senders alongside its subscriber plans. If you mail four times a year, compare the two before an import pushes you up a subscriber tier you'll barely use.

Questions people ask

Should I verify before migrating to Moosend?

Yes. Migrations are exactly when a list's real condition becomes visible, and a new account has no sending history to absorb a poor first campaign.

How do I avoid duplicate subscribers across lists?

Use one list with segments rather than several lists with overlapping members. The same address on two lists is billed once, but its bounce and unsubscribe status is tracked separately on each, and that is where mistakes creep in.

What should happen to unknown results?

Put them in their own list and send to them after your confirmed addresses, so a weak result there does not distort the main campaign report.

Check a sample first

100 free checks a month, no card. The share we could not resolve is the number worth comparing between vendors.