Milestone tracker
As part of the FastShift program, you and your dedicated FastShift team will have to plan and agree on the key milestones of your migration.
Key milestones
A detailed Migration Timeline Planner will be provided within our collaboration space.
The following milestones are required as part of your migration journey. This is a linear process, and each milestone must be met before we can move forward to the next. You can copy this table into another page and add your notes.
Pre-migration checklists |
|
60-day migration check |
|
Successful end-to-end test |
|
Signed off UAT without blockers |
|
45-day migration check |
|
35-day migration check |
|
Runbook review |
|
Go/No-Go |
|
Migration date |
|
We prioritize support for migrations that have successfully completed the milestones on time. The days are calendar day, not working days.
We are unable to provide your production and post migration support unless each milestone is completed on time. The milestones are critical to the success of the migration, and if completed, barring issues, we will have increased confidence that you will have a successful migration.
Additional milestone details
Kickoff call: This is the introductory call that we use for introductions, to discuss the process, review the MSA, and to help set expectations.
Pre-migration checks: This is a public checklist, for each product, that must be completed to validate that your source instance is ready to migrate.
60-day migration checks: These are primarily the initial discovery questions. We must complete all 60 day checks before our 60th day, or else the migration will likely move out. These are critical to the success of the migration.
45-day migration checks: We have additional technical checks that we complete here, along with confirmation checks. This includes an initial successful data import, and which includes app data. We must complete all 45 day checks before our 45th day, or else the migration will likely move out. These are critical to the success of the migration.
35-day migration checks: These checks are critical in that we must commit to a migration date, and must be completed no later than 35 days out from the migration date.
Runbook review and Go/No-Go: These milestones must be completed no later than 9 days before your migration. Here we will review the runbook that was used for the latest successful test. The runbook must include all pre-migration and post-migration steps. There is a template in the collaboration space that can be modified and used.
If the runbook review and go no-go milestones are not completed on or before 9 calendar days, we cannot provide weekend support for your migration. The 9 days are calendar days, and not work days.
In summary, migrations are not easy, and every migration is slightly different from others. We want to ensure that your migration is successful and completed as scheduled. Your CMM is here every step of the way to provide you the support needed and advocate for you along the way. Our migrations team has managed many migrations and our best practices are tried and true. Through collaboration and TEAMwork, we will get you over that finish line and into Cloud successfully.
Was this helpful?