Skip to main content
This guide walks you through migrating a Base44 app to a production AWS deployment with your own domain, database, and Git history.

What gets migrated

  • Full React + Vite source code
  • Supabase database schema (tables, indexes, RLS policies)
  • All detected environment variables
  • Static assets and public files

Prerequisites

  • An Nometria account
  • The Nometria Chrome Extension installed
  • Your Base44 project open in Chrome
  • A custom domain (optional — a free *.nometria.com URL is provided if not)
  • A Supabase account (free tier works)

Step 1 — Export from Base44

1

Open your Base44 project

Navigate to your Base44 project. Make sure you’re on the main editor view (not the settings or billing pages).
2

Click Export in the extension

Click the Nometria extension icon in your Chrome toolbar → Export to Nometria.The extension reads your project’s file tree. You’ll see a progress indicator as it packages the code.
3

Review the detected stack

A preview shows:
  • Framework: React + Vite
  • Database: Supabase (with your project ID)
  • File count and estimated size
Confirm and click Continue to Nometria.

Step 2 — Configure your deployment

You’ll land on the Nometria configuration screen with your Base44 project pre-loaded.
1

Set environment variables

Nometria pre-fills variables detected from your Base44 project. Review them and add any missing values:
VITE_SUPABASE_URL=https://xxxxxxxxxxxx.supabase.co
VITE_SUPABASE_ANON_KEY=eyJ...
Add any additional API keys your app uses (Stripe, OpenAI, Resend, etc.).
2

Configure your database

Choose one of:Option A — Migrate to your own Supabase project (recommended): Select Create new Supabase project. Nometria provisions a Supabase project and migrates your Base44 schema automatically.Option B — Keep using the Base44 Supabase project: Select Use existing Supabase project and paste your Base44 project URL and service role key.
If you choose Option B, your data still lives in Base44’s infrastructure. Option A gives you full ownership.
3

Set your domain

Enter your custom domain or leave blank to use the free *.nometria.com staging URL.
4

Choose your AWS region

Select the region closest to your users. us-east-1 is the default.

Step 3 — Deploy

Click Deploy. Deployment takes 5–10 minutes on first run. You can watch build logs stream in real time. When complete, your dashboard shows:
  • Live URL (your domain or *.nometria.com)
  • Git repository link
  • Deployment timestamp and commit SHA

Step 4 — Verify your app

Open your live URL and test:
  • App loads correctly
  • Authentication works (sign up / sign in)
  • Database reads and writes work
  • Any third-party integrations function (Stripe, email, etc.)

Step 5 — Enable two-way sync (optional)

To keep iterating in Base44 and have changes flow to production automatically: Settings → Sync → Enable Two-Way Sync From now on, every code change in Base44 is committed to builder/latest and can be reviewed and merged to production without re-running the export flow.

Two-way sync workflow

Learn how to build in Base44 while keeping production in sync.

Post-migration checklist

  • DNS is pointing to your Nometria deployment
  • SSL certificate is active (green padlock)
  • Supabase RLS policies are correct on the new project
  • Old Base44 project is archived or deleted
  • Environment variables are all set (no fallback to Base44 defaults)