Migration timelines
Migration to Jira and Confluence Cloud will be implemented as per the following timelines.
Date(s) | Tool | Actions required | Downtime |
---|---|---|---|
02 Sep ’24 – 06 Sep ’24 |
Confluence Jira CEPJira (f.k.a GDSJira) |
1. SHIP-HATS team assigns Migration ticket(s) to Subscription Administrators (SAs) with updates and subscription details. 2. Verify and acknowledge the receipt of the Migration ticket. |
NA |
02 Sep ’24 – 06 Sep ’24 |
Confluence Jira CEPJira (f.k.a GDSJira) |
1. Agencies to Prepare for migration. 2. Review the ticket and define success criteria and share with the SHIP-HATS team. 3. Use the provided template from the Migration activity checklist. |
NA |
15 Nov ’24 |
Jira | Begin migration preparation and ensure all data is backed up for Jira DC. | Jira Data Center (DC) will be unavailable from 22:00 SGT to 23:59 SGT. |
16 Nov ’24 – 17 Nov ’24 |
Jira | SHIP-HATS team migrates Jira DC users to Jira Cloud. Jira DC Freeze Period: Jira Data Center in read-only mode. |
Jira DC in read-only mode during migration. |
18 Nov ’24 |
Jira | 1. Jira Cloud go-live. 2. Users to complete Post migration tasks. 3. Users can create new projects in Jira Cloud after gaining Atlassian Account access. |
No downtime. Jira Cloud is live. |
18 Nov ’24 – 31 Jan ’25 |
Jira | 1. Monitor BAU in Atlassian. 2. Sign off from Jira Data Center. 3. Jira DC remains in read-only mode until sign-off or decommissioned by end of Feb ’25. |
No downtime. |
22 Nov ’24 |
CEPJira (f.k.a GDSJira) Confluence |
Begin migration preparation and ensure all data is backed up for Jira and Confluence DC. | CEPJira (f.k.a GDSJira) and Confluence DC will be unavailable from 22:00 SGT to 23:59 SGT. |
23 Nov ’24 – 24 Nov ’24 |
CEPJira (f.k.a GDSJira) | SHIP-HATS team migrates CEPJira (f.k.a GDSJira) DC resources to CEPJira (f.k.a GDSJira) Cloud. CEPJira (f.k.a GDSJira) DC Freeze Period: CEPJira (f.k.a GDSJira) Data Center in read-only mode. |
CEPJira (f.k.a GDSJira) DC in read-only mode during migration. |
23 Nov ’24 – 24 Nov ’24 |
Confluence | SHIP-HATS team migrates Confluence DC resources to Confluence Cloud. Confluence DC Freeze Period: Confluence Data Center in read-only mode. |
Confluence DC in read-only mode during migration. |
25 Nov ’24 |
CEPJira (f.k.a GDSJira) | 1. CEPJira (f.k.a GDSJira) Cloud go-live. 2. Users to complete Post migration tasks. 3. Users can create new projects in CEPJira (f.k.a GDSJira) Cloud. |
No downtime. CEPJira (f.k.a GDSJira) Cloud is live. |
25 Nov ’24 |
Confluence | 1. Confluence Cloud go-live. 2. Users to complete Post migration tasks. 3. Users can create new spaces in Confluence Cloud. |
No downtime. Confluence Cloud is live. |
25 Nov ’24 – 31 Jan ’25 |
CEPJira (f.k.a GDSJira) | 1. Monitor BAU in Atlassian. 2. Sign off from CEPJira (f.k.a GDSJira) Data Center. 3. CEPJira (f.k.a GDSJira) DC remains in read-only mode until sign-off or decommissioned by end of Feb ’25. |
No downtime. |
25 Nov ’24 – 31 Jan ’25 |
Confluence | 1. Monitor BAU in Atlassian. 2. Sign off from Confluence Data Center. 3. Confluence DC remains in read-only mode until sign-off or decommissioned by end of Feb ’25. |
No downtime. |