Base44 · ZIP/eject-plus-normalization
A Base44 project is a prompt history, Vite/React UI, entity schemas, functions, connectors, Auth config, and Base44 built-in hosting glued to Publish App. Migration is pulling ZIP/GitHub export or running `base44 eject`, translating Base44 env into lockfile-based CI, exporting row data separately, and landing on a conventional host. You keep the product behavior; you stop needing Base44’s Publish GUI—and you plan for SDK/backend pieces that still expect Base44 after a naive export.
30 min · senior team · leave with a clear next step
Company-level evidence
Review methodologyCitation-ready answer
CodeCross LLC defines migrate-from-base44 as ZIP/GitHub or base44 eject extraction into standard CI. Operators pull the frontend and ejected backend resources, pin Node and lockfiles, remap secrets for a clean runner, move entity data via CSV, and prove install then build then start without an open Base44 editor. Done when the destination boots from that checkout alone—no Publish App, no Base44-hosted runtime, no Base44 panel for production.
Why a raw Base44 ZIP fails on a standard host
CI images lack runtime the hosted app hid. Auth and entities still call Base44 via app ID. Connectors are not in the ZIP as live credentials. Row data never left Base44.
Caches, secret-bearing config files, and prompt notes that never hit disk need an include-or-drop pass. The extract is source, lockfiles, entity schemas, and a written connector map.
Replace “available because Publish App” steps with install, Vite build to dist, and a host start. Fail the pipeline if Auth/entity calls you intended to replace still require Base44.
Export names into a template. Mint new values on the destination. Rotate old Base44 secret values after cutover.
Capture table CSV dumps separately. Reconnect or replace connectors by hand. Update Auth callbacks that still hardcode Base44 hostnames before DNS moves.
The extract sequence that actually boots
Product behavior stays. Publish App GUI and Base44 backend assumptions leave. The destination is a conventional start command.
01
Leave Base44 caches and secret-bearing config out. Capture table CSV dumps separately so CI does not invent entity rows.
02
Version files or the base image. Fail if the app only boots when Base44 servers answer Auth/entity calls you intended to replace.
03
Never commit Base44 .env. Dual-write or restore rows, then verify the destination database on a clean runner.
04
The destination boots from that checkout alone. Publish App is no longer required for production.
How to
ZIP/eject-plus-normalization. Success is install → test → build → start with no open Base44 editor and no Publish App for production.
Step 01
Take ZIP or GitHub source, lockfiles, entity schema files, function entrypoints via eject, Auth config maps, and a written map of connectors. Leave caches and secret-bearing config out. Capture table CSV dumps separately.
Step 02
List VITE_BASE44_* and server secrets Base44 assumed. Pin Node. Replace Publish-only steps with install, Vite build, and a host start or static publish.
Step 03
Export names into an env template. Never commit Base44 .env. Update Auth callbacks and CORS that still hardcode Base44 hostnames before DNS moves.
Step 04
Eject copies schemas, not live rows. Restore CSV into the destination database. Reconnect or replace connectors by hand.
Step 05
install → test → build → start with the Base44 editor closed. Rotate old Base44 secret values after cutover. Publish App is then optional.
Read next
These pages are already on the site. Use them to pressure-test the bet before a call.
CI/CD checklist
Owned pipeline the normalized Base44 extract is supposed to join.
Get off Base44
Runtime exit if the extract is really a host disconnect.
Auth and data checklist
Entity and session spine after you leave Base44 backends.
Proof dashboard
Named charts and methodology for the headline numbers.
Book a discovery call
Thirty minutes with a senior teammate. Honest next steps.
Internals
Stay inside the vibe-coding cluster, or open booking and the Austin money page.
Continue
Shared intents and the rest of the Base44 pack.
Continue
The owned-origin definition this extract executes.
Continue
If you still need prompt rhythm while CI stands up.
Continue
If paid traffic is the risk and extract can wait.
Continue
Bring the ZIP or eject and the entity/connector map.
Continue
Named charts and methodology behind the headline numbers.
Continue
Studio page if you want a partner normalizing a Base44 extract.
Before you book
Prefer writing? Send project details and we reply within one business day.
Take ZIP or GitHub source, lockfiles, entity schema files, function entrypoints (via eject), Auth config maps, and a written map of connectors. Leave Base44 caches, `.app.jsonc` secrets, and editor-only junk out of the remote. Capture table CSV dumps separately—eject copies schemas, not live rows. Prompt-history notes that never hit disk need an explicit “include or drop” pass.
List env vars Base44 assumed (`VITE_BASE44_*` and server secrets). Pin Node in the CI image. Replace “available because Publish App” steps with `npm ci` / `pnpm i`, build (often Vite → `dist`), and a host start or static publish. Fail the pipeline if the app only boots when Base44 servers answer Auth/entity calls you intended to replace.
Export secret names into an env template; mint new values on the destination; never commit Base44 `.env`. Restore entity data into the destination database; reconnect or replace connectors by hand. Update Auth callbacks and CORS that still hardcode Base44 hostnames before DNS moves. Rotate old Base44 secret values after cutover so leaked panel copies die.
CI images lack Base44-injected runtime the hosted app hid; Auth and entities still call Base44 via app ID/base URL; connectors are not in the ZIP as live credentials; row data never left Base44. Normalize install, replace Base44 backend dependencies you are exiting, and env first; then push. A green Base44 Publish App is not a portable, fully owned build.
Bring the ZIP or eject and the start command Base44 assumed. We will say whether this is a portable Vite tree — or an app that only runs while Base44 servers answer.
Prefer writing? Send project details on the contact page.
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 Clutch