Guide

Cloud migration checklist

What to plan before moving to the cloud, in the order it comes up.

By the Ingenit team

A cloud migration succeeds mostly before the cutover. Here are the points to settle, in the order they come up, followed by a summary checklist you can reuse for your project.

Why prepare a cloud migration?

Migrating to the cloud means moving applications, data or servers from your premises to infrastructure rented from a provider. Difficulties rarely come from the provider’s technology: they come from a forgotten dependency between two applications, a poorly estimated cost, personal data hosted without checks, or a cutover with no way back. Methodical preparation deals with these risks one by one, before they cost you a service interruption.

1. Inventory the existing set-up

  • The applications, servers, databases and data volumes involved.
  • Who uses what, when, and what cannot stop.
  • Software licences and their terms of use in the cloud.
  • Current contracts: hosting, maintenance, telecoms.

2. Map the dependencies

  • Exchanges between applications, interfaces with partners, scheduled tasks.
  • What must move together, and what can wait.
  • User access: company network, remote access, secondary sites.

3. Choose a strategy for each application

StrategyPrincipleWhen to choose it
RehostMove the application as it isStable application, short deadline
ReplatformChange a few components, such as the databaseQuick gains without a rewrite
RefactorRework the application’s architectureStrategic application that must evolve
ReplaceSwitch to an online service (SaaS)Standard need, covered by the market
RetainKeep the application on premisesTechnical or regulatory constraints
RetireShut the application downApplication little or no longer used

A cloud architecture sized for your actual usage completes these choices. When part of it stays on premises, the architecture becomes hybrid: see our IT infrastructure services and our guide on choosing between on-premises, cloud and hybrid.

4. Deal with security and personal data from the start

  • Access and rights management, multi-factor authentication for administrator accounts.
  • Encryption of stored and exchanged data, access logging.
  • Data location: in which country the data is hosted and who can access it.

In Morocco, law 09-08 governs the processing of personal data, under the supervision of the CNDP; some processing must be declared to it or authorised, and transfers of data abroad are regulated. For data about people located in the European Union, the GDPR applies. Check these points with your legal adviser before choosing a hosting region. For security, see our cybersecurity and recovery services.

5. Estimate the full cost

  • Running costs, storage, backups, outbound data transfer.
  • Licences, provider support and monitoring tools.
  • The cost of the project itself: preparation, testing, running both set-ups during the transition.
  • Exit costs if you change provider.

Once in production, tag resources by project, set budgets with alerts and review unused resources every month: the cloud is billed by usage, so its costs have to be managed.

6. Plan the migration and the rollback

  • Successive batches, each with its own tests and rollback procedure.
  • A cutover window chosen with the business teams, outside critical periods.
  • A communication plan: who to inform, when, and what to do if something goes wrong.

7. Test, cut over, check

  • Functional and performance tests before the cutover, checks afterwards.
  • A verified backup before each step, and a tested restore.
  • A period of closer monitoring after each cutover.

8. Organise operations

Monitoring, updates, backups, cost control and support once in production: that is the role of managed IT services, or of your own team if it has the documentation and access it needs.

The checklist in short

  1. The inventory of applications, data and licences is complete.
  2. Dependencies between applications are mapped.
  3. Each application has a strategy: rehost, replatform, refactor, replace, retain or retire.
  4. The location of personal data has been checked (law 09-08, GDPR).
  5. Administrator access is protected by multi-factor authentication.
  6. The full cost is estimated, including transition and exit.
  7. Each batch has its own tests and rollback procedure.
  8. Backups are verified before each cutover.
  9. Operations after the migration are assigned and documented.
  10. Cost tracking is in place from the first month.

For support from inventory to operations, see our cloud migration services, or contact us.

A need on this topic?

Describe your context in a few lines: we come back to you with a first reading.

Book a call