Planning cloud migration: systems, cutover and costs
A cloud move is not finished when the files have been copied. Applications, access and connections must work in the new environment. A defined scope makes preparation, transfer and support easier to compare.
What needs to move?
List servers, applications, databases and file stores. Moving an unchanged system differs from adapting its platform or replacing an application. Developing new functions is a separate task.
Not every system needs to move together. Applications tied to physical equipment or recently renewed systems may stay in place. An inventory can be the right first deliverable when the destination or feasibility is undecided.
Identify dependencies before comparing quotes
Record the databases, sign-in services and interfaces each application needs. A missed connection can disrupt work even when all data has transferred. Include local printers, specialist equipment and connections to external partners.
| Starting point | Define in the quote |
|---|---|
| Local server | Operating system, applications, storage and connected services |
| Existing cloud | Portability, contract end and work required from the current provider |
| Business application | Licence rights, interfaces and necessary adaptations |
| Mixed environment | Connections and responsibilities across both environments |
Define access and data processing
Decide who administers systems and who may read business documents. Accounts, permissions and additional sign-in protection belong in the plan. Passwords and confidential raw data do not belong in a quote request.
For personal data, review processing locations, subcontractors and contractual assistance. Clarify recovery and export arrangements. A Swiss hosting location does not replace checking these commitments.
Use a pilot and a rollback plan
Test a representative subset. Acceptable downtime and the final update determine the cutover method. A rollback plan needs a decision point and must account for changes made after the switch.
- Prepare. Record inventory, destination, owners and acceptable cutover window.
- Test. Check sign-in, data, interfaces and ordinary tasks in the pilot.
- Switch. Transfer final changes and explicitly approve the cutover.
- Accept. Document results before retiring old systems with the agreed safeguards.
Compare project and operating costs
Request quotes based on the same inventory. Data volume alone does not explain application changes or support. Parallel operation may incur both old and new charges.
| Cost item | Comparison question |
|---|---|
| Assessment and preparation | Which systems and dependencies are reviewed? |
| Transfer and cutover | Are pilot, final synchronisation and rollback planning included? |
| Cloud operation | Which storage, compute, licence and transfer charges apply? |
| Support and exit | What do support, export and a later handover cost? |
Check real working tasks
Agree success criteria before migration. An accessible server is insufficient if files are missing or a business transaction fails. Check permissions, data and normal workflows.
- Data. Document samples, quantities and the agreed completeness checks.
- Operation. Test interfaces, responsiveness and restoration.
- Responsibility. Name the contact, support hours and documentation access.
Plan follow-up and a future exit
Agree a limited support period after cutover. Outstanding faults need an owner and traceable progress.
Documentation, administrative ownership and a usable export make a later provider change easier. Review actual usage and bills before increasing capacity or accepting longer commitments.
Frequently asked questions
Does everything need to move?
No. Assessment may recommend a partial migration or temporarily retaining certain systems.
Can migration avoid all downtime?
That depends on applications, transfer and changing data. Test feasibility rather than relying on a general promise.
Is a small dataset simple to migrate?
A small application may still have complex interfaces or special licence conditions.
Are backups included?
Only within the agreed scope. State retention, recovery testing and responsibilities explicitly.
What information is needed initially?
System names, approximate quantities and volume, affected users and the desired period. Unknown technical details can be assessed.
Why is there no single migration price?
Preparation, adaptations, testing and parallel operation depend on the existing systems.
