This guide includes features awaiting release. If an option is not available in your workspace, contact StackShift Support.
What you can do
Bring an authorized export of customers, conversations, tickets or knowledge into the right destination. Where to find it: Settings → MigrationsBefore you start
- Permission to import data and access to the destination inboxes.
- A supported portable export or supported Zendesk, Intercom or Freshdesk export snapshot.
Steps
1
Export the records you are authorized to move from the old service. Keep the original export while reviewing the import.
2
Open Migrations and load the supported package. Read parsing errors and warnings; correct the file before proceeding.
3
Map records to the intended brand, inbox, published ticket type and knowledge centre or collection. Preserve the difference between public messages and private notes.
4
Run the dry run and inspect its proposed changes and warnings. Confirm only after the mappings and scope are correct.
5
Start the import and inspect item-level results. Use its cancel or resume action if needed, then reconcile imported counts and representative records against the source.
Example
Move last year’s resolved tickets into the appropriate inbox while keeping their original timestamps and private notes.Things to know
- An export snapshot is not an ongoing live connection to the old provider.
- Imports do not grant former authors staff privileges or automatically publish imported knowledge.
- Unsupported or inaccessible data is reported; inspect warnings rather than assuming every source field was copied.
What happens next
Historical records appear in the selected destinations without sending old messages to customers as new replies.
If something goes wrong
Related guides
Find missing answers and improve your help centre
Use feedback and unanswered questions to decide what to write next.
Export, retain or delete Support data
Handle data requests deliberately and understand what deletion affects.