I would plan around automated discovery and import rather than assume Azure Migrate can move a workload into a precreated VM. Check the supported workflow for your migration scenario before designing around that.
After migration, collect the resource IDs and generate import blocks for the resources your modules will own. Import only brings existing objects into state. It does not make the module configuration match them. You'll still need to map things like VM size, disks, network interfaces and settings to the module inputs, then review the plan for changes you don't intend.
For a large batch, that mapping and plan review are probably the bigger automation targets than the imports themselves.
7k!marblethimble_462:
That mapping is the part I'm most concerned about. The migrated resources need to fit established modules, not just exist in state.