Connection requirements
- A connection string (couchbase:// or couchbases://) and a username/password with read access to the bucket
- The bucket and collection to migrate — collections are listed across every scope, not just the default one
One-time migration only — no CDC
Couchbase's native change protocol (DCP) is not exposed by the official Node SDK at all — Couchbase's own documentation points teams at a Kafka connector for that instead, and there's no official low-level DCP client for Node to fall back to. Rather than build one unverified, this connector supports bulk (one-time) migration only, via N1QL with automatic primary-index creation.
Setup
1
Add the connection
Provide the connection string, username, and password under Connections → Add.
2
Pick a bucket and collection
NoSQLSync lists your real buckets and collections (as scope.collection, or bare name for the default scope).
3
Introspect and migrate
Documents are sampled via N1QL to build a schema. A primary index is created automatically if the collection doesn't already have one.
FAQ
Why no live sync (CDC)?
Couchbase's DCP protocol is what powers its own replication and Kafka connectors, but it isn't exposed by the official Node SDK, and there's no mature low-level DCP client for Node to build on instead. It's left out rather than shipped half-verified.
Does this work with non-default scopes?
Yes — collections across every scope in the bucket are listed, not just _default.