Real Schema, Not Sampling
A CQL table already has a defined, typed schema. NoSQLSync reads it directly from system_schema.columns instead of sampling rows — more accurate than schema inference on a document store.
Schema-based introspectionComposite Key Handling
Cassandra tables commonly use a partition key plus clustering columns. When a table has more than one key column, NoSQLSync combines them into a single composite key column rather than risking distinct rows colliding on upsert.
No silent data lossPaginated Bulk Load
Full-table scans page through Cassandra's native paging state, so tables of any size migrate without loading everything into memory at once.
Cursor-based pagingType Coercion Engine
CQL types map cleanly to SQL: text/uuid → VARCHAR, int/bigint → INTEGER/BIGINT, list/set/map → JSONB, timestamp → TIMESTAMPTZ.
Auto type mappingOne-time Migration Only
Cassandra's CDC writes raw commit-log segments an external system must parse — there's no documented driver API for it. Rather than fake a shakier alternative, live sync isn't offered for this source yet.
Honest scope, no dual-writeThree steps to Snowflake
Type mapping: Cassandra → Snowflake
Frequently asked questions
Not yet. Cassandra's CDC feature writes raw commit-log segments to disk that an external system has to parse — there's no documented driver API for consuming CDC events. One-time (bulk) migration is fully supported; live sync isn't offered rather than shipped as something shakier.
Very common in Cassandra data modeling. NoSQLSync combines the partition key and clustering columns into a single composite key column for the SQL primary key, keeping every original column intact alongside it — this avoids distinct rows silently colliding during migration.
Yes. Choose which keyspace and table to migrate — NoSQLSync lists your real keyspaces and tables. Each table becomes a separate SQL table.
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 Snowflake?
Connect your Cassandra and Snowflake instances. No credit card required.