Data Center goes read-only on 28 March 2029.
That is 930 days from today.
I help mid-sized companies move Jira, Confluence and Jira Service Management to Cloud before that date, with workflows, automations and history intact.
New customers can no longer buy Data Center.
Last day to buy or expand Data Center licenses and apps.
Licenses expire. Jira, Confluence and JSM become read-only.
What I do
Hands-on delivery for the parts of an Atlassian move that usually go wrong.
- Data Center to Cloud migrations
- Jira, Confluence and Jira Service Management, including app gap analysis, data cleanup, test migrations and cutover.
- Instance consolidation
- Merging several sites into one Cloud organization without breaking workflows, permissions or history.
- Jira Service Management
- Portals, request types, SLAs, Assets, and migrations from other service desk tools.
- Identity and access
- Entra ID, Active Directory, SSO and SCIM provisioning, set up so joiners and leavers are handled automatically.
- Custom apps and integrations
- When Atlassian Cloud does not do something out of the box, I build the missing piece: Forge apps, integrations and internal tools.
- Readiness assessments
- A fixed-price, two-week plan for your move to Cloud. How it works
Recent work
Client names are withheld. References are available on request.
European motorcycle manufacturer
Moved Jira and Confluence from Data Center to Cloud under J-SOX change controls, then handled post-cutover remediation, the identity move to Entra ID and decommissioning of the old servers.
International technology group
Consolidated three separate Jira and Confluence instances into one Atlassian Cloud organization, including SSO and SCIM provisioning.
US manufacturer
Replaced HaloITSM with Jira Service Management: customer portal, workflows, Assets and data migration.
European energy infrastructure company
Carve-out assessment for splitting one Atlassian Cloud estate into two separate environments, covering migration order, organization design and content classification.
About me
I'm Howard Nedd. Most of my time goes to the hard parts of moving to Cloud: instances with years of custom fields and scripts, identity setups tied to Active Directory, and service desks that can't go down during cutover.
You work with me directly, from the first call to the final cutover. For larger programs I team up with a small network of Atlassian partners.
I'm also a full-stack developer, so when Cloud doesn't do something out of the box, I can build the missing piece rather than write a workaround into a document.
- Languages
- English, Dutch, Spanish
- Based in
- Punta Cana, working with teams across Europe and the Americas
- Focus
- Jira, Confluence, JSM, Assets, identity, custom apps
Tell me about your instance.
A short email with your products, user count and main apps is enough to start. I'll come back with a first view on effort and risk.