Atlassian Cloud Migration Architect

Role: Atlassian Cloud Migration Architect

Location: Oaks, PA (Hybrid)

Type: Contract

Role Summary

• We are looking for a highly experienced, hands-on Atlassian Architect with proven experience designing and executing large-scale Jira, Jira Service Management (JSM), and Confluence Data Center to Atlassian Cloud migrations.
• This is not a Jira administration-only role. The architect must have strong knowledge of the internal functioning of the Atlassian platform, migration tooling, application/data models, authentication and identity architecture, marketplace applications, ScriptRunner/customizations, APIs, automation, licensing, security, and Cloud platform constraints.
• The ideal candidate will have personally participated in multiple enterprise Atlassian migrations and be capable of independently assessing an existing Data Center estate, identifying migration blockers, defining remediation strategies, designing the target Cloud architecture, running migration rehearsals, troubleshooting failed migrations, and leading production cutovers.
• The architect is expected to work closely with customer platform teams, application owners, security/IAM teams, Atlassian, Marketplace vendors, testing teams, and business stakeholders.

Required Experience

• 10+ years of overall IT experience preferred
• 6+ years of hands-on Atlassian platform experience
• 4+ years of strong Jira and Confluence administration/architecture background
• 4+ years of proven Data Center to Atlassian Cloud migration experience
• Experience participating in at least 2–3 enterprise-scale DC-to-Cloud migrations
• At least one migration where the candidate had significant technical ownership
• Hands-on JCMA and CCMA experience having led at least one Atlassian DC- to-Cloud migration project
• 3+ years of experience migrating Marketplace applications, Strong ScriptRunner understanding, Strong REST API knowledge, Experience troubleshooting migration failures, Experience working with enterprise IAM/SSO solutions
• Strong knowledge of Atlassian Cloud architecture and administration
• Experience defining migration waves and cutover plans
• Ability to communicate architecture and migration risks to both technical and executive stakeholders

Key Responsibilities

• Data Center to Cloud Migration Architecture (5+ Years of Experience)
• Own the end-to-end technical architecture and migration strategy for: Jira Software Data Center, Jira Service Management Data Center, Confluence Data Center, Atlassian Marketplace applications, Custom integrations and applications, Identity and access management, Automation and scripting, Data and configuration migration
• Develop migration strategies using: Jira Cloud Migration Assistant (JCMA), Confluence Cloud Migration Assistant (CCMA), Atlassian-supported migration tooling, Atlassian APIs, Marketplace application migration capabilities, Custom migration utilities/scripts where required.
• Define and execute: Discovery and assessment, Migration readiness analysis, Cloud suitability assessment, Data cleanup strategy, Application/plugin assessment, Migration wave strategy, Pilot migration, UAT migrations, Production migration, Delta migration strategy, Hypercare and stabilization
• Design migration approaches for very large Atlassian estates involving: Thousands of projects/spaces, Millions of Jira issues, Millions of Confluence pages, Multi-terabyte attachment repositories, Thousands of workflows, Large numbers of custom fields, Complex permission schemes, Large user populations, Multiple Marketplace applications
• Deep Jira / Confluence Platform Knowledge (3+ Years of Experience)
• The architect must understand how Jira and Confluence work beyond the UI/admin console.
• Expected Jira knowledge includes: Projects and project configuration, Company-managed vs team-managed projects, Issue types and issue type schemes, Workflows and workflow schemes, Workflow conditions, validators and post-functions, Screens and screen schemes, Field configurations, Custom fields and contexts, Custom field performance implications, Permission schemes, Notification schemes, Project roles, Groups and users, Components, Versions/releases, Issue links, Filters and dashboards, Boards and Agile configurations, JQL, Jira Automation, REST APIs, Webhooks, Assets / CMDB concepts, JSM request types and portals, JSM queues, SLAs, Forms, Knowledge management, Customer vs licensed-user concepts
• Expected Confluence knowledge includes: Spaces, Pages and page hierarchy, Attachments, Permissions, Space permissions, Global permissions, User/group permissions, Macros, Marketplace macros, Templates, Page properties, Content properties, External integrations, Large attachment migration, Broken macro remediation, Application links and integrations
• Marketplace Application / Plugin Migration (3+ Years of Experience)
• Perform detailed assessment of Marketplace applications used within the Data Center estate.
• For each application, determine: Cloud equivalent availability, Data residency requirements, Cloud feature parity, Migration path, Vendor-provided migration tooling, Data migration support, Manual remediation requirements, Licensing impact, API differences, Functional gaps, Security implications, Replacement options.
• The architect should have practical experience with commonly used Atlassian applications such as: ScriptRunner, Xray, Zephyr, Structure, BigPicture, Tempo, Elements, Rich Filters, eazyBI, Configuration Manager, JSU, JMWE, Power Scripts, Refined, Insight / Assets, Advanced Roadmaps, Table/Grid applications, Reporting and dashboard applications, Experience troubleshooting Marketplace application migration failures is highly desirable.
• ScriptRunner & Customization Expertise (3+ Years of Experience)
• Strong knowledge of ScriptRunner for Jira is required.
• The candidate should understand: Groovy scripts used within Jira Data Center, ScriptRunner scripted fields, Behaviors, Listeners, Workflow functions, Conditions, Validators, Post-functions, Scheduled jobs, REST endpoints, Script fragments, Custom JQL functions, Scripted automation, External system integrations
• The architect must understand that Data Center scripts generally cannot simply be moved unchanged to Cloud.
• Must be capable of assessing individual scripts and recommending: ScriptRunner Cloud equivalent, Jira Automation replacement, Forge application, Atlassian REST API implementation, Marketplace application replacement, External microservice / integration, Functional redesign, Retirement of obsolete, customization.
• Should understand differences between Data Center and Cloud execution models including: Groovy vs Cloud execution models, API-based access, Authentication, execution limits, asynchronous processing, rate limits, data access restrictions, Cloud security boundaries
• Custom Application & Integration Architecture (3+ Years of Experience)
• Assess custom-built Jira/Confluence integrations including: REST API integrations, Webhooks, Database integrations, LDAP integrations, CI/CD integrations, ITSM integrations, Monitoring tools, Reporting platforms, Data warehouse integrations, CMDB integrations, DevOps platforms
• Should have architecture experience with integrations involving platforms such as: ServiceNow, GitHub, GitLab, Bitbucket, Jenkins, Azure DevOps, Microsoft Teams, Slack, Power BI, Splunk, Identity providers.
• Must be able to recommend whether existing customizations should be: Migrated, Refactored, Replaced, Re-platformed, Retired, Knowledge of Atlassian Forge and modern Atlassian Cloud extensibility models is strongly preferred.
• Identity, SSO & User Migration (3+ Years of Experience)
• Design Cloud identity architecture covering: Atlassian organization, Atlassian Administration, Managed accounts, Domains, Domain verification, SAML SSO, SCIM provisioning, User lifecycle management, Atlassian Guard, MFA, Group synchronization, User migration, Deactivated users, Duplicate accounts, Email address changes, External/non-domain users, JSM portal customers, Experience integrating   
• Atlassian Cloud with enterprise identity providers such as: Microsoft Entra ID, Okta, Ping Identity, Other enterprise IdPs.
• Must understand the differences between: Data Center LDAP/AD user management, Atlassian Cloud accounts, Managed accounts, Product access, Application roles, JSM agents, JSM customers
• Atlassian Cloud Architecture (2+ Years of Experience)
• Design enterprise Atlassian Cloud environments including: Atlassian organizations, Sites, Products, Sandboxes, Production environments, Administration model, Security boundaries, Access control, Data residency, Marketplace application architecture, Cloud integrations, Backup/restore considerations, Business continuity considerations
• Understand important Cloud architecture differences and constraints compared with Data Center including: No direct database access, Restricted filesystem access, REST API-based integrations, API rate limits, SaaS release model, Marketplace application architecture, Cloud automation limits, Customization limitations, Platform guardrails
• Licensing & Commercial Understanding (2+ Years of Experience)
• Strong knowledge of Atlassian licensing and subscription concepts is required.
• Candidate should understand the commercial implications of: Jira, Jira Service Management, Confluence, Atlassian Guard, Marketplace applications, User tiers, JSM agent licensing, JSM portal customers, Cloud subscription plans, Sandbox environments, Premium / Enterprise capabilities, Marketplace application subscription models
• Should be able to perform licensing optimization by identifying: Active vs inactive users, Product access, Agent vs customer access, Duplicate users, Unnecessary application access, Unused plugins, Marketplace app cost impact
• Must be comfortable participating in conversations involving Atlassian licensing, subscription optimization and overall platform TCO.
• Migration Assessment (5+ Years of Experience)
• Lead detailed discovery of existing Atlassian estates. Assessment should cover at minimum:
• Jira: Number of projects, Issues, Attachments, Users, Groups, Custom fields, Custom field contexts, Workflows, Workflow schemes, Issue types, Screens, Permission schemes, Notification schemes, Automation rules, Filters, Dashboards, Boards, Versions, Components, Integrations, Marketplace applications
• Confluence: Spaces, Pages, Attachments, Users, Groups, Macros, Marketplace  macros, Templates, Permissions, Integrations
• Customization Assessment: ScriptRunner scripts, Custom plugins, Custom REST endpoints, Java plugins, Groovy scripts, Database integrations, External scripts, APIs, Webhooks, Reporting integrations.
• Produce a migration complexity heatmap classifying objects as: Standard migration, Configuration remediation, App-dependent migration, Custom migration, Redesign required, Unsupported, Retire.