Prepare a change set
List which fields will change, which will remain untouched and how exclusions are preserved. Separate technical observations from subscriber-state changes. Keep an authorised backup or recovery reference appropriate to the source system before performing a bulk update.
Use a bounded acceptance step
Inspect the exact import options and compare expected changes with available preview information. Where the tool provides no safe preview, determine another documented control rather than improvising a production experiment. Do not treat a finished upload as verified reimport.
A return receipt
After an authorised update, record the observed outcome, exception count and any unresolved cases. Compare the resulting state with the intended changes. If the result is uncertain, stop additional batches until the discrepancy is understood. This guide does not connect to or modify your systems.
Put it into practice
A proposed change set can list the source record identifier, old technical value, new technical value, source observation and unchanged exclusion fields. Use a controlled internal artifact appropriate to the data; do not publish it or upload it to this guide. Review the exact destination and field mapping before execution. A fictional import preview that shows 1,000 updates may still be wrong if it updates subscription status instead of a technical-result field. The number of affected rows is only one acceptance condition. After an authorised return, compare observed changes with the intended set and record any exception. If the interface gives an uncertain result, do not immediately repeat the upload; establish whether the first action took effect. Preserve the recovery reference and stop dependent batches until the outcome is known. These safeguards concern your process, not a claim that every platform has an identical preview or undo function.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Bouncer integrations — Merchant documentation · usebouncer.com · Merchant-controlled · checked 2026-09-27
- Mailchimp audience requirements — Merchant documentation · mailchimp.com · Merchant-controlled · checked 2026-09-27