Runbook for Atlassian Cloud Migration

Before project execution, complete the standard discovery steps for Jira and Confluence Cloud migration, with a focus on app compatibility, data quality, and tenant readiness for aipstraining.com.

• Review Atlassian system app dependencies, custom integrations, and unsupported customizations.
• Verify database collation compatibility, integrity checks, and schema assumptions.
• Review duplicate users, stale groups, malformed content, and inactive accounts.
• Assess custom fields, workflows, macros, and dashboard objects against Cloud support boundaries.
• Confirm site architecture, admin ownership, domain control, and migration execution sequencing.

Jira pruning

Remove stale projects, archived workstreams, and legacy issue data before migration to reduce complexity.

• Identify abandoned projects and move them into Data Center archival workflows.
• Review duplicate project keys, reused schemes, and stale automation rules.
• Retain only production-critical data in the candidate migration set.

Confluence pruning

Clean space inventory and remove unsupported content before the final migration run.

• Archive outdated spaces and obsolete pages no longer required by operations.
• Review custom HTML macros, corrupted layouts, and legacy page templates.
• Remove duplicate content and explain unsupported implementations to stakeholders.

Database pre-check 1: Jira duplicate emails

SELECT lower_email_address, COUNT(id)
FROM cwd_user
GROUP BY lower_email_address
HAVING COUNT(id) > 1;

Atlassian support reference: Find duplicate users by email and username

Database pre-check 2: Broken group structures

SELECT g.id,
       g.group_name,
       g.parent_id,
       p.group_name AS parent_group_name
FROM cwd_group g
LEFT JOIN cwd_group p ON g.parent_id = p.id
WHERE g.parent_id IS NOT NULL
  AND p.id IS NULL
ORDER BY g.group_name;

Use this query to isolate empty, orphaned, or dangling hierarchy records before provisioning group access in Cloud.

Database pre-check 3: Unsupported Confluence macros

SELECT s.spacekey,
       c.title,
       bc.contentid,
       bc.body
FROM bodycontent bc
JOIN content c ON bc.contentid = c.id
JOIN spaces s ON c.spaceid = s.id
WHERE bc.body ILIKE '%<ac:structured-macro%'
   OR bc.body ILIKE '%customhtml%'
   OR bc.body ILIKE '%html-macro%'
ORDER BY s.spacekey, c.title;

Atlassian support reference: Find pages and spaces using a specific macro

1. User management: Standardize global accounts, invitation flows, and identity verification.
2. Group architecture: Use a clear nested/flat access strategy mapped to business ownership.
3. DNS configuration: Verify ownership of aipstraining.com using TXT and CNAME records in Atlassian Admin.
4. User claiming: Set up automatic onboarding for users with @aipstraining.com addresses.
5. Authentication policy: Enforce SAML with Okta or Azure AD as the identity provider.
6. API token lifecycle: Enable or disable user-generated API tokens by policy and governance rules.
7. Service and functional accounts: Keep a separated policy for SSO-enforced user accounts and API-based service accounts.
8. Data security policy: Disable anonymous public access and block downloads on unmanaged devices.
9. Atlassian Rovo: Limit AI-first access to sandbox environments for evaluation and staging.
10. Sandbox provisioning: Create isolated staging instances matching production metadata.
11. Cloud site creation: Initialize primary and secondary production instances under the org umbrella.
12. URL customization: Provision vanity paths and custom mappings for user-facing cloud URLs.
13. Org API token controls: Restrict systemic API access to approved app and automation trust boundaries.
14. Administrative RBAC: Define strict boundaries between org administrators and site administrators.
15. Site onboarding & consolidation: Link newly created and legacy sites into a single corporate org model.
16. Enterprise AD sync: Configure SCIM directory sync to provision users and group membership from Active Directory.

Custom domain request flow in Atlassian Administration for app URL and DNS validation

Org Overview

Overview Directory Apps Security

Org aipstraining.com

Ready Cloud tenant active

Sites 2 production

Status Healthy

Organization overview for the Atlassian cloud tenant and migration readiness

Directory • Users

User	Type	Status
jsmith	Managed	Active
teamadmin	Admin	Verified
svc-bot	Service	Managed

Directory control for users, managed accounts, service accounts, and admins

Domains • DNS

TXT aipstraining.com

Verified Custom domain ready

CNAME www → cloud.atlassian.net

Status Active

Domain verification, DNS ownership, and user claim configuration for aipstraining.com

Security • SSO

Identity provider

Okta / Azure AD

SSO enforcement

Required for all users

Certificate

Valid, expiry monitored

Authentication policy and SAML enforcement model for enterprise user access

Directory • SCIM

User	Group	Status
jsmith	jira-admins	Synced
akim	confluence-editors	Synced
svc-bot	automation	Managed

SCIM directory sync and provisioned memberships for Active Directory-driven user onboarding

Apps • Access

Marketplace

Approved Atlassian apps

Sandbox

Staging environment

App Access

Restricted to org policy

Atlassian apps, marketplace access, sandbox controls, and site-level lifecycle management

Harden network access before and during migration by restricting traffic to the required Atlassian Cloud domains and validating egress control paths.

• Whitelist Atlassian Cloud egress destinations used by Jira, Confluence, and migration tooling.
• Review proxy, firewall, and WAF policies for Cloud API routes and custom domain access.
• Confirm secure access for admin and operational teams.

Migration failure troubleshooting

When migration tasks fail, check the following sources in sequence:

Integration setup

Preserve native Jira-to-Confluence app links before and after migration so that page connectivity and project references remain intact.

Phased migration strategy

• Establish the initial migration plan in Data Center and validate dataset scope.
• Split large migrations into manageable workstreams for optimization and error containment.
• Stage app, user, and project migrations in sequence instead of all at once.

Execution runbook

App-specific migration handling

Split app migrations from project migrations to isolate failure domains. If a plugin sync fails, perform a targeted re-run of the migration for the affected app or project set and validate data parity before continuing.