# SaaS migration context loss and data referrals | SourceX

Canonical: https://refer.sourcex.si/guides/saas-migration-context-loss-data-referral
Last updated: 2026-11-04

Before a SaaS migration, a company should inventory the context that explains its records, not only the records: activity history, app-specific fields, custom events and notifications, user properties and the settings that shaped each workflow. Migration tools often move the core objects and leave those behind. The inventory is metadata only (what exists, how many years, which system, who owns it), and it gives the owner time to decide what to keep before an export deadline closes the option.

## What workflow context should a company inventory before a SaaS migration?

Inventory everything that turns a record into an explained decision: who acted, in what order, under which rule and with which add-on. Then note whether the migration path carries each item, so nothing disappears by default.

A ticket or work item on its own says what happened. The surrounding context says why: the custom field a checklist app added, the event that notified a supervisor, the activity stream that shows a reassignment at 2 a.m. For AI training and evaluation, that sequence is often the useful part, and it is also the part most likely to be dropped quietly when a company moves platforms. That is why a migration is a natural moment for an introducer to raise data licensing: the owner is already deciding what to carry forward.

## A dated example: Jira Data Center to Jira Cloud

Atlassian has published a firm date. Impacted Data Center products reach end of life on March 28, 2029; after that, Atlassian says data stays available read-only, without product updates or support. New-customer Data Center sales ended March 30, 2026, and existing customers can buy new licenses and expansions until March 30, 2028. Every company still running Jira Data Center therefore has a migration or exit decision on a known calendar.

Atlassian's migration documentation also lists what its Jira Cloud Migration Assistant moves and what it does not. Projects, issues, sprints, workflows and boards migrate. Global settings, user-defined custom notifications, custom events, user avatars, per-user timezones, the activity stream and user properties do not. Marketplace app data moves only when the app vendor provides an automated migration path. Checked 2026-10-18; the owner's administrator should confirm against the current page before relying on it.

### The pre-migration inventory (Illustrative)

A fictional 240-person facilities maintenance company has run Jira Data Center since 2016 for work orders and plans to cut over to Jira Cloud in the second half of 2027. Its operations director fills in this sheet with her Jira administrator. No record content is opened; every cell is a count, a date range or a name of an owner.

| Context item | Carried by the assistant? | Metadata recorded | Owner who decides |
|---|---|---|---|
| Projects, issues, workflows | Yes, per Atlassian docs | 11 projects, about 410,000 issues, 2016 to date | Operations director |
| Activity stream | No | Present for all years; no export taken yet | Jira administrator |
| Checklist app fields on work orders | Only if the vendor offers a path | Used on 6 projects since 2019; vendor path unconfirmed | Operations director |
| Custom events and notifications | No | 14 custom events for escalations | Jira administrator |
| User properties and timezones | No | Field crews in 3 timezones | IT manager |
| Global settings and permissions | No | Documented in a 2021 admin runbook | IT manager |

Every number above is invented for the example. The pattern is the point: one of six rows carries over by default, one depends on a third party, and four need a deliberate decision before cutover.

### The calendar the inventory sits on

| Date | Event | Source |
|---|---|---|
| October 2026 | Inventory completed; owner told what the assistant leaves behind | Illustrative plan |
| Q1 2027 | Test migration to a cloud sandbox; app vendor path confirmed or ruled out | Illustrative plan |
| Second half of 2027 | Production cutover | Illustrative plan |
| March 30, 2028 | Last date for existing customers to buy new Data Center licenses or expansions | Atlassian |
| March 28, 2029 | Data Center end of life; data read-only after expiry | Atlassian |

The deadline is real; the company's plan is not. For how Jira history itself carries across, see [Jira Data Center to Cloud migration history](/systems/jira-data-center-to-cloud-migration-history). Use the same two-table shape for any platform move: one table of context items against the migration path, one calendar anchored to a date the vendor has published.

## Which questions show whether the company could qualify?

Before introducing anyone, confirm the basics at metadata level:

- **Size and history.** At least 50 full-time employees at peak, contractors excluded, and documented operating history. A decade of work orders is a good sign; six months is not.
- **Ownership of the records.** Are these the company's own operational records, or client content it holds under contract? Client-owned material usually is not a fit.
- **Rights.** Do customer agreements, employee notices or the app vendors' terms limit reuse? The owner and counsel answer this, not the partner.
- **Authority.** Who can authorize a licensing discussion: the operations director, the CEO, or a parent company?
- **Geography.** Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

The full screening profile is on [who qualifies](/who-qualifies). For the commercial side of a SaaS business changing hands rather than changing platforms, see [how to sell a SaaS company](/guides/how-to-sell-a-saas-company).

## Limits and unanswered questions

- **No SourceX's data requirements are implied.** A preserved activity stream is not a sale. Whether there is demand for the records is something SourceX reviews after the introduction.
- **Vendor documentation changes.** The left-behind list is Atlassian's as of 2026-10-18. Other platforms publish different lists, and some publish none; where there is no documentation, the inventory row says "unconfirmed".
- **Preservation is the owner's call.** The partner suggests an inventory; the company decides what to export, under its own retention and privacy obligations.
- **Canceled subscriptions are a different clock.** If the risk is seats or a whole account lapsing rather than a migration, the timing questions differ: see [canceled SaaS seats and disappearing archives](/guides/saas-archive-retention-referral-opportunity).
- **Declines happen.** Common reasons are covered in [why a company referral was declined](/guides/how-to-understand-why-a-company-referral-was-declined).

Two kinds of money also stay separate. Any compensation for licensed data is agreed between SourceX and the company. A partner's referral reward is paid separately by SourceX and never comes out of the company's payout.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the owner has a migration date and an inventory like the one above, introduce the person who decides what to preserve: [register as a partner](/register), check [who qualifies](/who-qualifies), and read the [program terms](/terms). Agencies building this into client work can start with the [lead generation agency guide](/guides/a-lead-generation-agency-guide-to-becoming-a-data-referral-partner), and more partner playbooks are in [guides](/guides).

## Sources

- https://www.atlassian.com/blog/company-news/atlassian-ascend
- https://www.atlassian.com/licensing/data-center
- https://support.atlassian.com/migration/docs/what-gets-migrated-with-the-jira-cloud-migration-assistant/
- https://refer.sourcex.si/terms
