Operations
Switching cold email platforms: a small-team migration checklist
By ColdPegion editorial · · 4 min read
Move the operating context with the list, especially the records that say who should never receive another email.
Inventory active work
Record campaigns, sending mailboxes, scheduled steps and audience membership before migrating. Identify contacts who replied, bounced or opted out. An address export rarely includes every operational decision that led to the current sending state.
Pause the work you are migrating through the source tool’s supported controls and confirm its state. Closing a browser does not necessarily stop a background worker. Avoid equivalent live sequences in both products while testing the replacement. Keep a record of which workspace owns each sender and which person can authorize launch.
Preserve exclusions first
Move suppression and DNC information before constructing a new sending audience. Keep earlier replies and exclusion reasons available to the team. When a destination cannot represent a source status exactly, document the translation and use a conservative exclusion until it is reviewed.
Deduplicate by recipient identity and company context. Different capitalization does not make an existing address a new lead. Re-importing a contact should not erase an opt-out or make an old conversation appear new. Review the destination’s supported import semantics instead of assuming that a successful upload preserved all history.
Rebuild one small campaign
Choose a small eligible audience and a familiar brief. Inspect the exact subject and body for each person, including links, attachments and personalization fields. Resolve stale or inconclusive verification evidence under your campaign policy before launch.
Recheck daily caps, weekdays, timezone and waiting periods. Settings with similar names can behave differently across platforms. Use the capacity calculator only as a planning lower bound; it does not replace the actual campaign schedule or a sender’s current allowance. Confirm the review owner before starting any sends.
Retain a recovery path
Preserve exports and the source campaign state while evaluating the pilot. Do not delete the previous workspace because a new import succeeded. Historical reporting definitions may differ, so retain the original counts, timestamps and explanations.
Decide whether the new workflow solves your actual bottleneck. Draft preparation, review effort and reply handling are useful things to observe. A migration alone does not establish better deliverability or more customers. Record the outcome of the small pilot and expand only after the operational handoff is understood.
Sources and useful links
Practical guidance from the ColdPegion team. Examples are illustrative, not customer results. Use the current product documentation for supported operations.
Try the workflow with your own brief.
Connect your AI agent to ColdPegion, prepare a small campaign and inspect the messages before launch.