Jira Service Management Migration: Move Tickets and Repos Without Losing Trust
Migrate into Jira Service Management with an inventory, field map, pilot import, dual-run week, and validation — so history survives and operators trust the new system.
Quick answer
Migrate into Jira Service Management with an inventory of request types, queues, SLAs, and knowledge, a field map, a pilot import, a dual-run week, and validation with the people who live in the data — so history survives and the team trusts the new system.
- Inventory source objects
- Map fields before bulk load
- Pilot one site / one role / one team
- Dual-run for a week
- Validate with sceptic users
Jira Service Management migration rules
- Inventory first — Typical objects: request types, queues, SLAs, and knowledge.
- Pilot beats big-bang — Prove a small Jira Service Management import before you move everything.
- Integrations after the pilot — Research names Slack, Microsoft Teams, Zapier, and API access on the Jira Service Management side — confirm the connectors your IT loop depends on.
- Do not migrate the wrong job — Jira Service Management is Atlassian ITSM (not Jira Software project tracking). Do not import a git host or an observability suite and expect it to become Atlassian ITSM (not Jira Software project tracking).
Jira Service Management migration map
1. Inventory and map
List request types, queues, SLAs, and knowledge. Map required fields and owners. Never invent list prices here — confirm seats, hosts, ingest, and quote terms on /pricing/jira-service-management/. Worked example: Northline IT (Atlassian shop) discovers duplicate employee IDs in the spreadsheet before the first import — and fixes identity before volume.
2. Pilot import
Import one site, one role, or one team. Run open a request in the portal, SLA it, and resolve with a comment the requester can see on the pilot set. Worked example: Northline IT (Atlassian shop) will not schedule a cutover until the pilot can a requester files a ticket and an agent resolves it without a Jira admin.
3. Dual-run and cutover
Run old and new in parallel for a week. Spot-check records sceptic users care about, then freeze the legacy source. Worked example: Northline IT (Atlassian shop) keeps the old export for tickets, repos, or monitors until Jira Service Management matches for seven consecutive days.
Jira Service Management checklist
Bring these questions to every demo
Ask vendors to show the workflow live, not just describe it.
- 1Inventory source objectsrequest types, queues, SLAs, and knowledge
- 2Run a pilot importOne segment first; fix mapping before bulk.
- 3Validate with operatorsSpot-check records they care about before cutover.
4. Inventory what must move into Jira Service Management
List users, historical records, templates, and integrations that must survive migration. Mark nice-to-have exports you can leave behind.
Worked example: Teams already on Jira Cloud who need a service desk migrates active records only and archives the rest as read-only exports.
5. Run parallel cutover with a rollback path
Keep the old system read-only until Jira Service Management passes non-admin proof. Name a rollback owner and maximum parallel window.
Worked example: Teams already on Jira Cloud who need a service desk caps parallel run at two weeks with daily checkpoint notes.
6. Verify counts and permissions after import
Reconcile user counts, role permissions, and a sample of migrated records. Research lists Slack, Microsoft Teams, Zapier, and API access for Jira Service Management. Confirm which are native vs API before go-live.
7. Inventory what must move into Jira Service Management
List users, historical records, templates, and integrations that must survive migration. Mark nice-to-have exports you can leave behind.
Worked example: Teams already on Jira Cloud who need a service desk migrates active records only and archives the rest as read-only exports.
8. Run parallel cutover with a rollback path
Keep the old system read-only until Jira Service Management passes non-admin proof. Name a rollback owner and maximum parallel window.
Worked example: Teams already on Jira Cloud who need a service desk caps parallel run at two weeks with daily checkpoint notes.
9. Verify counts and permissions after import
Reconcile user counts, role permissions, and a sample of migrated records. Research lists Slack, Microsoft Teams, Zapier, and API access for Jira Service Management. Confirm which are native vs API before go-live.
10. Inventory what must move into Jira Service Management
List users, historical records, templates, and integrations that must survive migration. Mark nice-to-have exports you can leave behind.
Worked example: Teams already on Jira Cloud who need a service desk migrates active records only and archives the rest as read-only exports.
11. Run parallel cutover with a rollback path
Keep the old system read-only until Jira Service Management passes non-admin proof. Name a rollback owner and maximum parallel window.
Worked example: Teams already on Jira Cloud who need a service desk caps parallel run at two weeks with daily checkpoint notes.
12. Verify counts and permissions after import
Reconcile user counts, role permissions, and a sample of migrated records. Research lists Slack, Microsoft Teams, Zapier, and API access for Jira Service Management. Confirm which are native vs API before go-live.
Frequently asked questions
Can we skip the dual-run?
Only if the dataset is tiny and reversible. Most SMB/mid teams regret skipping a week of parallel use.
What if history will not map cleanly?
Import active records first. Archive messy history as files rather than poisoning the new system of record.
Was this article helpful?
Have more questions? Contact our support team.
SoftwareGlimpse Updates
Want clearer software shortlists? Get buying guides and comparisons by email.
Newsletter coming soon.