Four output formats
CSV, JSON Lines, JSON array and Parquet.
Sync MySQL to Google Cloud Storage with Polytomic and let the binary log decide what gets written. Turn on incremental files and every ETL run drops only the rows that actually changed, tombstones included, which is how most high volume MySQL change data leaves the database.
CSV, JSON Lines, JSON array and Parquet.
Incremental files carry deletions as tombstones.
One stable file, or a timestamped file every run.
Polytomic is bi-directional by default, so you can move data the other way just as easily.

Jonathan Krangel
VP Global Head of Revenue Operations
“Polytomic handles so many ETL and sync jobs at Cursor. They are a true partner to us.”
Follow these simple steps to connect MySQL with Google Cloud Storage in minutes
Connect MySQL
Connect Google Cloud Storage
Create sync
Enable sync
Connect MySQL to Polytomic with host, port, database, and credentials.
Connect Google Cloud Storage to Polytomic with a service account JSON key.
Sync data in either direction between MySQL and Google Cloud Storage. 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 MySQL and Google Cloud Storage.
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.