Hi Community, We are preparing to migrate our Jira and Confluence Data Center instances to Atlassian Cloud. According to Atlassian's About FastShift documentation under Data access, customers choosing Hands-on backup support can: "provide Atlassian with access to self-managed data to be migrated, preferably by sharing a database backup." Our primary concern is migration performance and minimizing downtime windows. Could anyone from Atlassian or Community members who have completed FastShift clarify: * Does Atlassian officially support this in FastShift, can we share our database backup directly with Atlassian and have their team load the data into Cloud to accelerate migration, rather than us running the entire migration through JCMA and CCMA on our local servers? * If this is supported, how does Atlassian actually process that database backup on their infrastructure, is it a direct backend database restoration, or do Atlassian engineers rehost it and run JCMA/CCMA on their end Any insights, practical experiences would be greatly appreciated!

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can we send our Data Center database to Atlassian to accelerate Cloud migration via FastShift?

Aakash Kumaresan

Hi Community,

We are preparing to migrate our Jira and Confluence Data Center instances to Atlassian Cloud.

According to Atlassian's About FastShift documentation under Data access, customers choosing Hands-on backup support can:

"provide Atlassian with access to self-managed data to be migrated, preferably by sharing a database backup."

Our primary concern is migration performance and minimizing downtime windows. Could anyone from Atlassian or Community members who have completed FastShift clarify:

Does Atlassian officially support this in FastShift, can we share our database backup directly with Atlassian and have their team load the data into Cloud to accelerate migration, rather than us running the entire migration through JCMA and CCMA on our local servers?
If this is supported, how does Atlassian actually process that database backup on their infrastructure, is it a direct backend database restoration, or do Atlassian engineers rehost it and run JCMA/CCMA on their end

Any insights, practical experiences would be greatly appreciated!

Accepted answers

Gabriela - LeanZero

Hi Aakash, yes. Sharing a database backup is an official FastShift option, and Atlassian's roles and responsibilities page recommends it "for the fastest migration time", where you provide the backups and attachments and they handle the technical details. The same pages describe what happens to it: the backup is restored to an environment only a small group of Atlassian engineers can access, and from there they run the test and production migrations for you. The data sits on AWS with encryption at rest, and access is limited to designated engineers in Migration Support, Cloud Transition and Platform Engineering.

What the docs don't say is which tool they run on that restored copy, so I wouldn't assume either a raw database restore into your Cloud site or JCMA and CCMA behind the scenes. That's a question I'd put to your FastShift delivery manager early, together with backup format, transfer method and retention. I'd check eligibility first too. FastShift is for 1,000+ seats on Commercial Cloud, and you get in through your Atlassian Account Executive or your Solution Partner.

Small note, the "Data access" wording you quoted is on the "What is FastShift?" page, in case you're looking for it again.

All comments

Gabriela - LeanZero

Small note, the "Data access" wording you quoted is on the "What is FastShift?" page, in case you're looking for it again.

Aakash Kumaresan

Thanks for the detailed clarification and sharing the relevant FastShift information.

Josh

Yes — for FastShift with Hands-on backup support, Atlassian’s own docs say you can share a database backup (or otherwise provide access to self-managed data) so their migration engineering team can work from that rather than only from CMJ/CCMA traffic over the wire.

How to actually do it (high level):

Start / continue the Cloud migration path and select the FastShift / assisted option that includes hands-on backup support (this is arranged through Atlassian, not a self-serve Marketplace toggle).
Your Migration Manager / Atlassian contact will give the approved transfer method (secure upload, temporary access, etc.). Don’t email raw DB dumps unsolicited.
Prepare a consistent backup (Jira + Confluence DBs as they specify), note versions, and strip secrets you must not share if they ask for a scrubbed copy — follow their checklist.

FastShift eligibility and “hands-on” are scoped engagements; if you don’t already have an Atlassian migration contact, open a migration Support / Customer Success request referencing FastShift + hands-on backup support and your DC versions. Community can’t accept the DB for you — Atlassian will.