What would be a better setup for migrating our copywriter app from Bubble to Webflow, considering our requirements for saving user-generated content and potential limitations with Airtable's number of records?
- Use Webflow solely for UI and static content while handling user-generated data with a scalable backend like Xano, Supabase, or Firebase.
- Integrate user auth and API-connected front-end tools (e.g., Wized) to read/write dynamic content, avoiding Airtable's limitations and Webflow CMS constraints.
Migrating from Bubble to Webflow requires thoughtful architecture, especially when saving user-generated content and avoiding Airtable’s record limits. Here's how to build a scalable and future-proof setup.
1. Understand Airtable Limits
- Airtable’s record limit is 50,000 records per base (free & paid plans), which can quickly become restrictive with user-generated content like post drafts, responses, and histories.
- Search and filtering capabilities are also limited at scale.
- Not ideal for dynamic write-heavy applications.
2. Choose a Scalable Backend
- For production-grade apps with frequent content creation/editing, choose a real database such as:
- Xano (no-code, scalable, API-first backend)
- Supabase (open-source Firebase alternative with SQL support)
- Firebase Firestore (for real-time syncing and structured data)
- These options support a much higher amount of content and have superior API capabilities than Airtable.
3. Use Webflow for Front-end Only
Webflow CMS is read-only via API, not suitable for user-generated content.
Use Webflow for:
Public UI
Landing pages
Static content
Style system and responsive layout
Pair with an API-connected front-end (via Wized, Outseta, Memberstack, or custom JS) to handle dynamic data.
4. Integrate User Authentication
- Choose an auth solution like:
- Wized (connects Webflow to Xano or Supabase with logins)
- Firebase Auth (if using Firestore)
- Outseta (if monetization + auth is needed)
- Connect authenticated flows to your backend so users can create/read/update their content securely.
5. Manage Front-End to API Sync
- Avoid trying to push user content into Webflow CMS—it’s not writable via user interaction.
- Use forms or JS code on Webflow pages (connected via Wized/Xano API) to:
- Save new content
- Fetch user-specific data
- Update/delete entries
6. Optional: Progressive Enhancement with Backend UI
- If needed, build an admin dashboard or copywriter panel using:
- Xano front-end modules
- Retool or Stacker (for internal tools)
- Custom web app with React (if you’re going dev-heavy)
Summary
To migrate from Bubble to Webflow, use Webflow for the UI and connect it to a scalable backend like Xano or Supabase instead of Airtable. Webflow CMS is not meant for user-submitted content, so handle dynamic data via API on the front-end using Wized or similar tools. This avoids Airtable limitations and sets your app up for scale.