Inventory the running system
Identify frontend output, server processes, databases, object storage, authentication, scheduled jobs, domains and external connectors.
// Use case / Migration deployment
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.
// A migration is more than copying code
The Skill should help the agent distinguish portable source from provider-owned services, then turn that inventory into an explicit target architecture.
Identify frontend output, server processes, databases, object storage, authentication, scheduled jobs, domains and external connectors.
Map each provider-specific component to a supported runtime, provider service, external service or self-hosted replacement.
Create a separate target, test behavior and data paths, then move traffic with production approval and a documented rollback route.
// Migration inventory
// What this changes
// Next step
Connect your agent, select the right migration Skill and produce a target plan that can be reviewed before infrastructure changes begin.