Migrate from another platform

Use this guide when the source platform does not have a dedicated migration page.

Separate application behavior from platform behavior

Identify what belongs to:

Application source and framework
Build system and runtime
CDN, domain, and TLS
Security controls
Managed services
Observability
Deployment automation

Application code may transfer unchanged while platform-specific services require replacement.

Record the current build

Document:

Source repository
Root directory
Install command
Build command
Output directory
Runtime version
Environment variables
Generated artifacts

Record runtime dependencies

Inventory:

Functions and containers
Persistent processes
WebSockets and streaming
Background jobs, queues, and scheduled work
Local filesystem use and persistent disks
Native binaries
Region and private-network requirements

WebSockets are not supported on Easel today for typical framework deployments. Plan replacements before cutover when the application depends on them.

Record delivery behavior

Inventory CDN caching, invalidation, redirects, rewrites, headers, compression, image optimization, static assets, custom error pages, domain routing, and TLS.

Record managed services

Identify dependencies such as database, object storage, key-value store, message queue, authentication, email, analytics, feature flags, and secret managers.

Decide whether each service remains external or needs replacement. Easel does not replace those managed data services as part of a deploy.

Import and validate

Import the GitHub repository into Easel (or deploy with the CLI).
Recreate build settings and environment variables.
Use a non-production Easel URL until the Production validation checklist passes.

Cut over

Follow Domain cutover and prepare Migration rollback before changing traffic.