Inventory the queue before changing connections
List each pending item with an internal label, destination account, intended time and timezone, copy, asset location, and current status. Include native platform schedules and automatic sync rules, not just the tool you are replacing. A campaign can have several copies with different owners. If two systems can publish the same copy, the migration has a duplication risk even when both systems work correctly.
Keep the original media and final text independently available. A downloadable performance report is not necessarily an export of editable drafts or scheduled records. If the old tool lacks a usable queue export, record the required fields manually and check them against its interface. Do not assume importing a spreadsheet will preserve media, alternative text, platform options, or schedule semantics without inspecting the new tool's actual results.
Choose a cutoff and reconcile every destination
For an illustrative launch, let the old system own all confirmed items before a selected cutoff and the new system own later items. Write the cutoff with a timezone. Around the boundary, review jobs already uploading or processing separately: canceling a local queue entry may be too late to stop an accepted platform task. TikTok, for example, documents cancellation of media pulls as best effort.
Use the worksheet below for each destination, not just each campaign. The statuses are your migration bookkeeping, not universal platform labels. If one row cannot be resolved, pause that item rather than transferring uncertainty into two systems. Keep a person responsible for the cutover so collaborators do not independently recreate a post that someone else has already moved.
| Item | Old system | New system | Completion evidence |
|---|---|---|---|
| Announcement A / account 1 | Owns pre-cutoff publication | Do not recreate | Save the destination URL |
| Tutorial B / account 2 | Confirmed canceled before dispatch | Owns new schedule | Check saved time and later URL |
| Clip C / account 3 | Processing; outcome unresolved | Hold | Resolve original task first |
Test the new path before loading the whole queue
Transfer a small representative batch first. Check the account, complete caption, link destination, asset, accessibility information, and schedule as saved by the replacement. Reopen the saved item instead of relying only on the form you submitted. YouTube's scheduling documentation explicitly includes a timezone selection; other tools may display or store it differently. Confirm your intended instant rather than copying a clock reading without context.
After the first publication, inspect the destination directly. Compare the new URL with the old system's history and look for duplicates. If something fails, identify whether the problem is account authorization, an unsupported option, unavailable media, or an unresolved previous task. Do not reactivate the entire old queue as a blanket fallback. That can duplicate the copies that the new workflow already published successfully.
Retire the old tool only after reconciliation
A rollback plan should say which system owns the still-unpublished rows and how the other system is disabled for those rows. Reconcile already-public copies separately. Keep a record of the final schedules and destination URLs before removing access. Account disconnection, subscription cancellation, retained-data deletion, and deletion of public posts are separate actions; verify each one that your migration actually requires.
For Ferryman or any replacement publisher, test the specific create, schedule, or sync route you intend to retain. Avoid enabling reverse sync routes merely to make the migration feel complete. The cutover succeeds when every planned destination has one known owner, published work has a recorded URL, and unresolved work has an explicit next action. No universal importer is needed to apply that discipline.
FROM GUIDE TO WORKFLOW
Explore this workflow in Ferryman
Review Ferryman's planner and scheduling
Check draft management, pending-post editing, and cancellation before moving a queue. Use the cutover checklist to assign one publishing owner to each destination.
Sources & further reading
Written by Ferryman. Sources checked Oct 16, 2026. Platform rules can change; consult the linked documentation for current requirements.