A dependency graph represents infrastructure resources and the relationships that determine how infrastructure-as-code changes are applied. During brownfield migration, reconstructing this graph turns live infrastructure into a reliable source of truth. section 2.2.2
Use dependency order to structure migration:
- Migrate accounts, provider isolation, service accounts, networks, subnetworks, routing, and root DNS first. section 2.2.2
- Migrate servers, queues, and databases after their supporting infrastructure exists. section 2.2.2
- Migrate orchestration platforms and application deployments after the compute layer. section 2.2.2
- Leave resources with the fewest dependencies, or those requiring server and database configuration, until later. section 2.2.2
Infrastructure migration
Reverse-engineer the networks supporting a database and server, write those configurations as code, then migrate the server and database resources that depend on them.




