Real Bucket & Scope Hierarchy
Couchbase has real buckets, scopes, and collections. NoSQLSync lists your actual buckets and collections (including non-default scopes) instead of a placeholder.
No guessworkSchema Discovery
Documents within a collection can carry different fields. NoSQLSync samples documents via N1QL to build a complete schema covering every observed field.
Union schemaType Coercion Engine
Couchbase JSON types map cleanly to SQL: string → TEXT, number → INTEGER/DOUBLE, boolean → BOOLEAN, array/object → JSONB.
Auto type mappingOffset-Paginated Bulk Load
Full-collection scans page through N1QL LIMIT/OFFSET, creating a primary index automatically if one doesn't already exist — the same 'ensure what's needed' approach used for SQL targets.
Auto-indexingOne-time Migration Only
Couchbase's native change protocol (DCP) isn't exposed by the official Node SDK at all — Couchbase's own docs point teams at a Kafka connector instead. Rather than build an unverified low-level DCP client, live sync isn't offered for this source yet.
Honest scope, no dual-writeThree steps to Supabase
Type mapping: Couchbase → Supabase
Supabase is PostgreSQL. Connect it as a PostgreSQL target using the connection string from your project's database settings — every PostgreSQL type mapping below applies unchanged.
Frequently asked questions
Not yet. Couchbase's native change protocol (DCP) isn't exposed by the official Node SDK — Couchbase's own documentation points teams at a Kafka connector for that instead. One-time (bulk) migration is fully supported; live sync isn't offered rather than shipped as something shakier.
Yes. NoSQLSync lists collections across every scope in the bucket, not just the default one.
No — NoSQLSync creates one (CREATE PRIMARY INDEX IF NOT EXISTS) if the collection doesn't already have one, the same way it creates tables on SQL targets that don't exist yet.
A typical 100 GB dataset migrates in under 2 hours with bulk mode. With CDC enabled, ongoing writes sync in real time. Total time depends on data volume and network throughput.
Yes. All data is encrypted in transit (TLS 1.3) and at rest (AES-256). Database credentials use short-lived tokens. Migration workers run in an isolated environment and never store data after the job completes.
Yes. NoSQLSync only reads from your source — it is never modified, and CDC keeps running until you stop it. If you hit a problem after cutover, point your application's connection string back at the source.
Ready to migrate to Supabase?
Connect your Couchbase and Supabase instances. No credit card required.