Atlassian and ServiceNow: migration, administration and support
Jira, Confluence and ServiceNow migrated, configured and looked after, so your teams work in the tools instead of around them.
- Timeline
- 2–12 weeks
- Flagship
- Data Center to Cloud migration
01Who it is for
- 01
Your Jira or Confluence runs on Data Center, which Atlassian retires on 28 March 2029.
- 02
Years of custom fields and workflows have made Jira slow and hard to change.
- 03
Nobody owns the tools, so admin work lands on whoever has a free hour.
- 04
You are choosing between Jira Service Management and ServiceNow and need a clear answer.
- 05
Teams were given the tools but never shown how to use them well.
02What’s included
Migrations
Jira and Confluence Server or Data Center to Cloud, instance merges, and moves from Redmine, YouTrack or spreadsheets into Jira or ServiceNow.
Configuration
Workflows, issue types, fields, automation rules, service catalogs, SLAs and integrations with your other systems.
Administration
Users, groups and permissions, apps, upgrades and licence housekeeping, handled by a named admin.
Maintenance & support
Health checks, performance tuning, backups and help for your users within agreed response times.
Training
Role-based sessions for admins, agents and end users, with recorded walkthroughs and short guides.
Consulting
Tool audits, licensing and edition choices, process design, and the Jira Service Management or ServiceNow question.
- Atlassian
- JiraConfluenceJira Service ManagementBitbucketTrello
- And similar
- ServiceNowZendeskFreshservicemonday.com
03How it runs
Bar length shows how long each stage usually takes.
- 01
Assess
Instance health, apps, customizations, users and licences.
1 week - 02
Plan
Target setup, migration or change plan, and replacements for apps that will not move.
3–5 days - 03
Execute
Test runs in a sandbox, checked by your key users, then production.
1–8 weeks - 04
Hand over
Training, admin guides and, if you want it, ongoing administration.
1 week
04What you get
- Instance health report: apps, fields, workflows and licence usage
- Migration or change plan, tested in a sandbox first
- Documented workflows, automation rules and permissions
- Training sessions and admin guides for your team
Ways to start
- Data Center to Cloud migration4–12 weeks
- Assessment and app audit
- Test migrations
- Cutover and user support
- Admin & support retainerMonthly
- Named admin for your instance
- Requests within agreed response times
- Monthly health report
- Training programme1–2 weeks
- Admin training
- Agent and end-user sessions
- Recorded walkthroughs
05Technologies
06Questions
When does Atlassian Data Center reach end of life?
Atlassian has announced that Data Center products reach end of life on 28 March 2029 and become read-only. Existing customers can no longer buy new subscriptions or expansions after 30 March 2028. Bitbucket and Bamboo Data Center are the exception.
How long does a Data Center to Cloud migration take?
Usually 4–12 weeks, depending on users, apps and customizations. The assessment in the first week gives you a firm timeline.
What happens to our Marketplace apps?
Before the migration we check each app for a Cloud version, a built-in replacement or a workaround, and test the result in a sandbox.
Do you work with ServiceNow too?
Yes: ITSM processes, service catalogs and SLAs, administration, integrations, and migrations into ServiceNow from other tools.
Can you train our team?
Yes. Sessions are built around your own workflows and roles (admins, agents and end users) and recorded, so new hires can use them too.
Tell us about the task.
We reply within 1 business day.
- 01An engineer, not a sales rep, reads your request.
- 02NDA before the first call, if you need one.
- 03A 30-minute call with an architect, in your time zone.