Migration from Netlify to CreateOS
Use this guide when your app is currently deployed on Netlify and you want to move it to CreateOS.
What changes
| Netlify concept | CreateOS equivalent |
|---|---|
| Connected Git repository | GitHub repository deployment |
| Build command | Build command |
| Publish directory | Output directory or static build output |
| Environment variables | CreateOS environment variables |
| Netlify Functions | API routes, backend service, or separate CreateOS service |
| Netlify redirects | App-level redirects, router config, or proxy rules |
| Custom domain | CreateOS domain mapping |
Step by step
- Open the Netlify site settings and collect:
- Repository
- Production branch
- Build command
- Publish directory
- Environment variables
- Redirect rules
- Functions directory, if used
- Confirm the app builds locally with the same command Netlify uses.
- Sign into createos.sh/app.
- Click Deploy.
- Choose Import GitHub Repository and select the same repository.
- Choose Manual if you want to enter the exact Netlify build settings, or Build with AI if you want CreateOS to detect the framework.
- Add the build command and output directory.
- Add required environment variables.
- Deploy and open the CreateOS preview URL.
Functions and redirects
Netlify-specific features need a quick review before cutover:
- Move Netlify Functions into your app framework's API routes or a separate backend service.
- Move scheduled functions into CreateOS cron jobs if they are time-based.
- Recreate important redirects in the app router, framework config, or edge/proxy layer.
- Check any
_redirects,netlify.toml, and function-specific environment variables.
Cutover
- Verify the CreateOS deployment directly.
- Test static routes, API routes, forms, and redirects.
- Add the production custom domain in CreateOS.
- Update DNS after the CreateOS domain is ready.
- Keep the Netlify site active until the new deployment is stable.