You made a real site with Create.xyz. The hosted preview opens. Friends can click around. Now you want it on your side — your copy of the export, your place to run it, your passwords and keys. That is what this page is about. We help you move what you built so the hosted preview is no longer the only place it can live.
Leaving Create.xyz means this: you get your own copy of the export, you run it somewhere that is not the hosted preview, you move your passwords and your data with a plan, and you prove it still works before you tell everyone the new address. You are done when your site starts without opening the project editor.
Where people get stuck
A quick download is not a safe move
You do not always need every prompt draft. You do need to know what still lives inside project settings — and how people will sign in after the move.
Thinking “the same user list” is enough
People sign in with Google, email links, or a password. That sign-in needs its own plan. Copying a user list is not the same as someone opening the new site and getting in.
Changing your site address too early
Get the new place working first. Do not put secret passwords in the part of the site everyone can see. Certificates, sign-in links, and email must move together.
“We still have the Create project” with no real plan
A real way back means the old data can take new work again without splitting into two messy copies. Freeze what the host holds at switch time, and set a clock for how long you can go back.
Only testing the happy demo
Also try an old account, a brand-new signup, odd roles, empty screens, form submits, and old public links.
The calm order
List what the host still holds, practice the move, then switch
We do not change your site address just to look fast. We change it after a short written check and a practiced way back.
01
Label every pile: keep, copy, or toss
Decide what the hosted data and files own versus throwaway prompt seed. Missing labels surprise you when real people hit the new place.
02
Keep the sign-in links the project already made
Sessions, Google or email sign-in, passwords, and “I agree” records each get a line. A user list alone is rarely enough.
03
Practice the address and password move before customers leave the preview
Keep a sealed list of old and new secret names. Check certificates and old automatic messages, then rotate secrets after the new place can take traffic.
04
Sign a short “everything still works” note, then limit how long you can reverse
Name sample accounts, permissions, media, old links, and who can put the preview back in charge.
How to
How to leave Create.xyz without guessing
Move your records, secrets, and public links off the hosted preview. Success is a short “it still works” note plus a practiced way back.
Step 01
List what the host holds and label every kind of record
Keep, copy, or toss. Sign-in sessions, Google or email sign-in, passwords, and consent each get a line.
Step 02
Build the new place before you touch your site address
Keep old and new secret names in a sealed list. Secrets must not sit in the public part of the site. Plan sign-in allowlists, email, and return links as one set.
Step 03
Build test accounts the demo never used
Old account, new signup, odd roles, empty screens, forms, and old public paths.
Step 04
Replay real journeys and note where host data stopped
Compare what people see and side effects. Freeze the data shape at switch time.
Step 05
Stop host writes only after the “it still works” note is signed
Watch the first group on the new address. Support knows preview-era problems. Time-box going back.
Read next
Proof, the essay, and sibling intents
These pages are already on the site. Use them to pressure-test the bet before a call.
“What impressed us most about CodeCross was their ability to deeply understand our vision and translate it into a complete digital solution. Unlike many agencies that just focus on technical delivery, CodeCross approached our project like true partners.”
What should leave Create.xyz, and what can stay behind?
Take the thing you built — the export, a list of what it needs to run, and a note of how it starts. Leave preview caches, prompt clutter, and one-off test screens behind. Save your data (or how to reach it) on its own so nothing invents that shape later.
How do you make “it runs on Create preview” work somewhere else?
Write down the tools and settings the hosted preview had ready for you. Lock that list so a new machine gets the same setup. Replace “it worked because the host already had it” with that real list. Put the start command somewhere clear. The check should fail if the site only installs inside the project editor.
How should passwords and data move off the hosted preview?
Copy the names of your secrets from project settings into a template. Make fresh values on the new place — never put a host secret into your owned code. Point the site at the new data store and run the moves on a clean machine. Update sign-in return links that still point at the preview before you change your site address.
Why does “just download the export” break on a normal host?
A normal host is missing tools the preview hid for you. Start paths assume the editor folders. The one-click publish button is gone. Passwords arrive empty. Sign-in and live links still expect preview names. Fix install, how it starts, and secrets first — then move. Green inside the hosted preview does not mean portable.
Keep what you built. Move it on your terms.
Bring your project list, how people sign in, and a few test accounts. We put your site address last — and we name the preview path you can roll back to.