Audience
Beyond CSV upload, Mumara ONE pulls contacts directly from Gmail, Outlook, Yahoo, and Mailchimp over OAuth — with field mapping, list and tag preservation, and on-demand re-sync. The thing that makes migration day painless.
How import works
Step 1
Authorize Gmail, Outlook, Yahoo, or Mailchimp over OAuth — no exporting a CSV from one place to upload into another.
Step 2
Match the provider's fields — and Mailchimp's lists, tags, and merge fields — to your lists and Custom Fields, so the structure carries over intact.
Step 3
Pull the contacts in, validated and de-duplicated against what you already have, so nothing arrives messy or doubled.
Step 4
Refresh from the source on demand whenever you need the audience current, rather than letting it go stale the moment it landed.
What carries over
A migration is only painless if you keep what you built. Mumara ONE brings the organisation across — not just a flat dump of email addresses you'd have to re-segment from scratch.
Email addresses and the core identity of every contact — validated as they arrive.
A provider's lists and Mailchimp audiences map onto your lists, so groupings survive the move.
Mailchimp tags carry across, ready to become segment rules instead of being lost on arrival.
Merge fields and provider fields map to your typed Custom Fields, keeping personalization data intact.
Incoming contacts are checked against what you already have, so nothing lands doubled or malformed.
Bring your suppression list along so contacts who already opted out stay opted out after the move.
You decide the mapping — the page reflects how your lists and fields are actually organised.
Why OAuth beats CSV gymnastics
CSV still works — and it's there when you need it. But for the providers people actually migrate from, a direct connection skips the part where structure gets lost in translation.
The old way
Download a CSV from the old tool, re-map columns by hand, upload, and discover the lists and tags didn't come with it. Every round-trip through a file flattens structure and invites mistakes — and the moment it's done, it's already a stale snapshot.
The Mumara way
Authorize the source once and pull contacts directly — with lists, tags, and merge fields mapped onto your structure as they come in. De-duplicated against what you already have, and re-syncable on demand so the audience stays current instead of frozen.
Worked example · Mailchimp
The Mailchimp connection is the migration workhorse. Audiences become lists, tags become segment-ready labels, and merge fields become typed Custom Fields — so the segmentation you built over years doesn't collapse into one undifferentiated list.
What lands is immediately usable: contacts ready to segment, fields ready to personalize with, and prior opt-outs respected from day one.
What teams do with it
“Moving off Mailchimp was the part I was dreading — I assumed we'd lose all our tags and segments and rebuild from a flat CSV. Instead the audiences, tags, and merge fields came across mapped, and the people who'd unsubscribed stayed unsubscribed. We were sending again the same afternoon.”
Verified review
Mumara ONE customer
Common questions
Gmail, Outlook, and Yahoo for contact lists, and Mailchimp for full audience migration — all over OAuth. Standard CSV import is available too for anything else.
Yes. The Mailchimp connection brings audiences across with their lists, tags, and merge fields preserved and mapped to your lists and Custom Fields — so the segmentation you built doesn't collapse into a flat dump.
You map the provider's fields to your Custom Fields during import, so contacts arrive structured and immediately segmentable rather than as raw rows you have to clean up.
Bring your existing suppression list along and those contacts stay suppressed after the move — combined with de-duplication on arrival, migrated audiences respect prior opt-outs from the first send.
Yes — re-sync on demand pulls from the connected source again to keep the imported audience current, instead of relying on a one-time snapshot.
Standard CSV import handles anything else — you still map columns to your lists and Custom Fields on the way in, so the result is just as structured as an OAuth pull.
Related
Imported contacts land in the lists/contacts/fields model, ready to maintain and segment.
Read moreProvider fields and Mailchimp merge fields map to your typed Custom Fields on import.
Read moreTags and fields that come across become the rules you target on right away.
Read moreBring your existing suppression list along so migrated contacts respect prior opt-outs.
Read moreHigher tiers add hands-on migration assistance for a clean cutover.
Read moreMumara ONE · Contact Import
Connect Gmail, Outlook, Yahoo, or Mailchimp over OAuth and pull contacts in with lists, tags, and fields intact — then re-sync whenever you need them current.
