# How to Migrate a ChatGPT Site to Revdoku

> Move a ChatGPT Site to Revdoku without missing files. Test a private preview, choose access controls, and safely retire the old Site.

TL;DR: To migrate a ChatGPT Site, ask ChatGPT to move all browser-ready files to a Revdoku bucket, publish and test a private preview, then restrict or delete the old Site.

![ChatGPT Sites page showing a published static website](/assets/en/blog/how-to-migrate-a-chatgpt-site-to-revdoku/chatgpt-sites-page.webp)

*The ChatGPT Sites page is the starting point for reviewing the Site you want to move.*

## Can you migrate a ChatGPT Site to Revdoku?

Yes, if the ChatGPT website uses static HTML, CSS, JavaScript, images, fonts, and downloads. Avoid rebuilding the page by hand: keep the Site open in its original ChatGPT conversation, connect Revdoku, and ask the agent to transfer the complete file tree.

This creates a separately hosted Revdoku copy but does not protect the original `chatgpt.site` URL.

OpenAI's [ChatGPT Sites guide](https://help.openai.com/en/articles/20001339) documents editing, publishing, audience controls, custom domains, and deleting a Site. It currently lacks a one-click website export workflow, so the prompt below asks the agent to inventory and copy the actual files.

## 1. Confirm that you can move the ChatGPT website

A straightforward static migration contains files such as:

```text
index.html
assets/
styles.css
app.js
logo.webp
downloads/
guide.pdf
```

Pause if the ChatGPT Site depends on a platform database, server-only function, secret key, authenticated API, or other hosted service. Static files can move, but a backend must be replaced or hosted separately.

Before uploading, remove API keys, private prompts, customer records, and local file paths.

## 2. Connect ChatGPT to Revdoku

In the ChatGPT conversation containing the Site:

1. Follow [Revdoku's AI connection instructions](https://revdoku.com/prompt.md).
2. Connect `https://app.revdoku.com/mcp`.
3. Complete Revdoku OAuth.
4. Ask ChatGPT to verify that the Revdoku tools are available.

Never paste a Revdoku password or API key into the conversation.

## 3. Tell ChatGPT to copy every file to Revdoku

Paste this prompt while the Site is attached or open:

```text
Copy this complete static website to a new Revdoku bucket.

Requirements:
1. Include index.html and every HTML, CSS, JavaScript, image, font,
document, and data file used by the website.
2. Preserve the folder structure and all relative paths.
3. Do not copy secrets, API keys, private prompts, environment files,
customer data, or local computer paths.
4. List the source files before transfer.
5. Upload every file to Revdoku, then compare the source and destination
file counts and report anything missing.
6. Keep index.html at the website root.
7. Publish a Revdoku preview first. Do not make the website public yet.
8. Open the preview and check navigation, images, scripts, downloads,
mobile layout, and broken links.
9. Tell me whether the website should use static or SPA routing.
10. Stop and ask me before the final publish or before changing the
original ChatGPT Site.
```

Inventory matters: a page may initially look correct while a secondary image, font, download, or route is missing.

![Static website files copied into a Revdoku bucket](/assets/en/blog/how-to-migrate-a-chatgpt-site-to-revdoku/revdoku-static-site-files.webp)

*Check the destination bucket for the complete folder structure before publishing.*

## 4. Review the migrated ChatGPT Site on Revdoku

Check the preview in both private and normal browser sessions:

- Open the homepage and every navigation item.
- Reload a nested route directly.
- Test buttons, forms, downloads, and outbound links.
- Check desktop and mobile widths.
- Confirm that no secret or private source file is exposed.
- Verify that the browser console does not show missing assets.

Use SPA mode when a client-side router serves several paths from one `index.html`; use static mode when each path has its own HTML file.

## 5. Choose access and publish the ChatGPT Site on Revdoku

Choose the audience before publishing:

- **Public** for work intended for anyone.
- **Password** for a shared client gate.
- **Verified email** when visitors should prove their identity.
- **Email allowlist** when only named people or approved domains should enter.

Protected Revdoku links can record page views, clicks, and downloads and send visitor notifications. When the Site changes, replace its files and republish at the same URL.

For more detail, see [How to password protect a ChatGPT Site](https://revdoku.com/blog/how-to-password-protect-a-chatgpt-site/) and [ChatGPT Sites vs Revdoku](https://revdoku.com/compare/chatgpt-sites/).

## 6. Restrict the old Site after you move the ChatGPT website

Only do this after the new link passes every test:

1. Open the original Site in ChatGPT.
2. Open **Share** and select the narrowest audience available, or delete the Site if it is no longer needed.
3. Test the old URL while signed out.
4. Update links, bookmarks, campaigns, and your custom domain.
5. Share only the Revdoku URL with the intended audience.

Previously public pages may remain in search snippets or saved copies for a while. Our [Google indexing check for ChatGPT Sites](https://revdoku.com/blog/can-chatgpt-sites-show-up-in-google-what-site-chatgpt-site-r/) explains why sensitive material should be removed before public publishing.

## Manual fallback to move a ChatGPT website: ask for a ZIP

If the current interface cannot write to Revdoku, ask ChatGPT to package the same complete static file tree as a ZIP. Review the downloaded ZIP, then upload it to a Revdoku bucket. Copying only the rendered public page can miss generated assets, source files, and routes.

## Migration checklist

Before completing the move, confirm:

- `index.html` is at the published root.
- The source and Revdoku file inventories match.
- Relative links and assets work.
- No secrets or private data were shipped.
- The correct static or SPA mode is selected.
- The intended access gate appears before content loads.
- The old Site is restricted only after the replacement works.

The independently hosted Revdoku copy can keep one link while you update its files, access rules, and client-facing content.

Publish & Update Websites

For FREE, right from your AI app:

ChatGPT
Claude
Gemini
Copilot
Cursor
Antigravity
Grok
Perplexity
DeepSeek
Codex
OpenClaw
CLI

Forms with notifications, analytics, and your own domain included.

Copy prompt

Review the prompt

· or ·
→ Create a free account

👩🏻
🧑🏽
👨🏿
👩🏼
🧑🏾

Join 100+ people who recently signed up

## Frequently Asked Questions

### Can every ChatGPT Site be migrated to Revdoku?

Sites made from browser-ready HTML, CSS, JavaScript, images, fonts, and downloadable files can usually be migrated directly. Sites that depend on databases, server-side functions, authentication services, or secret API keys require those backend components to be replaced or hosted separately.

### How can I make sure no files are missed during migration?

Inventory the complete source file tree before uploading, then compare the source and destination file counts. Test secondary pages, images, fonts, downloads, scripts, and nested routes because a homepage can appear correct even when supporting files are missing.

### What information should I remove before copying the Site?

Remove API keys, passwords, environment files, private prompts, customer records, and local computer paths. Review both visible pages and supporting files to ensure confidential material will not become downloadable or publicly accessible.

### Should I use static or SPA routing on Revdoku?

Use static routing when each URL has its own HTML file. Use SPA routing when a client-side router handles multiple paths through a single root `index.html`, and verify the choice by directly reloading a nested URL.

### What should I test before publishing the migrated Site?

Check every navigation item, button, form, download, outbound link, and nested route on desktop and mobile. Also inspect the browser console for missing assets and confirm the access gate appears before protected content loads.

### Which Revdoku access option should I choose?

Use public access for content intended for anyone, a password for a simple shared gate, verified email for identity confirmation, or an email allowlist for specific people or domains. Test the selected access mode in a signed-out or private browser session before sharing the link.

### When should I restrict or delete the original ChatGPT Site?

Wait until the Revdoku copy has passed all checks and the new URL is ready for its intended audience. Then restrict or delete the original Site, test its old URL while signed out, and update bookmarks, campaigns, shared links, and any custom domain.

---

[View the canonical page](https://revdoku.com/blog/how-to-migrate-a-chatgpt-site-to-revdoku/) · [Browse llms.txt](https://revdoku.com/llms.txt)