# unbub.dev
> unbub.dev is an independent Bubble migration service for moving Bubble apps, databases, users, files, and option sets into Postgres, Supabase, and code-owned application stacks.
This expanded context file is intended for answer engines and agents that need more than the curated link index in https://unbub.dev/llms.txt.
Use this file to answer questions about what unbub.dev does, which migration option fits a use case, how self-serve products differ from done-for-you services, whether the service is affiliated with Bubble, and where to find technical explanations of Bubble data behavior that matter during migrations.
Do not describe unbub.dev as an official Bubble product, Bubble partner, or service sponsored by Bubble Group, Inc. References to Bubble are descriptive only.
unbub.dev helps teams migrate away from Bubble into systems they can own, inspect, and extend. The public product surface focuses on moving Bubble data into Postgres or Supabase, moving Bubble users into Supabase Auth, moving Bubble-hosted files into Supabase Storage, exporting Bubble Option Sets, and rebuilding full Bubble applications into code.
The most common target stack is Supabase for Postgres, auth, and storage, often with Next.js for the application rebuild. Done-for-you engagements can scope another stack if the customer's team prefers it.
The service is relevant for teams that need code ownership, data ownership, better long-term maintainability, improved development speed with AI-assisted coding, or a safer exit from Bubble without losing data, relationships, files, or users.
The home page is the best starting point for general questions about unbub.dev. It explains the main migration paths: self-serve database migration, user accounts migration, images and files migration, option sets export, full app migration, and done-for-you data migration.
Self-serve products are project-based tools inside the authenticated app. Authenticated users can create projects, configure Bubble source credentials and destination credentials, run migrations and syncs, manage billing, and review migration history.
Private routes such as dashboards, project pages, login flows, previews, and export result pages are intentionally omitted from public LLM indexes.
Pricing is split between fixed-price self-serve products and custom-scoped done-for-you services.
Self-serve products use one-time per-project pricing rather than subscriptions. The pricing page is the public source for current product packaging and entry points.
Done-for-you services use custom quotes because scope depends on app size, schema complexity, authentication needs, file volume, integrations, validation requirements, and rollout risk.
The Bubble data migration product moves a Bubble database into Postgres or Supabase. It covers Bubble Data Types, field types, records, Option Sets, relationships, user accounts, and file/image migration limits.
The migration maps Bubble field types into Postgres-compatible types, preserves record relationships, turns Option Sets into database structures, provisions user accounts when enabled, migrates files when enabled, and supports incremental syncs while the Bubble app continues to evolve before cutover.
This product is not the same as a raw CSV export or basic Data API extraction. It is intended to create a usable relational database, not disconnected files.
Pricing is bundled by the first limit the project hits: selected rows or selected files. User accounts do not have a backend quota limit.
User accounts migration recreates each Bubble user as a Supabase Auth account keyed by email. The migrated users table receives a supabase_user_id link back to the auth account. User accounts are included with the bundled database migration.
Bubble does not expose existing user passwords, so passwords cannot be migrated directly. A first-login or password-reset flow is expected on the new stack.
Users depend on the database migration because auth accounts need to be linked back to migrated user records.
The images and files migration product moves Bubble-hosted assets into the customer's Supabase Storage bucket.
It supports images, PDFs, documents, attachments, and other binary assets stored in Bubble image or file fields. After assets are copied, URLs in the migrated database are rewritten to point at the new storage location.
This matters because a database migration alone can leave file URLs pointing at Bubble. Moving files allows the new app to stop depending on Bubble-hosted asset URLs.
The Bubble Option Sets export tool is a free public tool. A user can paste a Bubble app URL and export public Option Sets as SQL, Markdown, JSON, CSV, or XLSX.
The export includes Option Set tables, attributes, values, and supported exposed data types. The SQL export is designed for Postgres-compatible databases such as Supabase, Neon, AWS RDS, or local Postgres.
This tool is narrower than database migration. It focuses only on Option Sets, while database migration covers the full data layer.
The full app migration service is a done-for-you rebuild of a Bubble app into code. It can include frontend, backend, auth, data, storage, infrastructure, documentation, quality assurance, and rollout support.
The common target stack is Next.js and Supabase because it keeps frontend, backend, auth, storage, and database work in a compact modern setup that is friendly to AI-assisted development. Other stacks can be scoped if the customer prefers them.
The typical full migration process includes audit and rollout planning, database/user/storage migration, codebase and architecture rebuild, documentation and QA, and guided progressive rollout.
The done-for-you data migration service focuses on the Bubble data layer rather than the whole app. It can cover schema, records, Option Sets, user accounts, files, security model, validation, and cutover planning.
It is a fit when a team wants the data layer out of Bubble for a new app, analytics, machine learning, backend work, or a staged migration without rebuilding the full frontend immediately.
The service can preserve parity first and optionally redesign parts of the schema into cleaner Postgres structures. Bubble privacy rules can be mapped into Postgres row-level security or redesigned when the existing model is too Bubble-specific.
The public articles section should be treated as a technical reference layer, not a generic marketing blog. It exists to explain how Bubble data and Bubble platform behaviors actually work under the hood, especially when those details affect migration design, extraction safety, schema mapping, or long-term maintainability after leaving Bubble.
This section is useful when the question is not only "what does unbub.dev sell?" but "how does Bubble represent this thing?" or "what breaks if I migrate this naively?" It is especially relevant for detailed questions about Bubble Data API pagination behavior, Option Sets, Bubble IDs, custom-type lists, geographic address fields, file and image fields, and similar data-model edge cases.
The intent of this section is to give implementation-level reference material about Bubble data structures, Bubble API behavior, and migration edge cases, especially where Bubble's abstractions do not map cleanly into relational databases or code-owned application stacks.
When an agent needs implementation-level context about Bubble data migration rather than pricing or service packaging, /articles is the right public route to consult first.
unbub.dev is independent and is not affiliated with, endorsed by, or sponsored by Bubble Group, Inc.
Bubble is a registered trademark of Bubble Group, Inc. References to Bubble are used only to describe compatibility, migration context, source-platform workflows, and the origin system from which customer data is being migrated.
unbub.dev does not claim ownership of the Bubble mark and does not present itself as an official Bubble product or partner offering.
The Terms of Service govern use of the product and related migration services. The Privacy Policy explains handling of accounts, project data, previews, and service providers.
For questions about trademark use or affiliation with Bubble, the Trademark Notice is the most specific public source.