Atlassian Cloud migration with virtual project management and weekly status updates for your Jira or Confluence server migrations.
Blended Perspectives provides virtual project management with weekly status updates for migration to Cloud.
Why Blended Perspectives?
As a Platinum Enterprise Partner, we have the trusted technical and business experience.
Ex-Atlassian Engineers to support you every step of the way.
Experience Counts – Migration is one of our day-to-day jobs, and we experience dealing with unexpected technical and functional challenges. Let us help you avoid those!
Why agile companies are moving to cloud:
- Reduce costs
- Save time
- Never upgrade again
- Work from anywhere
- Stay secure
- Increase agility
Based on your resolution to migrate, we evaluate your migration type, review your security and compliance requirements, evaluate and review any apps* and custom integrations you may have to determine what you’ll need for your Jira Cloud site. To help you through this, we’ve put together some advice and best practices.
*App data is not typically included in the backup when migrating from Jira Server to Jira Cloud. Some apps do have the capability to export and import their data but we’ll need to check with the app developers or their documentation to confirm if this is possible.
Prepare to migrate
Now that you’ve
Depending on the size of your organization and
At this stage, your migration communication plan should comprise items like:
- When will the migration take place?
What downtime can users expect?
- What will happen to the former site after migrating?
- Will it still be available or readable?
Prepare your Jira Server site – test your current environment to determine if you need to perform any changes before migrating your data.
Set up your Atlassian Cloud
Set up your organization
An organization allows you to view all the Atlassian Cloud users at your company in one place, manage your users’ accounts, and set up security features like SAML SSO. Organizations are essential if your company manages more than one cloud site and requires insight into all your sites, products, and the users who can access them.
Set up SSO
If you plan to use SSO in your cloud site, set this up in advance so it will continue running seamlessly for your users when you migrate.
Run a test migration and QA.
- Launch and on-board users
- Establish cloud security practices
- End-of-life old systems
- Make use of mobile apps
- Explore cloud apps and integrations
- Stay up to date
Cloud Migration Resources
A few tips on a successful Server to Cloud migration
- Planning: Planning is a key feature on all migrations. Establish a timeline, expected downtime, data validation, and post migration checks to
- Apps usage and features: Not all server apps are available on the Cloud. If you use an app that is not available on the Cloud, it is essential to access what the app does to find a relevant solution that will be available on the Cloud.
- Timing: Ideally
no more than30 days between testing and performing the actual migration (or as close as possible). Cloud is continually changing, keeping the testing and actual migration dates close helps to assure everything will run smoothly and no surprises happen.
- Have audience involved on the process: When moving from Server to Cloud some UI features change. It is imperative to engage the team on this process. Once the test migration happens, have the users to actually use the Cloud site and perform their everyday activities. This helps in getting them comfortable with the new platform and further helps with testing the migration (verify if all integrations, functionalities, and performance are working as expected).
- Testing the migration: When performing the test migration, review your cloud site to validate that everything works as expected (application links, app data, integrations, data creation (projects and issues for Jira and Spaces and pages for Confluence), verify if attachments
were migratedcorrectly and if they can be edited/deleted).
- Migration run-book: Document the test migration steps executed so they can
be executedrepeatedly on the actual migration.
- Documentation: Take notes on changes detected between your Server and your Cloud instances (this is useful for training your users during and after the actual migration.