Seller field guide · 3 min read
What should you preserve before migrating a business system?
Before a migration, assess whether permitted operational history is about to lose its comments, relationships or context. Preserve only what your retention and rights review allows, using an export you can validate independently. A migration deadline is a reason to plan the inventory early, not to rush an unreviewed data transfer.
A successful migration can still lose useful history
Moving the fields needed by the new system does not necessarily preserve the full historical workflow. Zendesk documents that its CSV ticket export omits comments and descriptions, illustrating why an export that looks complete in a spreadsheet may not contain the reasoning behind a resolution.
List the features the new system will not import: archived objects, deleted-user mappings, attachments, status events, custom fields and old policy references. Then decide which of those are permitted and useful to preserve separately. The migration project and the licensing assessment need different acceptance criteria.
Source notes: Zendesk: account export formats and limitations
What should an archive handover contain?
Slack documents that exports contain message history and file links. A link in a historical export is not the same thing as a self-contained permitted attachment. Check whether a reviewer will still be able to interpret the package after the old subscription, permissions or accounts change.
The following is a recommended preservation register, not a claim about every platform’s export capabilities. Keep it with the archive so a future reviewer understands both what survived and what was intentionally left out.
| Preserve when authorized | Why it matters | Validation |
|---|---|---|
| Original record identifiers | Keep conversations, tasks and outcomes connected | Trace a sample of cross-system relationships |
| Schema and field definitions | Explain old status values and custom fields | Compare definitions against representative records |
| Export manifest and dates | Identify the actual captured population | Reconcile counts by period and record type |
| Exclusion and retention decisions | Explain omissions without recreating restricted data | Confirm the approved scope with its owner |
Source notes: Slack: reading workspace exports
Validate before retiring the source
Select samples across different years and process versions, then compare them with the source while it is still available. Count checks alone will not reveal missing comments or broken joins. Record limitations rather than recreating unavailable history from memory.
Treat the resulting archive as controlled company material. Restrict access, keep a named owner, and apply existing retention decisions. Assessing potential licensing value is not a blanket reason to extend retention, preserve material subject to deletion, or give a prospective buyer unrestricted system access.
Source notes: NIST: Privacy Framework
Illustrative scenario · fictional company
A fictional SaaS team discovers a migration gap
Juniper Billing is leaving a support platform. The migration spreadsheet carries ticket subjects and status, but not the internal conversation that explains each resolution. The team checks its allowed export options and tests a permitted historical sample before closing the old account. It preserves a schema note and linked ticket identifiers, excludes restricted customers, and documents missing attachments. The archive is retained only under the company’s approved policy while a separate licensing assessment proceeds.
When to pause or narrow the scope
Client work and customer files are excluded from this starting scope. Assess company-owned internal records separately from personnel, health, privileged or NDA-restricted material.
- Retention or deletion obligations require records to be removed.
- The export cannot be reconciled and would misrepresent its coverage.
- Migration pressure prevents a proper permissions and exclusion review.
Your preparation checklist
- List what the destination migration does and does not preserve.
- Check platform export documentation and account permissions.
- Record schema, relationships, scope and export timestamps.
- Validate representative records against the source before retirement.
- Keep approved archives access-controlled with a named owner.
Start with a description of the records. The quote form does not ask you to upload a dataset.
Discuss your dataSources and further reading
- Zendesk: account export formats and limitations · Checked October 26, 2026
- Slack: reading workspace exports · Checked October 26, 2026
- NIST: Privacy Framework · Checked October 26, 2026
This is general information, not legal advice or confirmation that a buyer will accept your records. Published buyer ranges describe their programs, not an offer for your dataset. Buyers may pay QuoteMyData when a deal closes; see how we are paid.
