Move from Netlify
Publish a Netlify site on Spacefast. netlify.toml build settings, redirects, and headers carry across when Spacefast builds the project
Spacefast reads netlify.toml and the _redirects and _headers files you already have, so a static or prerendered Netlify site usually moves with one publish.
Move the site
Create the Space
In the project directory, create an empty Space. Later publishes from this directory update it.
sf spaces create --slug my-siteBring the environment variables
Export the site’s variables from Netlify as a dotenv file, then import it before the first build so the build can read them.
sf env import .env --from netlify --space my-siteA line with an empty value fails the import, and empty values aren’t supported. Remove the line, or give the variable a real value. See Environment variables.
Publish the project
Run sf publish --space my-site in the project and let Spacefast build it. netlify.toml is read when Spacefast builds, so a folder you built yourself carries over only the _redirects and _headers files inside it.
sf publish --space my-siteTo build on every push instead, connect the repository with Publish from Git.
Check what was flagged
Anything Spacefast cannot convert is flagged at publish. Move it to a supported equivalent, or pass --allow-unsupported-platform-features to publish without it.
Point your domain
Add the domain to the Space and add the DNS records it asks for. Delete the address records that point at Netlify, because a leftover record blocks verification. Spacefast issues the certificate once DNS points at it. See Custom domains.
What carries over
| From Netlify | On Spacefast |
|---|---|
netlify.toml build command and publish directory |
Read after framework detection, and they override the detected build command and output directory |
Redirects and headers in netlify.toml |
Converted to _redirects and _headers rules |
_redirects and _headers files |
Published with your pages and applied as routing rules |
| Environment variables | Imported from a dotenv export with sf env import --from netlify |
The full rules for build detection are on Frameworks and builds. Rule order, conditions, and limits are on Redirects, rewrites, and headers.
What doesn’t
- Netlify Functions and edge functions. Move request handling to a Functions route or a supported framework’s server. Edge functions are flagged at publish.
netlify-cdn-cache-controlis rejected withheader_cdn_cache_unsupported. Spacefast manages shared caching;Cache-Controlstill applies to browsers. See Caching.- The
.netlifyfolder is dropped at publish, along withnode_modulesand.envfiles. See what gets uploaded.
Choose who can open it
A team’s new Spaces start private unless the team changed its default. Make the Space public, or share it with a link, in Spacefast Share.