Quickbooky

Accounting News

Contacts & Data Export

QuickBooks Users Hit Confusion Exporting Marketing Contacts to CSV

QuickBooks users who market through the bundled Mailchimp tools can export contacts to CSV, but status rules, permissions, and a 30-day window apply.

COMMUNITY ISSUESQUICKBOOKY

Small businesses that use the marketing tools sold alongside QuickBooks keep running into the same wall. The list they want to review or back up sits in Mailchimp, the marketing platform Intuit owns, and the path to a spreadsheet is not obvious. The question appeared on a French-language help thread, but the underlying problem crosses languages. The accepted answer lays out the fix, and it carries catches worth knowing before you start.

The QuickBooks connection

Mailchimp handles audiences and campaigns; QuickBooks handles the books. Because Intuit owns both, the services are sold together, and outreach often happens somewhere that feels detached from the ledger. The confusion that follows is predictable. A business knows it has contacts, but cannot tell where the full list lives or which statuses matter.

Every contact carries a status: subscribed, unsubscribed, non-subscribed, or cleaned. A cleaned address is one that bounced or failed badly enough to be pulled from sending. Exports can include any mix of these groups, which matters when you want a true inventory rather than only the people who opted in.

This split trips up the accounting-minded. The customer list in your books and the marketing audience are separate things, updated on separate schedules. An export is often the only practical way to compare the two and spot customers missing from outreach entirely.

Can you shape the contact table first?

You can, and it pays to do so before exporting anything. The contact table shows the basics for each person, and you control what appears. Open the audience area and choose all contacts, then pick the specific audience if you run more than one.

A columns control lets you tick fields on or off. A drag handle next to each field reorders the view, and applying your changes reshapes the table. Hiding a column changes nothing else: the underlying field survives, and any signup form keeps showing it.

Running the export

From the same contacts view, you can export a section, a tag, or a larger group, and you choose which statuses come along. The download does not always arrive as one tidy sheet. Depending on scope, you may get a ZIP archive holding separate CSV files, one per contact type. Unzip it and open the pieces in any spreadsheet app.

One limit stops some teams cold. Only owners and administrators can export a full audience. A staff member with narrower access may hit a wall that looks like a bug but is not, so check the user level before assuming something broke.

What does the export leave out?

Email performance data is not part of the package. Open rates, clicks, and similar metrics live in campaign reports, and they come out through a separate report export. If you need to prove what a mailing actually did, the contact CSV will not carry that evidence. The two downloads answer different questions.

GDPR requests follow a different path

European privacy law lets people ask what personal data you hold on them. When a contact makes that request, the bulk export above is the wrong tool. The guidance on this point is explicit: for an individual data request, you export from that contact’s own profile instead. The single-record route answers the request without exposing everyone else.

A 30-day clock on your files

Exported contacts and their files stay available in the account for 30 days, no longer. After that, you would need to run the process again. Treat every export as a snapshot you store yourself, not a standing backup the service keeps current. Businesses that reconcile marketing lists against their books on a schedule should mind that clock.

The takeaway

The pattern here is familiar from this beat. The feature works, and the friction comes from status rules, permission tiers, and retention windows that surface only at export time. Knowing them in advance turns a lingering support question into a short task.

← Back to Community Issues