How to audit your Bubble app before migrating
Before you move an app off Bubble, list everything it does: data types, privacy rules, workflows, scheduled jobs and plugins. The free, open-source no-code migration audit does this from Claude Code through Bubble's official MCP server, without reading records or changing the app, and writes a plain-language report and an app spec you can build from.
Why audit before you migrate
Moving an app off a no-code platform goes wrong in the same places every time: data rules nobody wrote down, workflows that run in the background, plugins that hide real logic, and permissions that only exist as privacy rules. A rebuild that misses one of these looks finished until a user sees someone else's records or a scheduled job quietly stops. An audit lists all of it first, so the rebuild plan, the quote and the test list come from the real app rather than from memory.
What the free audit reads
The no-code migration audit is a free, open-source plugin for Claude Code. It connects to your app through Bubble's official MCP server and reads the app's structure only:
- Data types and their fields.
- Option sets.
- Privacy rules, which become the permission model in code.
- Pages and reusable elements.
- Workflows, including backend and scheduled workflows.
- Plugins and the API calls it can see used in workflows.
It never reads your records, logs or metrics, and it never changes the app: the skill is limited to five read tools. It runs on your machine with your own login, so nothing is sent to Red Center Studio.
What you get
- audit.md: a plain-language report. What is in the app, a complexity score, who can do what, what maps cleanly to code, what needs care, and what does not move automatically.
- app-spec.json: the same structure in neutral terms, checked against a published JSON Schema, so any developer or tool can build from it.
The complexity score compares apps with each other. It is not an estimate of hours or price.
Run it in four steps
- Install Claude Code and connect Bubble's MCP server by following Bubble's own MCP guide. You need to own the app or be a collaborator on it.
- Add the plugin's marketplace:
/plugin marketplace add Red-Center-Studio/nocode-migration-audit - Install the plugin:
/plugin install nocode-migration-audit@nocode-migration-audit - Run the audit with your app's name from the editor address (
bubble.io/page?id=your-app-name):/nocode-migration-audit:audit your-app-name
The two files land in migration-audit/your-app-name/ in the folder you ran Claude Code from. For a second lock, the plugin's README lists permission rules that make Claude Code refuse any Bubble tool that writes to an app or reads records.
Read the report like a migration plan
- Privacy rules are the first thing to check. Each one becomes a permission check in code, and a missed rule is a data leak.
- Backend and scheduled workflows become background jobs. List each one with what triggers it.
- Plugins either have a direct code equivalent, need a small rewrite, or hide logic you must rebuild. The report says which.
- What does not move: data, passwords, API keys and visual design are listed separately for your app. Passwords cannot be exported, so users will need a reset or a magic-link sign-in after the move.
What the audit does not do
It does not move data, rebuild the app or price the work. It cannot open API Connector call definitions with read-only tools, so it lists the calls it sees and asks you to check the rest in the editor. It supports apps built on Bubble today; other platforms will be added one reader at a time.
From audit to rebuild
The report is yours to use with any developer. If you want the move done for you, a Project Blueprint turns the audit into a scoped plan, architecture and fixed quote, and website and app migrations covers the rebuild itself, with your app running as code in your own Cloudflare account.