Infrastructure movement becomes easier to reason about when it is part of the same orchestration model that already understands hosts and workloads. One-Click treats external migration as a Fleet import/export workflow rather than a separate migration product.

Use cloning when both systems are already peers

If source and destination are trusted Fleet members, the normal clone and restore paths already have the inventory and transport context they need.

Use export when the destination sits outside that trust boundary

Export creates a clear hand-off artifact for a workload so movement does not require extending controller trust merely to perform the transfer.

Import is a destination operation

The receiving side takes the package and places the workload into its new environment. The target can remain external or be enrolled into the Fleet afterward.

Do not confuse migration with backup

A backup exists so a system can be recovered. Import/export exists so a workload can be moved. Keeping those goals separate makes both workflows clearer.