Prepare Your Bubble App for Migration

Postgres table and column names are generated automatically from your Bubble names — so the cleaner your Bubble names, the cleaner your Postgres schema will be.

Recommendation

Rename your Bubble tables and columns to be meaningful and SQL-friendly before running the migration. PlanB will normalise them automatically (see Name normalisation rules), but renaming in Bubble means cleaner Postgres names and easier future SQL.

Checklist

1. Remove emojis from table and column names

Bubble lets you put 🚀 💰 ⭐ in your names. Postgres can't store them as identifiers. PlanB converts them to descriptive words (🚀 → rocket) but the result is rarely what you want long-term.

2. Don't start table names with a digit

Postgres identifiers can't start with a digit. PlanB prepends an underscore (2024_orders → _2024_orders) but underscored names are awkward in SQL. Rename in Bubble first.

3. Fix duplicate names in Bubble

Bubble lets you have:

• Two tables with the same name.
• Two columns with the same name within one table.

Postgres does not. PlanB suffixes _2, _3 to the duplicates, but you should fix them in Bubble first.

4. Avoid diacritic characters

Characters like é, ñ, ü, å are converted to their ASCII equivalents during migration:

• café → cafe
• René → rene

It doesn't matter whether your Bubble Data API setting is field display or ID key names — both go through the same normalisation.

5. Avoid SQL reserved words

Postgres has reserved keywords like USER, SELECT, DELETE, TRUNCATE, ORDER. PlanB suffixes an underscore (user → user_) but a Bubble table named user means every SQL query against your Postgres database will need extra quoting.

See the full list of reserved words.

6. Avoid Bubble's special column names

Bubble has built-in column names that you should never use for your own custom columns:

• Unique id
• authentication (used internally on the User table)
• Modified Date
• Created Date

Next: connect Supabase

Once your names are clean, the next step is to connect your Supabase database.