Binary log change capture
After the first load only committed changes move, read from the binary log rather than rescanning tables on every run.
Replicate MySQL into MotherDuck with Polytomic using binary log change capture, so an application database can be analyzed in DuckDB without running reporting queries against the server your product depends on. Both directions are supported and run on a schedule.
After the first load only committed changes move, read from the binary log rather than rescanning tables on every run.
GTIDs make picking up exactly where a sync stopped reliable, provided your binary log retention outlasts any outage you want to survive.
Analytical queries run in MotherDuck instead of competing with the transactional workload MySQL is actually there to serve.

Bec Hu
Head of Sales Ops, Chowbus
“The support is among the best I have ever encountered.”
Follow these simple steps to connect MotherDuck with MySQL in minutes
Connect MotherDuck
Connect MySQL
Create sync
Enable sync
Connect MotherDuck to Polytomic with an access token and your database name.
Connect MySQL to Polytomic with host, port, database, and credentials.
Sync data in either direction between MotherDuck and MySQL. Choose the source data and destination objects for the direction you need.
Map the fields, choose the sync schedule and behavior, then save and enable the sync.
Get answers to common questions about the integration process
Sync data in either direction between MotherDuck and MySQL.
Use both integrations' source and destination capabilities in one managed sync workflow.
Enterprise encryption and security protocols ensure your data remains protected.
Get up and running in minutes with our step-by-step integration guide.