Skip to main content
Horton Scientific

Checklist · 9 min

Power Platform Migration Governance Checklist

A checklist for governing Power Apps and Power Automate during migration so legacy forms and workflows do not become a new unmanaged estate.

Governance checklist

  • Environment strategy: development, test, production, departmental, and migration environments.
  • DLP policy: business connectors, non-business connectors, blocked connectors, premium connectors, and exceptions.
  • Ownership: app owner, flow owner, business owner, support owner, backup owner, and service account owner.
  • ALM: solutions, environment variables, connection references, deployment pipelines, releases, and rollback.
  • Monitoring: failed flows, expired connections, orphaned owners, premium connector changes, and critical process alerts.
  • Support: runbooks, known issues, incident intake, triage, escalation, and change management.

Migration-specific controls

  • Every migrated app or flow should have a source process, target process, owner, validation owner, and support model.
  • Form Migrator and Flow Migrator outputs should feed the migration backlog and governance reporting.
  • Critical apps and flows should be reviewed after cutover and again after stabilization.

Migration software

Form Migrator

Inventory and plan legacy form migrations with Form Migrator

Form Migrator helps teams analyze InfoPath and legacy form estates, identify dependencies, and organize which forms should be converted, redesigned, simplified, or retired.

Migration software

Flow Migrator

Analyze and plan Nintex migrations with Flow Migrator

Flow Migrator analyzes Nintex workflow exports, identifies actions and dependencies, and helps teams organize supported conversions and workflows that need redesign.

Apply the guidance

Turn the resource into a plan for your environment

Horton Scientific can help validate the source estate, document the risks, and define the next delivery step.
Request an assessment