Skip to content
Database

MySQL and PostgreSQL integration — two-way sync

Keep supported MySQL and PostgreSQL records aligned with two-way data sync. Give each team access to current data while controlling which system can update each field.

  • Field mappings and sync direction under your control
  • Inspect and resolve record errors in one dashboard
Two-way sync for supported objects
stacksync.com
MySQL
PostgreSQL
Explore record coverage

Built for teams where self-serve, reliability and scale matter

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo

Example workflow

Plan table mappings between MySQL and PostgreSQL

Validate the selected objects and operations even where connector-level direction is documented.

Starting eventA selected source table needs an operational replica, a reporting projection, or a migration copy.

  1. Choose actual tables in MySQL and PostgreSQL and compare their schemas and record types.

  2. Specify the primary/business key, type conversions, filter boundaries, relationship dependencies, and the source of each writable field.

  3. Choose a one-way copy or two-way sync according to connector support and your update rules. Keep source views, aggregate outputs, and writable base tables distinct.

What to verifyCounts reconcile within identical filters; updates preserve keys; precision, nulls, deletes, and schema changes follow the agreed mapping rules.

Review records and field ownership

Mapping essentials

Records and field ownership

Match records by stable IDs and assign an owner for each field. The record notes identify the coverage to check.

Download the mapping worksheet

CSV · No email required

Choose the tables you need in MySQL and PostgreSQL, then map their keys, field types, and filters. Your schemas determine how records relate and which system should own each field. Use the worksheet to document those choices before testing the first load.

Why teams connect MySQL and PostgreSQL

Put your MySQL and PostgreSQL data to work

Start with the work your team needs to complete: keep records up to date, make operational data available for reporting, or move data to a new system. Choose one MySQL and PostgreSQL workflow to test, define what success looks like, and decide who handles failed updates.

  • Two-way sync between a MySQL application database and a CRM so operational records and sales records stay identical

  • Expose SaaS objects as MySQL tables so legacy internal tools built on MySQL can read live business data

  • Expose SaaS objects (CRM contacts, ERP invoices, support tickets) as Postgres tables that internal tools can query and join

  • Let an application write to its own database and have those rows appear as records in business systems in near real time

What records can you sync?

Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.

MySQL

Read and write support varies by record

Record types covered in the setup guide

Record typesCoverage and requirements
  • Tables
See connector requirements. Confirm field permissions and sync direction.

Read the MySQL connector guide

PostgreSQL

Read and write support varies by record

Record types covered in the setup guide

Record typesCoverage and requirements
  • Tables
See connector requirements. Confirm field permissions and sync direction.

Read the PostgreSQL connector guide

Connection essentials

Review how each system connects, detects changes, and permits access to your records.

View setup requirements and limits
Connection requirementMySQLPostgreSQL
Integration interfaceSQL wire protocol (MySQL client/server protocol)SQL wire protocol (PostgreSQL frontend/backend protocol)
AuthenticationDatabase credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnelDatabase credentials
Change detectionStacksync creates database triggers for change logging.The Postgres connector uses logical replication.
Read accessAvailable for supported recordsAvailable for supported records
Write accessAvailable for supported recordsAvailable for supported records

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

  • SOC 2 Type II
  • ISO 27001
  • HIPAA BAA
  • GDPR
  • CCPA
  • DPF US-EU-UK-CH

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

MySQL
Integration interface
SQL wire protocol (MySQL client/server protocol)
Authentication
Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host)
Change detection
Stacksync creates database triggers for change logging. Trigger permissions and binary-log settings must allow their creation.
Read access
Available for supported records
Write access
Available for supported records
Setup requirements
  • Use one auto-generated primary key per selected table and grant the connected user the required table permissions.
  • Verify that Stacksync can create triggers. When binary logging is enabled, an administrator may need to enable log_bin_trust_function_creators.
Limitations to check
  • Composite keys are unsupported and schema/table/column renames require a sync configuration update.
Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

MySQL setup guide
PostgreSQL
Integration interface
SQL wire protocol (PostgreSQL frontend/backend protocol)
Authentication
Database credentials (connection string or parameters), with optional SSL root certificate upload and optional SSH tunnel (SSH user + host); a least-privilege DB user
Change detection
The Postgres connector uses logical replication. The separate Postgres Heroku connector uses database triggers when replication rights are unavailable.
Read access
Available for supported records
Write access
Available for supported records
Setup requirements
  • Use a single-column primary key with a database-generated default for every selected table; composite primary keys are not supported.
  • Give the connected database role the required ownership and replication rights. Logical replication requires wal_level=logical; check the hosted database procedure before changing it.
  • For PostgreSQL 12 and earlier, have the database administrator install the pgcrypto extension before starting the sync so tracking tables can use gen_random_uuid(). PostgreSQL 13 and later provide this function without the extension.
Limitations to check
  • Renaming a schema, table, or column requires updating the sync configuration.
  • Database views cannot be used as writable destinations in two-way sync; validate the selected connector and view support separately.
Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

PostgreSQL setup guide

Prepare MySQL and PostgreSQL access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

MySQL setup checklist
  • Use one auto-generated primary key per selected table and grant the connected user the required table permissions.
  • Verify that Stacksync can create triggers. When binary logging is enabled, an administrator may need to enable log_bin_trust_function_creators.

Setup guides: Authorize MySQL

PostgreSQL setup checklist
  • Use a single-column primary key with a database-generated default for every selected table; composite primary keys are not supported.
  • Give the connected database role the required ownership and replication rights. Logical replication requires wal_level=logical; check the hosted database procedure before changing it.
  • For PostgreSQL 12 and earlier, have the database administrator install the pgcrypto extension before starting the sync so tracking tables can use gen_random_uuid(). PostgreSQL 13 and later provide this function without the extension.

Setup guides: Authorize PostgresEnsuring Secure Cloud SQL Connections with SSL CertificateEnsuring Secure RDS Connections with SSL Certificate

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the MySQL and PostgreSQL planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

See Stacksync in action · Review current pricing

Record identity and field ownership

Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.

Download the mapping worksheet · CSV, no email required

Choose the tables you need in MySQL and PostgreSQL, then map their keys, field types, and filters. Your schemas determine how records relate and which system should own each field. Use the worksheet to document those choices before testing the first load.

Compare integration approaches

Choose your tables and update rules before the integration method. A live application copy, a reporting table, and a one-time migration need different handling for updates, history, deletes, and reconciliation.

Stacksync managed sync

Best fit
Two-way sync for supported objects. Choose the records, writable fields, and permissions for your workflow.
Operating responsibility
Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose
Provide your table or object schemas and one example update; confirm the supported keys, fields, and direction.

Native vendor integration

Best fit
A vendor-built integration may fit if it supports your MySQL and PostgreSQL record types.
Operating responsibility
Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose
First check whether either vendor offers this integration. If available, verify your record types, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit
Consider when MySQL and PostgreSQL need a transformation, approval, or action outside a direct record sync.
Operating responsibility
Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose
Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery.

File or scheduled snapshot

Best fit
Consider for a one-time MySQL / PostgreSQL migration or a reporting need with an explicit freshness window.
Operating responsibility
Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose
Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Plan table mappings between MySQL and PostgreSQL

Validate the selected objects and operations even where connector-level direction is documented.

Starting event: A selected source table needs an operational replica, a reporting projection, or a migration copy.

  1. Choose actual tables in MySQL and PostgreSQL and compare their schemas and record types.
  2. Specify the primary/business key, type conversions, filter boundaries, relationship dependencies, and the source of each writable field.
  3. Choose a one-way copy or two-way sync according to connector support and your update rules. Keep source views, aggregate outputs, and writable base tables distinct.

Expected result: Counts reconcile within identical filters; updates preserve keys; precision, nulls, deletes, and schema changes follow the agreed mapping rules.

If it fails: Compare current source state, key mapping, and destination constraints before retrying. Reconcile the backlog after any schema or permission change.

Initial load and acceptance testing

Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.

Direction and permissions

Test case

Check that each connected account can read and write the chosen objects. Exercise both directions with a test record before enabling production changes.

Expected result

Only an approved, supported direction and permitted fields are written.

Schema, keys, and reconciliation

Test case

Use an actual MySQL and PostgreSQL table. Compare key uniqueness, nulls, decimal precision, timezone conversions, and counts within identical filters.

Expected result

The process meets its agreed freshness target and reconciliation has no unexplained differences.

Failed updates, retries and recovery

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

A record type or update is unavailable

Investigate

Check the MySQL and PostgreSQL connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between MySQL and PostgreSQL

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

MySQL PostgreSQL Timing depends on the connected systems

Detect changesStacksync creates database triggers for change logging. Trigger permissions and binary-log settings must allow their creation.

Apply updatesSelected writable fields update in PostgreSQL. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.

PostgreSQL MySQL Timing depends on the connected systems

Detect changesThe Postgres connector uses logical replication. The separate Postgres Heroku connector uses database triggers when replication rights are unavailable.

Apply updatesSelected writable fields update in MySQL. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.

Update timing and record limits
  • Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
FAQ

MySQL and PostgreSQL integration FAQ

Further reading

Guides and resources

Next step

See your workflow in Stacksync

Walk through your MySQL and PostgreSQL records, field mappings, and requirements with an integration engineer.

See Stacksync in action Explore plans and pricing