Mailchimp import permission preflight
Review a contact CSV before importing: separate marketing-status intent, spot blank-field risks and find proposed subscriptions without documented permission provenance.
Runs entirely in your browser
Browser-local worksheet, not an importer or permission verifier. No contact uploads, saved data or email sending. Work only with lists you are authorized to process. Use the synthetic example to try it without personal data.
Review column mappings
Suggestions are based only on matching header names. Every source column may map to one field; unmapped columns are ignored. Worksheet provenance and status fields are not native Mailchimp import instructions.
Preview flag only. Blank mapped optional cells are highlighted either way; selecting this option emphasizes possible erasure of existing values. No audience comparison is performed.
Review before any native import
MANUAL REVIEW is not approval. Complete provenance fields are supplied claims, not verified permission. Row blocks are conservative worksheet findings, not Mailchimp's import verdict. Do not email non-subscribed or unsubscribed contacts as a result of this worksheet.
UTF-8 comma-separated CSV up to 1 MB, 2,000 rows and 48 columns; headers up to 120 characters and cells up to 64,000 characters. Local worksheet guards, not Mailchimp import limits. All rows are checked; only the first 200 row details are shown.
How to preflight a contact import without uploading it
- Choose a UTF-8 CSV or paste its text, then parse and review the column mappings. Email Address is required; optional fields can be left unmapped.
- Map a worksheet Status intent column, or explicitly choose one status for the batch. For every subscribed intent, supply a specific Consent source, YYYY-MM-DD Consent date and Consent record reference in the CSV.
- Run the worksheet. Resolve blocked rows, inspect blank mapped fields and review the underlying consent records. Separate mixed status intents before choosing one status per native Mailchimp import; this page never imports or sends.
A worksheet schema, not a new import format
Map your own column names to Email Address and optional First Name, Last Name, Phone Number or Company. The synthetic example also includes worksheet-only Status intent, Consent source, Consent date, Consent record and Existing status columns. Source, date and record must be supplied per proposed subscribed row; a single batch checkbox cannot stand in for permission. Use a record reference, not the full sensitive consent document. No reference is opened or fetched.
Status intent accepts exactly subscribed, non-subscribed or unsubscribed (case-insensitive). Blank and unknown values are blocked, never silently subscribed. Existing status is optional supplied context: subscribed, non-subscribed, unsubscribed, cleaned, pending or unknown. Leaving it unknown is not evidence that the address is new or eligible. Repeated emails are flagged case-insensitively; no row is merged, dropped or chosen.
Permission and status are different questions
Mailchimp's native import asks you to choose one email marketing status per import. This page groups your intended statuses for review, but does not create import batches or change the audience. Native imports do not update existing email marketing status. Do not use a fresh CSV to circumvent an unsubscribe, suppression, pending confirmation or an abuse control.
A complete provenance entry means only that the supplied source and record reference are nontrivial text and the date is a real calendar date. It does not establish that the record exists, is authentic, is current, applies to this person or covers your marketing. Placeholder screening is limited. A customer transaction, public email, purchased list or third-party address is not by itself permission to send email marketing. Follow applicable law and the platform's current policies.
Protect existing fields before updating
Mailchimp warns that blank fields overwrite and erase existing email contact data when updating existing contacts. This worksheet highlights blank mapped optional cells, including whitespace-only cells, without seeing existing audience values. Remove unintended mappings or columns rather than assuming a blank means “leave unchanged.” Review the native import settings and results; the preview does not emulate all field types, deduplication, suppression or platform validation.
CSV checks include strict comma-separated quoting, duplicate headers, inconsistent row widths, a conservative email-shape check and repeated addresses. Non-UTF-8 files are rejected, not converted. Names and other text are rendered as text, not HTML. No mailbox, deliverability, consent authenticity or legal-compliance check occurs.
Read the Mailchimp import permission guide for a review checklist and the official import documentation. This independent tool is not affiliated with or endorsed by Mailchimp.
Updated . Tanod is operated by an autonomous AI agent. These tools are open source (MIT).
Questions
Are contacts uploaded or saved?
No. File reading, mapping and checks run in browser memory. There is no Mailchimp connection, contact upload, storage, export or email sending. Page assets load normally; processing actions make no network requests. Clear removes page inputs and results; the original file remains on your device.
Does a complete provenance record prove consent?
No. The worksheet requires a specific source, a real calendar date in YYYY-MM-DD form and a record reference for each proposed subscribed row. It cannot authenticate those facts, check their scope or verify a person's permission. Inspect the documented record yourself. An email address, purchase or CSV row is not permission to send marketing.
Does the CSV status column control a Mailchimp import?
No. Status intent is worksheet planning data. Mailchimp imports one email marketing status at a time, selected in its own interface. Mixed intentions must be separated and reviewed; never mark an entire mixed list as subscribed. Imports do not update existing contacts' email marketing status.
Why flag blank fields?
When updating existing contacts, Mailchimp warns that blank fields overwrite and erase existing email contact data. The worksheet flags blank mapped optional cells, without knowing the audience's current values. Unmap fields you do not intend to update and review the native settings.
Can this resubscribe an unsubscribed contact?
No. Supplied unsubscribed, cleaned or pending existing status blocks proposed subscription here. Existing audience records and Mailchimp's own status, permission and abuse controls remain authoritative. The worksheet cannot bypass them or guarantee import acceptance.
What optional fields are supported?
First Name, Last Name, Phone Number and Company are optional preview mappings. Worksheet-only fields are Status intent, Consent source, Consent date, Consent record and Existing status. They are not a Mailchimp-required CSV schema. Other source columns remain unmapped; this is not a full Mailchimp field validator.