Softgen · You keep what you built
You made something real on Softgen. The hosted preview opens. Friends can try it. Now you want it on your side — your export of the code, 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 preview host is no longer the only place it can live.
30 min · senior team · leave with a clear next step
Company-level evidence
Review methodologyIn plain words
Leaving Softgen means this: you hold an export you can build, you run it somewhere that is not the preview host, 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 app starts without opening the Softgen project.
Where people get stuck
Pretty screens leave Softgen easily. Identities, media, and path assumptions the preview still holds do not — unless you plan them.
People sign in with Google, email links, or a password the host brokered. That sign-in needs its own plan. A Softgen user id alone rarely opens the new door.
Get the new place working first. Preview keys must not land in the public app “just for the weekend.” Certificates, sign-in links, and email move together.
A real way back means the old project can take writes again without split-brain. Freeze the data shape at switch time, and set a clock for how long you can reverse.
Also try an old account, a brand-new signup, odd roles the host assigned, empty states, stored files, and paths that matter for search.
The calm order
We do not change your site address just to look fast. We change it after parity fixtures pass and a practiced way back exists.
01
Authoritative data versus disposable demo seed. Missing labels surprise you when real Softgen-era users hit the new place.
02
Sessions the host made, OAuth it brokered, passwords if any, and consent flags each get a line.
03
Sealed Softgen-to-destination secret map. Lower TTL, check certificates and era webhooks, then rotate secrets after the new place can take traffic.
04
Sample accounts, permissions, media, SEO paths, and who can put Softgen back in charge.
How to
Move records, secrets, and public URLs. Success is a parity note plus a practiced way back.
Step 01
Keep, copy, or toss. Sessions, OAuth subjects, passwords, and consent each get a line.
Step 02
Sealed Softgen and destination env names. Preview keys stay out of the client bundle.
Step 03
Old account, new signup, edge roles, attachments, SEO paths.
Step 04
Compare outcomes and side effects (emails, webhooks). Freeze schema at switch time.
Step 05
Watch Softgen-era cohorts on the new origin. Time-box reversal.
Read next
These pages are already on the site. Use them to pressure-test the bet before a call.
Get off Softgen
Leave Softgen hosting if the job is to stop running there.
Softgen to production
Own the process if you are not ready to leave Softgen yet.
Production-ready checklist
Moves, backups, and the ship list in checklist form.
Book a discovery call
Thirty minutes with a senior teammate. Honest next steps.
Verified on Clutch · 29 reviews
“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.”
Harris Edelmam
CEO · Ombligo, Inc.
Read on Clutch“Their project management was top-notch.”
Greg Moreno Earle
Technology Executive · Driven Brands Inc.
Read on Clutch“Their eye for clean, modern design combined with technical excellence was very impressive.”
Robert Valentino
Founder · Lean Coach
Read on Clutch“We appreciated Codecross's practiced approach to development.”
Brice Wiley
Marketing Director · Lex Mundi
Read on Clutch“On the development side, everything has gone quite smoothly and perfectly.”
Brandon Patterson
Co-Owner · Cap Tech Services, LLC.
Read on Clutch“They are very thorough in their approach to the project.”
Lukas Haynes
Member Board of Directors · Protect Our Winters Action Fund
Read on ClutchInternals
Stay inside the vibe-coding cluster, or open booking and the Austin money page.
Continue
Shared guides and the rest of the Softgen pages.
Continue
Move one part at a time if you are not switching this week.
Continue
When wrapping the Softgen app in place is still the honest job.
Continue
Bring what Softgen still holds. We will say what is missing before you change your site address.
Continue
Studio page if you want a partner for the Softgen move.
Before you book
Prefer writing? Send project details and we reply within one business day.
Take the product Softgen helped you prove — exportable code, a list of what it needs to run, and how it starts. Leave junk: preview caches, chat clutter, throwaway demo seed. Save data (or how to reach it) on its own so nothing invents that shape later.
Write down what the preview host had ready for you. Lock that list for a new machine. Replace “it worked because Softgen already had it” with a real start note. The check should fail if the app only installs inside Softgen.
Copy secret names into a template. Make fresh values on the destination — never paste preview keys into owned code. Point at the new store, run imports on a clean machine, update Softgen-era return links before DNS, then rotate secrets after the switch.
A normal host is missing preview helpers. Start paths assume Softgen folders. Publish is gone. Passwords arrive empty. Sign-in and live links still expect Softgen names. Fix install, start, and secrets first. Green on the preview does not mean portable.
Bring your Softgen export list, how people sign in, and a few Softgen test accounts. We put your site address last — and we name the Softgen path you can roll back to.
Prefer writing? Send project details on the contact page.