How it works
A help desk never stops. While a full migration of 500,000 tickets runs, customers keep writing in and agents keep replying. A delta migration handles this in three steps:
- Full run. Move everything as it was at time T0, while agents keep working in the old help desk.
- Delta. At cutover, move only the records created or updated after T0, such as new tickets and new comments on old tickets.
- Switch. Point email forwarding, widgets and channels at the new help desk.
| Without a delta | With a delta | |
|---|---|---|
| Agent downtime | Freeze for the length of the full run | Minutes to hours at cutover |
| Tickets changed during the run | Lost or re-entered by hand | Captured |
| Risk | Pressure to rush the full run | The full run can take as long as it needs |
What the native tools do / where they stop
No major help desk offers “delta migration” as a feature. The pieces exist as APIs. Zendesk’s Incremental Export API returns “items that changed or were created … since the last request”, and Zendesk recommends cursor-based exports, with an end_of_stream flag to show you’ve caught up. File exports don’t work for this: Freshdesk’s ticket export “will NOT give you the entire conversation” or archived tickets, so a CSV can’t carry a delta of new comments.
The other detail the docs don’t cover is what a delta does to a ticket that changed in both systems. Most delta tools overwrite the destination with the newer source version. So the rule at cutover is simple: agents work in one system at a time.
Checklist for a clean delta
- Record T0 precisely, in UTC, when the full run starts.
- Make sure every record keeps its source ID, so the delta updates instead of duplicating.
- Include new comments on old tickets, not just new tickets.
- Run a rehearsal delta a day before cutover to time it.
- Switch channels only after the final delta finishes.
Where FlitStack AI fits
Delta migration is part of every FlitStack AI migration. It catches tickets created or updated during the cutover window, so support doesn’t freeze. See help desk migrations.