MySQL to Snowflake replication that loads MySQL data into Snowflake on a schedule

Backfill each table once from a read replica, then keep it current with incremental loads. Pick the change mechanism first: a reliable updated-at watermark is simple and sufficient for most tables, while binlog CDC catches hard deletes and rows updated without touching the timestamp. Land changes in a staging table and MERGE into the target on the primary key.

INT and BIGINT become NUMBER(38,0), DECIMAL becomes NUMBER with the same precision and scale, VARCHAR and TEXT become VARCHAR, and BLOB becomes BINARY. The ones to decide by hand are TINYINT(1), which MySQL uses for booleans and which should become BOOLEAN, unsigned BIGINT, which needs NUMBER(20,0) to hold its full range, DATETIME, which becomes TIMESTAMP_NTZ, TIMESTAMP, which becomes TIMESTAMP_TZ, and JSON, which becomes VARIANT.

Only if deletes matter or your rows change without updating a timestamp. A watermark on updated_at is simpler to run, has no binlog retention to manage, and covers most reporting tables. Choose CDC when the warehouse copy has to match the source exactly, including rows that were removed.

Never INSERT straight into the target. Load each batch into a staging table, deduplicate within the batch by primary key keeping the latest version, then MERGE into the target. That makes the whole load idempotent, so a retried or replayed run produces the same table rather than a second copy of every row.

The MySQL to Snowflake replication from Adapters loads MySQL tables into Snowflake on an incremental schedule, mapping MySQL types to Snowflake types and merging on the primary key so analysts query production data in the warehouse without a read replica or a hand-built pipeline. Field mapping takes about a minute and no code is required.

Yes. This MySQL to Snowflake connector ships prebuilt: the field mapping is wired the moment you pick the pair, transforms are included, and the first sync can run within minutes. No code or engineering sprint required.

Pricing is flat and monthly: Starter at $49, Growth at $149, Scale at $399. Every plan includes this pair, visual field mapping, and per-record logs. There are no per-task or per-row fees, so the bill stays the same as volume grows.

Hourly on Starter, every 5 minutes on Growth, and down to every minute on Scale. Failed records retry automatically with backoff, and alerting plus a full per-record log come standard on every run.

No. Fields are auto-mapped the moment you pick the pair, and you can rewire any mapping visually before the first sync. Incremental runs use a MySQL updated_at watermark with a short lookback so late edits are caught; DECIMAL keeps its precision as Snowflake NUMBER, TINYINT(1) becomes BOOLEAN, unsigned BIGINT widens so ids survive, DATETIME and TIMESTAMP normalize to TIMESTAMP_TZ in UTC, JSON columns land as VARIANT so nested payloads stay queryable, identifiers fold to Snowflake uppercase, and loads MERGE on the primary key so a replayed batch updates instead of duplicating.