For each cloud workload, name who owns the business process, which systems it depends on, how staff will accept the move and who can authorize a rollback.
Map the work behind the application
List the people who use the application, the data it reads, the systems it writes to and the network or identity services it needs. Include scheduled jobs, outside vendors and staff who work remotely. Identify a business owner who can say which tasks must work before the cutover can be accepted.
| Before cutover | What to verify |
|---|---|
| Representative use | An approved user can sign in and complete a critical task in the destination. |
| Permissions | The right people have access and an unauthorized user is refused. |
| Recovery | The team knows how to recover the agreed workload and who accepts the result. |
| Rollback | The decision time, responsible owner and handling of new work are written down. |
| Operating handover | Monitoring, billing, support and ownership of backups are assigned. |
Test the workflow, not just the login
For example, an office moving a shared application should test a normal transaction, an export, a scheduled job and the vendor support path. Record anything that differs from the old environment and decide whether staff can work around it. Ask the business owner to accept the representative task after the switch.
See Azure Files versus SharePoint when choosing where file workloads belong, and disaster recovery planning for the post-move responsibilities.
Bring the workload, its dependencies and the people who can accept the cutover. Explore NetSys cloud services.
Related reading
Discuss cloud services for your business.
Tell us about your current systems, the result you need and your timeline. We will discuss the work, responsibilities and pricing before you decide on an engagement.