> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackshift.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Move existing support history into StackShift

> Bring an authorized export of customers, conversations, tickets or knowledge into the right destination.

<Note>
  This guide includes features awaiting release. If an option is not available in your workspace, contact StackShift Support.
</Note>

## What you can do

Bring an authorized export of customers, conversations, tickets or knowledge into the right destination. Where to find it: Settings → Migrations

## Before 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

<Steps>
  <Step>
    Export the records you are authorized to move from the old service. Keep the original export while reviewing the import.
  </Step>

  <Step>
    Open Migrations and load the supported package. Read parsing errors and warnings; correct the file before proceeding.
  </Step>

  <Step>
    Map records to the intended brand, inbox, published ticket type and knowledge centre or collection. Preserve the difference between public messages and private notes.
  </Step>

  <Step>
    Run the dry run and inspect its proposed changes and warnings. Confirm only after the mappings and scope are correct.
  </Step>

  <Step>
    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.
  </Step>
</Steps>

## 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

<Check>
  Historical records appear in the selected destinations without sending old messages to customers as new replies.
</Check>

## If something goes wrong

<Warning>
  * Dry run fails: fix the reported mapping, field or destination permission.
  * Resume unavailable: check source retention and permissions; erased or expired source content cannot be restored by retrying.
</Warning>

## Related guides

<CardGroup cols={2}>
  <Card title="Find missing answers and improve your help centre" href="/stackshift-support/knowledge-insights">
    Use feedback and unanswered questions to decide what to write next.
  </Card>

  <Card title="Export, retain or delete Support data" href="/stackshift-support/data-and-privacy">
    Handle data requests deliberately and understand what deletion affects.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.