Do not start with the CSV
Start with the record owner, the proposed message purpose and the evidence that the relevant records belong in the destination. File formatting is a later concern. A technically clean import can still be inappropriate if it mixes unrelated audiences or loses preference history. Keep the smallest relevant scope and follow the merchant’s actual import approval process.
Define what must not change
Write down exclusions, opt-outs and unresolved records that must remain excluded. Identify duplicate and overlapping records without assuming that the destination’s deduplication matches your requirements. Preserve the source record and a controlled reconciliation record according to your organization’s applicable policies. Do not use this website to store or process a contact file.
Separate a test from a full move
If an authorized implementation proceeds, establish a small, permitted test scope with explicit expected outcomes. Confirm which fields, groups and exclusions are represented. A successful upload message is not proof that all preferences or relationships survived. Do not repeat an uncertain import blindly; first reconcile what the destination actually contains to avoid duplicates or unintended sends.
Plan the owner handoff
Record who can approve the import, who reviews discrepancies and who can stop a campaign if a problem appears. Keep the calendar separate from the import action so a newly populated list is not automatically treated as ready for sending. The acceptance decision should be based on verified state and applicable requirements, not the fact that the software accepted the file.
Reconcile counts without exposing records
An acceptance record can compare approved source scope, excluded records, attempted import count and observed destination count. A mismatch is a question to resolve, not a reason to upload the same file again. Keep any necessary record-level investigation inside the authorized systems. A public planning note needs the aggregate discrepancy and responsible role, not the underlying personal data.
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.
- TXT180 feature documentation — Merchant documentation · txt180.com · Merchant-controlled · checked 2026-10-02