Migrate from Netlify

Netlify and Easel both support Git-based deployments and previews, but their deployment terminology and configuration files differ.

Easel does not automatically import netlify.toml, _redirects, or _headers. Translate those settings into Easel project settings and framework-native configuration.

Concept mapping

Inventory Netlify configuration

Review:

• netlify.toml, _redirects, _headers
• Build command, publish directory, base directory
• Build contexts and environment variables
• Functions and Edge Functions
• Scheduled and background functions
• Forms, Identity, Blobs, Large Media, Image CDN
• Plugins and split testing
• Traffic Rules, rate limiting, deploy protection
• Log drains and integrations

Mark every Netlify-specific capability as supported differently, requires external replacement, not required, or unsupported.

Import the repository

Import the GitHub repository into Easel.

Map:

Netlify base directory → Easel root directory
Netlify build command → Easel build command
Netlify publish directory → framework or Easel output setting
Production branch → Easel Production branch

Review the matching framework guide.

Translate build and routing

Move build settings to the Easel project.

Translate redirects and headers from _redirects / netlify.toml into:

• Framework routing (preferred when the framework owns the routes)
• Application redirects
• Domain redirects when the rule is hostname-level
• Security headers or framework header config

Validate status codes, wildcards, SPA fallbacks, and proxy-style rewrites carefully. Behavior will not match Netlify one-for-one without testing.

Functions

Compare Netlify Functions with Easel Functions:

• Request and response API
• Runtime and bundling
• Duration and region
• Environment variables
• Background and scheduled execution

Netlify-specific APIs require code changes or an external replacement. Scheduled and background Netlify functions are not first-class Easel products; use an external scheduler or queue when needed.

Edge Functions

Review every Edge Function for runtime APIs, geographic assumptions, cookies, headers, rewrites, and streaming. Use framework middleware or Node.js functions on Easel only after compatibility is confirmed for your stack.

Netlify Forms and Identity

These are application services, not ordinary deployment settings.

Replace them with application-owned forms and API routes, an external form provider, an authentication provider, or a database-backed implementation.

Do not treat a successful static build as proof that these services were migrated.

Observability and drains

Use Observability and Logs. Customer log drains are not available yet. See Export.

Validate and cut over

Complete the Production validation checklist, then follow Domain cutover.

Keep the Netlify site and published deploy available until the rollback window has passed.