MySQL workflows / Cupcake-DRCP for macOS
MySQL to PostgreSQL. Copy, stream, compare.
Move MySQL data into PostgreSQL from a native Mac workspace. Cupcake-DRCP supports snapshots, ongoing CDC, and comparison so you can build the target, follow source changes, and verify the result.
One initial copy. An ongoing data path.
A MySQL-to-Postgres workflow has three distinct jobs: populate the target, keep up with changes, and check that the mapped data agrees. A reporting database may need all three. A one-time copy may only need a snapshot and a follow-up comparison.
Cupcake keeps the source connection, target connection, table pairs, and column rules in a reusable plan. The current Mac connection picker includes MySQL 5.7 and 8.x and PostgreSQL 14–17. Test the exact engine versions and types in your plan before expanding its scope.
Review the MySQL-to-PostgreSQL mappings.
Moving between engines requires attention to values as well as column names. Use the table and column mapping editor to inspect keys, casts, and expressions. Review the target definitions instead of assuming MySQL DDL can be used unchanged in PostgreSQL.
| Data or definition | What to verify |
|---|---|
| Keys and generated IDs | Row identity, uniqueness, and the target’s behavior when new rows arrive. |
| Numbers and flags | Accepted ranges, decimal precision, and the intended meaning of boolean-like values. |
| Dates and times | Valid source values, precision, and the time-zone behavior expected by the application. |
| Text and JSON | Encoding, comparison behavior, and whether representative values reach the target as intended. |
These are review points, not a promise of automatic conversion for every type. Consult the PostgreSQL data type reference for the target’s definitions.
Build and verify the PostgreSQL target.
- Connect and map. Choose MySQL as the source and PostgreSQL as the target. Start with a representative set of tables.
- Run a snapshot. Review the target and replacement options, then copy the initial data and inspect the completed run.
- Compare through the plan. Check missing, extra, and changed rows. Resolve mapping or data issues before increasing the workload.
- Enable ongoing CDC. Confirm MySQL source readiness and the selected capture method, then monitor changes arriving at PostgreSQL.
Exercise inserts, updates, and your chosen delete policy against a test target. Include values near type limits and records used by your application’s important queries.
Keep the PostgreSQL copy under review.
Use scheduled comparisons to detect drift as the source changes. Inspect proposed repairs or export SQL for review before applying them. Copying table data does not by itself convert application queries, stored procedures, or every engine-specific object.
Manual snapshots and comparisons are included in the Mac trial. Ongoing CDC requires a paid license and an awake Mac with a logged-in session. See the MySQL CDC workflow for capture and operating requirements.