Migration kickoff
How migration works
Migration is a headache for many people. After all, it is an important milestone on the way to the Atlassian Cloud, if not the most important. Therefore, it’s important to carefully prepare well for the migration process. With that said, you don't need to panic or procrastinate over fears that something might go wrong: knowledge and information can prevent (almost) all worries!
That’s why we’ve put together an overview of the migration process and how different responsibilities are divided between you, the customer, and Seibert Media. In the end, hopefully you realize that you've been worrying over nothing, because with just three steps, you can safely take off into the Atlassian Cloud!
3, 2, 1 - the countdown to a successful migration
Preparation phase
- Allowing access for Seibert Media consultants - Customer
- If it is available in the cloud, allow access as a user with site admin authorization
- For On Premise - allow access to system accounts with admin authorizations (Confluence Administrators Group, etc.)
- Assessing existing systems - Seibert Media
- Permissions
- Apps
- Configuration
- Clarify the procedure for creating cloud instances and licenses - Customer and Seibert Media
- Activate Cloud Migration Trial?
- Demo licenses for apps?
- When should cloud licenses be purchased (are offers available?)
- Name of the cloud instance
- Data residency
- Clarify use cases, apps and potential Feature Gaps - Customer and Seibert Media
- Work out a migration plan (with start date and duration) - Seibert Media
- Clean up the Server instance - Kunde
- Clean up users/groups
- Delete old apps
- Delete/archive old/empty Spaces
Test phase
- Test migration from Jira/Confluence - Seibert Media
- Estimate the time expenditure for migration (time window for productive migration) - Seibert Media
- Record possible errors and repairs - Seibert Media
- Refine the migration plan - Seibert Media
- If necessary a second test migration before going live - Seibert Media
- Testing users - Kunde
- Training employees on using the cloud (potential differences) - Kunde
Productive migration, rework, hypercare phase
- Plan the downtime (unavailability) and inform employees - Kunde
- Pre-migration steps - Seibert Media
- Productive migration - Seibert Media
- Rework - Customer and Seibert Media
Organizational
- Who is involved from the customer side?
- Project Managers
- Individuals who can test the content
- Technical contact individuals
- Appointments
- Next appointment: An update meeting after setting up user access and system assessment
- Regular appointments, if necessary bi-weekly
- Billing hours (monthly or according to project sections)
- Monthly billing, also provides an overview of hours
- Non Disclosure Agreement (NDA)
More about Atlassian Cloud
//SEIBERT/MEDIA GmbH
Luisenstraße 37-39, 65185 Wiesbaden