In this article
A complete migration includes files, image, parameters, permissions and a tested next step. A copied directory alone does not reproduce a working instance.
Move data between Vast.ai instances through supported data-movement tools or an appropriate SSH-based copy. Before deleting the source, verify both the files and a small run on the destination. File transfer does not automatically move template settings, secrets or process state.
Select a supported transfer route
The official guide distinguishes instance, local and cloud-storage movement, with different behaviour for Docker instances and VMs. Certain built-in operations can work with stopped instances under documented constraints. Do not assume they are equivalent to every manual SSH transfer.
Record source and destination type, access method, data size and state. An SSH tool needs a working connection to the relevant endpoint. A console operation needs the documented support for that resource state. Check the route before the source’s rental window becomes short.
Keep files separate from the launch recipe
Inputs, edited results, code, image and launch parameters are separate migration components. A directory does not recreate environment variables or an on-start script set in the panel. Preserve those as an explicit recipe.
Use a known image version and meaningful paths. Move secrets through a managed access process rather than including live tokens in a shared archive. Preserve required variable names so the next operator knows what must be supplied.
Test a larger destination disk
Suppose the next research stage no longer fits the original allocation. Create a suitable destination and stop writers before copying important data. Keep the source available while acceptance is still incomplete.
| Stage | Evidence to preserve |
|---|---|
| Destination preparation | Working access and sufficient space |
| File transfer | All required directories present |
| Integrity check | Matching sizes or checksums |
| Application check | A small input produces a valid result |
| Source completion | Destination works independently |
Also check ownership and permissions under the intended user. A file existing on the destination does not guarantee the application can read or update it.
Account for time and bandwidth
Transfer charges have placement-dependent conditions and exceptions. Do not call all instance-to-instance movement free. Include volume, route and the overlapping lifetime of two resources in the estimate.
Measure a representative sample; many small files can behave differently from a single archive. Finally, open the latest result and execute a small next step on the destination. Confirm it does not depend on an old path or a secret available only in the former session, then update connection information and retire the source deliberately.
Turn the check into a practical next step
A complete migration includes files, image, parameters, permissions and a tested next step. A copied directory alone does not reproduce a working instance.
For the documented details, consult the primary documentation; configuration reference. Continue with vast ai instance lifecycle stop destroy and vast ai template environment variables.