Cloud Readiness Assessment
In two weeks you get a costed, step-by-step plan for moving Jira, Confluence or JSM from Data Center to Cloud. One you can put in front of your budget holder.
- Duration
- Two weeks
- Price
- Fixed, agreed before we start
- You get
- A written plan and a readout with your team
Existing customers can buy or expand Data Center licenses until 30 March 2028. Planning now keeps that date from becoming your deadline.
What you get
Everything you need to decide how, when and at what cost you move.
- App inventory
- Every Marketplace app mapped to its Cloud version, a replacement, or a gap you need to plan around.
- Customization audit
- Custom fields, workflows, ScriptRunner scripts and automations, sorted into what moves, what gets rebuilt and what can go.
- Identity plan
- How users, groups, SSO and provisioning work in Cloud, including Entra ID or Active Directory.
- Migration approach
- Sequence, test migrations, cutover and rollback, planned around your change windows.
- Estimate and risks
- Effort and cost for the migration, plus a risk register with owners and mitigations.
- Readout
- A 60-minute session with your team to walk through the plan and answer questions.
How it works
Kickoff
Day 1
We agree goals and constraints, and you give me a read-only admin account or exports.
Discovery
Days 2 to 6
I analyze your instance, apps and scripts, and talk to your admins and key users.
Plan and readout
Days 7 to 10
You receive the written plan and estimate, and we walk through it together.
Who it's for
Built for organizations of roughly 100 to 1,000 users. Atlassian offers self-service migration tools at this size, but no dedicated migration team.
- You run Jira, Confluence or JSM on Data Center.
- You rely on Marketplace apps or ScriptRunner and don't know what survives the move.
- Users sign in through Active Directory or Entra ID.
- Your service desk can't afford downtime during cutover.
Questions
Do you need access to our production system?
A read-only admin account is ideal. If your security policy doesn't allow that, exports and screenshots work too.
We use a lot of ScriptRunner. Is that a problem?
No. That's where most of the planning effort goes, and every script gets reviewed and classified.
Can you also do the migration?
Yes. The plan is also yours to use with any partner or your own team.
Which languages do you work in?
English, Dutch and Spanish.
Start with a 30-minute intro call.
We look at your setup together, and you get a fixed quote for the assessment afterwards.