nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Strategies for painless data migration from Data Center to Government Cloud

Cassie Goss

Agencies consider the move to Atlassian Government Cloud, one of the biggest concerns is often the data migration process. Today, let's discuss strategies to make this transition as smooth and painless as possible.

Thorough Planning and Assessment

Conduct a comprehensive inventory of your data, apps, and customizations
Identify any potential compatibility issues or data that can't be migrated
Develop a detailed migration plan with clear timelines and responsibilities

Clean and Optimize Before Migration

Remove unnecessary data, inactive users, and obsolete projects
Standardize and normalize data where possible
Update and streamline customizations and workflows

Leverage Atlassian Migration Tools

Utilize Atlassian's Cloud Migration Assistant for Jira and Confluence
Take advantage of the Jira Cloud Site Import for larger instances
Use the Bitbucket Cloud Migration Assistant for code repositories

Test, Test, Test

Perform a trial migration with a subset of data
Validate data integrity and functionality in the test environment
Identify and resolve any issues before the full migration

Communicate and Train

Keep all stakeholders informed throughout the process
Provide training on any new features or changes in the Cloud environment
Develop user guides and FAQs for common questions

Gradual Migration Approach

Consider migrating in phases, starting with non-critical projects
This allows for learning and adjustment without risking critical operations

Maintain Parallel Environments

Keep your Data Center environment running alongside Cloud during initial stages
This provides a fallback option and allows for gradual user transition

Post-Migration Validation

Perform thorough checks to ensure all data has migrated correctly
Verify integrations, plugins, and custom functionalities are working as expected

Optimize for Cloud

Take advantage of Cloud-specific features to enhance performance
Reassess and optimize workflows for the new environment

Document the Process

Keep detailed records of the migration process
This will be valuable for future updates or assisting other agencies

Challenges to Watch For:
- Large attachments or datasets that exceed Cloud limits
- Custom apps or integrations that may not have Cloud equivalents
- User management and permission changes between Data Center and Cloud
Remember, Atlassian provides extensive documentation and support for Cloud migrations. Don't hesitate to reach out to their support team or engage with Atlassian Solution Partners for complex migrations.

We'd love to hear about your experiences with data migration. Have you already made the move to Government Cloud? Are you planning a migration? Share your stories, questions, or tips in the comments below!

Together, we can make the journey to Atlassian Government Cloud smooth and beneficial for all.

Comments

Mark Thomas_lf0f9c

We were given a quote so high that we plan to stay on DC until we are forced to leave. And then we'll consider all our options at that time.

Tanya Christensen

Great write-up @Cassie Goss

I love the clean before migrating guidance. Just like moving homes, do you take the trash with you? No. Not that historical content or work items are 'trash' but such data can be exported and archived offline instead of moving it to the cloud.

Darin - Opus Guard

+1 to the clean up before migration guidance, just to YES AND...

The migration presents a great opportunity to clean old records and better conform to the many government record keeping requirements that you may or may not be subject to. Particularly great about moving to Atlassian Government Cloud is an opportunity to also start fresh and get your document classification and retention schedules in place to keep your Confluence and Jira manageable and compliant.

An example simple solution is Content Retention Manager for Confluence (and Jira) which is one of the very few apps fully approved for Atlassian Government Cloud. No data leaves your environment, no external storage, and zero data egress, which is a requirement for many FedRAMP-sensitive teams.

Content Retention Manager is the missing piece to Atlassian Government Cloud if you are an agency or contractor that needs to conform to the various document retention/removal requirements as part of doing business with a government. Even if you're not subject to these requirements, it's still an inexpensive and elegant solution to keep risks and storage down.

Carla Ann Rowland

My concern is that the cloud migration tool strips soooo much from JSM that it is difficult to see the value. IL5 certification delay is having my government client move away from JSM/Jira in addition to the cost increase.