Replit · Deployments, Secrets, and GitHub
A Replit App can publish a Deployment. That is the live copy people open. It can keep passwords in the Secrets tool, save rows in a Database, and store uploads in App Storage. GitHub can hold the files. This page is about moving those four piles so the published app does not need an open Repl.
30 min · senior team · leave with a clear next step
Client + owned app revenue
$1,696,729
Company-reported · Basis and limitationsPartner savings
$308,650
Company-reported · Basis and limitationsProjects shipped
110+
Company-reported · Basis and limitationsIn plain words
CodeCross LLC treats leaving Replit as four piles. GitHub gets the files — not Secret values, not Database rows. The Secrets tool encrypts keys as environment variables, names the app reads at start. Editor Secrets do not copy to a published app; add those in the Publishing pane. A published app gets its own production Database. App Storage holds uploads. Done means the app starts on a host you pay for and the Repl can stay closed.
What a Git pull skips
The Git tool can sync files both ways. Replit is clear that Secret values and Database data do not ride along.
Importing or syncing a repo brings files and common run settings. Existing Secret values stay in the pane.
Secrets you set while building do not automatically carry over. Add the same keys in the Publishing pane or the published URL will miss them.
The editor uses a development Database. Publishing creates a separate production Database. Copying practice rows into the live one is a choice you make on purpose.
App Storage is Replit’s file bucket for pictures and documents. Those objects do not appear in GitHub. Download them before you stop the Deployment.
The Replit order
Connect GitHub first so the tree is safe. Then write down Secret names. Then copy the Database and App Storage while the Repl still runs.
01
Link GitHub in connected services, then connect the repository. Turn on auto-sync if you want two-way updates. This step is files only.
02
Open the Secrets tool. Copy the names — not a screenshot of the values — into the destination. Make fresh values there.
03
Know which Database the published app uses. The production Database is the one visitors hit. Move that, not only the editor copy.
04
Use the App Storage tool to download files from each bucket. A bucket belongs to one project and does not follow the GitHub repo.
How to
GitHub for files. Fresh Secrets on the destination. Database and App Storage on their own. Success is a start that does not need the Repl.
Step 01
Use the Git tool. Open the repo on GitHub and check the latest files. Do not expect Secret values or rows to appear there.
Step 02
The lock icon stores encrypted values as environment variables. Copy the names. On the destination, create new values. Never commit the pane.
Step 03
Editor Secrets stay in the editor. The Publishing pane needs its own keys. Missing keys show up as failed login or a dead Database.
Step 04
The published app uses a production Database and a DATABASE_URL. That address is what the app uses to find the rows. Copy that store, not only the editor one.
Step 05
Save uploads from each bucket. Start the app on the destination with the new Secrets. If start still needs the workspace, you are not done.
Replit pass or fail
Each line is a check you can run. Pass means that pile lives off the Repl.
Pass: GitHub has the latest Repl files.
Fail: you expected Secret values or Database rows to arrive with the pull.
Pass: every Secret name has a fresh value on the destination.
Fail: the app still reads the Replit Secrets pane.
Pass: production Secrets are set if anything still publishes on Replit.
Fail: only the editor pane has keys and the public URL is broken.
Pass: the production Database is copied to a store you control.
Fail: only the editor Database was copied, and live rows were left behind.
Pass: App Storage objects are downloaded.
Fail: pictures and uploads still live only in the Replit bucket.
Pass: the app starts on the destination with the Repl closed.
Fail: start still means opening the workspace.
Technical review: , CodeCross engineering
Read next
Use these guides to check your requirements and prepare the questions you want to discuss.
Get off Replit
Stop paying for the Deployment after Secrets and the Database live elsewhere.
Replit to production
Stay on Replit if you only need a boot you can name, not a host change.
Production-ready checklist
Go or no-go after the workspace can stay shut.
Book a discovery call
Bring the Secrets name list and which Database the Deployment uses.
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 ClutchWork with our team
Stay with the vibe-coding guides, or open booking and the Austin pages.
Continue
Directory of Replit intents.
Continue
Keep the Repl for spikes while one pile — Secrets or rows — moves first.
Continue
Seal the pane and the Deployment when leaving is wrong.
Continue
Show us the Git tool and the Publishing pane. We name the four piles.
Continue
If you want help moving pane Secrets and the production Database.
Before you book
Prefer writing? Send project details and we reply within one business day.
No. GitHub gets repository files and common run settings. Secret values and Database data stay on Replit. You remake Secrets on the destination and copy the Database yourself.
Editor Secrets do not automatically carry over to a published app. Add the same keys in the Publishing pane. Missing production Secrets cause empty values, failed API calls, and login errors.
The editor uses a development Database. Publishing creates a separate production Database for visitors. Copy the production one if people already use the live app. Only copy development rows if that data is safe to show live.
App Storage is a private bucket for uploads. It is not in GitHub. Download the objects from the App Storage tool. A bucket cannot move to another project, so take a copy while the Repl is still up.
Bring the Repl, the Secrets name list, and which Database the published app uses. We will say what GitHub already missed.
Prefer writing? Send project details on the contact page.