Skip to content

Move a site here

Hosting is open to everyone.

A site here is a folder of files, published exactly as it is: nothing runs on our side, and nothing is built. So moving a site means getting its files out of the place it lives today and giving them to us, then moving the domain last.

In the console, Hosting has Move a site here beside New site. It asks where your site lives today and says what is on this page, in short. A place that can move opens New site on the way in it uses: Upload from your computer or From GitHub.

Netlify, Vercel, Cloudflare Pages or GitHub Pages

Section titled “Netlify, Vercel, Cloudflare Pages or GitHub Pages”

Your site is already a folder of files. Find the folder your host publishes: it is named in the site’s settings there, often dist, build, public, out or _site.

Nothing is built here, so we need the folder your host’s build produced, not the project it was made from:

  • If that folder is committed to your public GitHub repository, choose From GitHub and pick it. Publish a site from GitHub walks through the form.
  • If your host makes the folder on its side, run the same command on your own computer and choose Upload from your computer with the folder it makes.

Functions and form handling your host ran for you do not come along: nothing runs on our side.

  1. In your WordPress admin, install a plugin that exports the site as static HTML, and run its export.
  2. Download the zip it makes, and in New site choose Upload from your computer and give it the zip.
  3. Open a few pages at the new address before you move your domain.

Comments, contact forms, search, logins and the admin pages stop working: they need WordPress running, and nothing runs on our side. What a plan takes in one upload is on Plans and limits.

  1. Download your site’s files from your host, with its file manager or over FTP, so that index.html is at the top.
  2. In New site, choose Upload from your computer and give it the folder, or a zip of it.

Anything your host ran for the site, such as PHP pages or a script behind a form, does not come along: we publish the files as they are.

A project made in one of these tools is not a site yet: it is the source a site is made from, and it has to be built into plain files first. Nothing is built here, so that step happens on your computer.

  1. Get the project out of the tool: download it as a zip, or connect it to GitHub and download it from there.
  2. In the project’s folder, run npm install, then npm run build. You need Node.js installed for that. It makes a folder of plain files, usually named dist or out.
  3. In New site, choose Upload from your computer and give it that folder, not the project.

If you are not sure the project builds into plain files, ask the tool first. Move a site here has a prompt to copy: it asks the tool to make the build produce one folder with index.html at the top that works without a server, and to list what needs a server.

Logins, databases, payments and anything else the project ran on a server do not come along: nothing runs on our side. If the project draws its pages in the browser, open it from its front page: an inner page opened by its own address shows “not found”.

A site like this cannot come as it is. We publish files and run no code of yours, so nothing that needs a server or a database works here.

If the site can be saved as plain HTML pages, save it that way and follow HTML files on any host. What hosting does not do yet says more about what is not run.

A site in a builder like these cannot come as it is: the builder keeps your site’s files and does not hand them out.

If your builder can export the site as HTML, export it and follow HTML files on any host.

Move the domain last, once the site is live at its oraicle.app address. Add your domain to the site under Manage, and before you change anything its box shows what the name has today: the old site’s records that our record replaces, the mail records that stay as they are, and how long the old site may keep answering after the change.