Move from another platform
Move a site to Spacefast from Netlify, Vercel, Cloudflare Pages, GitHub Pages, here.now, Glitch, or Val Town
Most sites move with one publish. Spacefast builds the same source, reads the config files other platforms leave in a project, and flags what it cannot convert. Pick the platform you are leaving.
Netlify
netlify.toml build settings, redirects, and headers carry across.
Vercel
vercel.json build settings, redirects, headers, and crons carry across.
Cloudflare Pages
_redirects, _headers, and wrangler.toml build settings carry across.
GitHub Pages
Connect the repository. Jekyll and other generators are detected.
here.now
Publish the same folder from the same agent.
Glitch
Publish the code you downloaded before Glitch closed.
Val Town
Move HTTP vals to Functions and scheduled vals to crons before Val Town closes.
What every move has in common
- Publish it. Hand Spacefast the source and let it build, so it reads your old platform’s config file, or publish the built output. Set environment variables on the Space before the first build. See Frameworks and builds.
- Check what was flagged. Platform features Spacefast cannot convert are flagged at publish. Move them to a supported equivalent, or pass
--allow-unsupported-platform-featuresto publish without them. - Choose who can open it. A team’s new Spaces start private unless the team changed its default. Make the Space public or create a share link with Spacefast Share.
- Point your domain. Add the domain to the Space and add the DNS records it asks for. Delete the address records that point at your old platform, because a leftover record blocks verification. Spacefast issues the certificate once DNS points at it. See Custom domains.