Base44 | Make it easy for beginners to move from Base44 -> Bolt.new -> oTTomator

Can anyone help to build this?
Awesome—use GitHub as the “bridge.” Here’s the clean path from Base44 → Bolt.new → post on oTTomator.

1) Export from Base44

  • In your Base44 project, download/export source (or open the project folder locally).

  • Ensure you have:

    • package.json with a valid "start" or "dev" script (Bolt prefers dev for Vite).

    • README.md, LICENSE, .env.example, and a /public folder if you have static assets.

Example package.json (Vite/React):

{
  "name": "ottomator-prototype",
  "private": true,
  "scripts": {
    "dev": "vite",
    "build": "vite build",
    "preview": "vite preview --host --port 5173"
  },
  "engines": { "node": ">=18" },
  "dependencies": {
    "react": "^18.3.1",
    "react-dom": "^18.3.1",
    "vite": "^5.4.0"
  }
}

Add a .env.example:

VITE_API_BASE_URL=

2) Push to GitHub

cd your-project
git init
git add .
git commit -m "Export from Base44"
gh repo create ottomator-prototype --public --source=. --push
# or create a repo in the browser and:
# git remote add origin https://github.com/<you>/ottomator-prototype.git
# git push -u origin main

3) Import into Bolt.new

  • In Bolt.new, Create → Import from GitHub.

  • Pick the repo you just pushed.

  • In Bolt:

    • Set Node ≥ 18 (Project Settings → Environment).

    • Add any Secrets (Project Settings → Secrets) to match .env.example.

    • If it’s Vite, use Run “dev”. If you need a custom port, set it in Bolt’s settings or in vite.config.ts (Bolt usually proxies fine).

4) Sanity checks in Bolt

  • App builds and the preview runs.

  • If you use API calls:

    • Use relative paths or VITE_API_BASE_URL from Secrets.
  • Commit any tweaks back to GitHub; Bolt will pick them up if connected.

5) Post on oTTomator (thinktank.ottomator.ai)

Open: https://thinktank.ottomator.ai/c/general/4/l/new (new topic in “General”).
Use this template (paste-ready):

Title: oTTomator Prototype – Base44 → Bolt.new (Open Demo + Repo)

Hey all! I built an oTTomator prototype in Base44 and ported it to Bolt.new.

🔗 Live Demo (Bolt): <YOUR_BOLT_PROJECT_URL>
📦 Repo (GitHub): https://github.com/<you>/ottomator-prototype
📝 Tech: Vite + React (Node 18), API via VITE_API_BASE_URL

What’s inside:
- Modular components (UI + services)
- .env.example for easy setup
- Build scripts: dev / build / preview
- Lightweight README for quick start

Setup locally:
```bash
git clone https://github.com/<you>/ottomator-prototype
cd ottomator-prototype
cp .env.example .env # fill values
npm i
npm run dev

Roadmap:

  • Auth & roles

  • n8n/Flowise integration hooks

  • API endpoints for tasks (“runs”, “workflows”)

Feedback welcome—especially on API shape & UI flows. Thanks!


# 6) Optional niceties
- **README.md** (short, helpful):
```md
# oTTomator Prototype

Live: <YOUR_BOLT_PROJECT_URL>  
Repo: https://github.com/<you>/ottomator-prototype

## Run
```bash
npm i
cp .env.example .env
npm run dev

Build

npm run build && npm run preview

Env

  • VITE_API_BASE_URL – backend base URL

- **Screenshots**: add 2–3 images in `/docs` and embed them in the forum post.
- **License**: MIT is fine unless you have constraints.

---

Goal: Make it easy for beginners to move from Base44 -> Bolt.new -> oTTomator.

1 Like

this post may be a few months old, but I think I could still help anyone facing this problem.

I built EscapeBase44 after facing this exact problem myself. what it does is to rebuild the entire Base44 app end-to-end as a “normal” codebase on Github (deployed through vercel & supabase) that you fully control (includes entire backend, runtime, db, users, auth, etc). you can then do whatever you want with it (like plug it into Bolt.new and then to oTTomator in this case).