List the dependencies first
An announcement routine can depend on audience preferences, message history, staff access, recurring schedules and a sender identity. Write down which of these matter to the organization. Do not assume that every item can be exported, transferred or kept after cancellation. The presence of an import feature does not prove an equivalent export or migration route.
Verify the actual options
Ask the merchant about available exports, number handling, cancellation timing and access after termination before relying on them. Keep applicable retention, permission and security requirements separate from convenience. This guide does not promise portability or prescribe a legal retention period. If a dependency cannot be moved, account for that before committing to a longer term.
Avoid overlapping sends during a change
If an authorized move eventually occurs, identify which system owns the current audience and which scheduled campaigns remain active. Running both casually can create duplicate notices or inconsistent preferences. Reconcile the source and destination through a controlled plan rather than assuming that an exported file is a complete operational handoff.
Keep an adequate fallback
A maintained public reference, an existing permitted email channel or another established routine may provide continuity for ordinary announcements. None is automatically appropriate for urgent or sensitive communication. The point is to understand the dependency before it becomes a crisis, not to buy a second service preemptively. Choose a fallback that fits the actual audience and purpose.
Plan the last scheduled message
Before a change of supplier, identify any future campaigns in the old system and decide through authorized controls which should remain. Record the final intended sending date and the owner of later notices. A paid subscription ending is not evidence that every scheduled activity or integration has stopped. Verify those states separately before treating the handover as finished.
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 pricing — Merchant documentation · txt180.com · Merchant-controlled · checked 2026-10-02
- TXT180 feature documentation — Merchant documentation · txt180.com · Merchant-controlled · checked 2026-10-02