Practical resource

Manufacturing cloud migration checklist

A manufacturing cloud migration should inventory the business service, application, data, identities, interfaces, licenses, devices, network paths, backups, recovery needs, support owners, and factory continuity constraints before scheduling a move.

Illustrative technician reviewing production information beside a component inspection station
01

Understand

1. Application and business scope

01

Name the business service and accountable owner

02

Record application version, vendor support, users, peaks, and critical periods

03

Identify retain, retire, replace, rehost, or replatform decision

04

List acceptance criteria and functions that must not change

02

Understand

2. Dependencies and connectivity

01Map identity, DNS, certificates, file shares, databases, scheduled jobs, email, print, and time services

Record the decision, responsible owner, supporting evidence, and follow-up action.

02Record inbound and outbound flows with ports and owners

Record the decision, responsible owner, supporting evidence, and follow-up action.

03Include plant devices and vendor remote support

Record the decision, responsible owner, supporting evidence, and follow-up action.

04Test bandwidth, latency, outage behavior, and edge autonomy

Record the decision, responsible owner, supporting evidence, and follow-up action.

03

Apply

3. Data, licenses, and cost

ReferenceInput or decision to establish
01Measure data volume, growth, sensitivity, residency requirements, and transfer window
02Confirm application, operating system, database, virtualization, and user licenses
03Model compute, storage, backup, support, logs, network, egress, dual running, and internal labor
04Keep assumptions and taxes explicit
04

Apply

4. Identity, security, and operations

01

Use named identities and least privilege

02

Separate production and non-production environments

03

Enable appropriate logging, alert routing, patch, vulnerability, and change processes

04

Agree cloud-provider, software-vendor, client, and support responsibilities

05

Review

5. Backup and recovery

01Approve recovery point objective (RPO) and recovery time objective (RTO)

Record the decision, responsible owner, supporting evidence, and follow-up action.

02Include data, configuration, keys, identity, network, and integrations

Record the decision, responsible owner, supporting evidence, and follow-up action.

03Run a restore test before relying on the target

Record the decision, responsible owner, supporting evidence, and follow-up action.

04Record recovery sequence, decision authority, and communications

Record the decision, responsible owner, supporting evidence, and follow-up action.

06

Review

6. Cutover, rollback, and handover

  1. 01
    Rehearse migration and measure the windowDefine evidence and the exception path
  2. 02
    Define go/no-go and rollback triggersDefine evidence and the exception path
  3. 03
    Prevent duplicate transactions during transitionDefine evidence and the exception path
  4. 04
    Reconcile data and interfacesDefine evidence and the exception path
  5. 05
    Train support roles, transfer runbooks, and schedule the next recovery testConfirm ownership and handover
01

Start with one process

Which workflow currently costs your team the most time?

Bring one normal example and one exception. Use them to frame the systems, decisions, controls, and evidence a sensible next step needs.

Discuss your operation