// Use case / Migration deployment

Move the app. Keep the agent workflow.

Give your agent an appropriate migration Skill to inventory a running application, map its dependencies and prepare it for a new target—from another hosted platform to public cloud, edge or self-hosted infrastructure.

Migration still depends on source access, data portability, provider APIs and application-specific constraints. AgentDeploy makes the target deployment and cutover process controlled and observable.

migration pathcontrolled workflow
01 / sourceRunning applicationFrontend, backend, data and connectors
02 / inspectAgent + migration SkillInventory dependencies and constraints
03 / mapTarget planRuntime, resources, network and secrets
04 / verifyPreviewValidate the new environment
05 / cutoverApproved cutoverMove traffic with a rollback path
Inspect first, reproduce the required environment, verify it separately and cut over only after the target is ready.

// A migration is more than copying code

Map the whole application before moving traffic.

The Skill should help the agent distinguish portable source from provider-owned services, then turn that inventory into an explicit target architecture.

01 /

Inventory the running system

Identify frontend output, server processes, databases, object storage, authentication, scheduled jobs, domains and external connectors.

02 /

Translate dependencies

Map each provider-specific component to a supported runtime, provider service, external service or self-hosted replacement.

03 /

Verify before cutover

Create a separate target, test behavior and data paths, then move traffic with production approval and a documented rollback route.

// Migration inventory

What the migration plan should make visible

Source and buildRepository access, export format, build commands and generated assets.
State and dataDatabase ownership, backups, transfer method, consistency and downtime limits.
ConnectionsDomains, identity, webhooks, third-party APIs, secrets and network routes.
Target constraintsRuntime compatibility, capacity, region, self-hosted prerequisites and operating ownership.

// What this changes

Less lock-in pressureChoose a new target based on the application’s actual needs.
Safer changeoverKeep the old environment serving while the target is verified.
Agent continuityContinue working through Codex, Claude or another supported client.
Clear limitsSurface components that need manual export, redesign or provider cooperation.

// Next step

Start with an inventory, not a cutover.

Connect your agent, select the right migration Skill and produce a target plan that can be reviewed before infrastructure changes begin.