Effort & cost calculation
What does the migration cost? Seriously, that can only be answered from the instance. That is exactly what the effort and cost calculation does — and it shows where our tools save time and budget.
- Makes the savings from our tools visible
- Computes from the real inventory, read-only
- An open, transparent calculation
- Read-only, no write access
- Evaluated against the Data Center original
- No interference with live operations
- Results documented transparently
The basis is your real inventory, not an estimate: the calculation reads your instance configuration, read-only and without ticket content, and rates every category individually.
At its core is a direct comparison: how much effort in pure manual work, how much with our tools? The difference shows exactly where our toolset saves time and budget — traceable from your numbers, down to the individual line.
What a standard migration leaves open
After a standard migration
- Effort is estimated and negotiated
- An assessment is usually just an extrapolation
- The quote is a black box
- A flat price
With this tool Effort & cost calculation
- Effort is computed from the inventory
- Founded on your real inventory, not extrapolated
- The calculation is open, position by position
- A model of phases and staffing costs
From instance to quote
Four steps, read-only and traceable.
-
1
Read the inventory
The configuration is read per endpoint from the data layer — the full inventory, not a sample.
Verified: Completeness reported per category.
-
2
Rate the effort
Each category is rated individually and given a complexity class.
Verified: Every unit assigned to a class.
-
3
Compute both scenarios
From the ratings come two cost models: one for pure manual work, one with our tools.
Verified: The savings are reported as the difference.
-
4
Create the quote
From the model an anonymised quote with an open calculation is created.
Verified: Every line traceable to a finding.
What it does
Shows the savings
The direct comparison of manual work and tool use makes visible how much time and budget our toolset saves in your specific case.
From your real inventory
The basis is the actual inventory of your instance, read-only and configuration only. Ticket content is never read.
Every category rated individually
Automation, workflows, scripted fields, service management, assets and filters each get their own complexity class.
A model of phases and costs
The individual ratings form a cost model by phase and staffing effort, traceable down to the category.
Open calculation
Hourly rates and effort values are open and adjusted per project. Nothing disappears into a black box.
Traceable and reproducible
The calculation is deterministic: the same inventory yields the same result, proven down to the individual line. That is more precise than an estimate and more reliable than hand-evaluated scripts.
Common questions before migrating
Is ticket content read in the process?
No. Only the configuration is evaluated — fields, workflows, automation, schemas, assets and filters. Issue content is never read, and access stays read-only throughout.
How are the savings proven?
From comparing two calculations of the same inventory: one done entirely by hand, one with our tools. The difference shows what using the tools saves in time and budget.
Can we follow the calculation?
Yes. Hourly rates and effort values are open and adjusted per project. There are no hidden assumptions.
How does the calculation relate to the assessment?
Both use the same data basis as the migration tools. So the quote matches the assessment and, later, the final report.
Safe and transparent
Reading separated from writing
Reads come from a read-only data layer; writes go through a single controlled channel. Read access never burdens your Cloud.
Evaluated read-only
Everything is evaluated read-only; nothing is written back into your systems. Operations and cloud budget stay untouched.
Repeatable without risk
Every step can be run again without doing harm. An interruption is no problem, and a second run creates no duplicates.
One isolated stack per customer
All tools run on the Jira Migration Manager platform, fully separated per engagement. No mixing of data.
All results are documented transparently and can be checked against the Data Center original. Nothing is silently changed or left out.
Runs on the Jira Migration Manager
This tool does not stand alone. It runs on the platform that unites every tool: a read-only read layer pulls Data Center and Cloud into a versioned snapshot, and every change goes through a single, controlled write gateway.
More on the Jira Migration ManagerMore tools
Migration platform
Jira Migration Manager
The platform that brings every migration tool under one roof and makes a Jira DC-to-Cloud migration safe and repeatable: separate read and write paths, rate-limited into the Cloud, credentials encrypted, one isolated stack per customer.
- Read-only read layer and rate-limited write channel kept strictly separate
- All tools on one shared data base, chainable into pipelines
- Token-secured perimeter, encrypted keystore, one stack per customer
Assets Migration
Asset Relink
Migrates Insight/Assets to the Cloud in full: fields and contexts, AQL filters, screens and the object values on every issue. Exactly where standard tools lose the links.
- Create fields, contexts and screens in the Cloud
- Translate AQL filters from Data Center to Cloud
- Relink object values on every issue
Managed Migration
Jira Migration Helper
JCMA migrates the bulk of your data but leaves configuration broken or unmigrated. Jira Migration Helper closes these gaps module by module and, with Managed Migration, runs the right fixes for each finished project automatically — every one dry-run by default and verified against the live Cloud API.
- Repair filters, dashboards, fields, roles and permissions that JCMA leaves open
- Managed Migration: automatically run the right fixes per project as it finishes
- Web UI or CLI, every module dry-run by default and secured by the idempotent write gateway
A fit for your migration?
Describe your case in a few lines — I'll tell you honestly whether and how this tool helps.
Book a callAtlassian ends support for Data Center on 28 March 2029. If you are moving a large, deeply connected environment, plan early rather than late.