--- title: "Database sync: Postgres, MySQL, Mongo, Oracle | Stacksync" description: "Connect operational databases to business applications with Stacksync. Verify keys, change detection, write permissions, schema changes, and recovery." canonical: https://www.stacksync.com/database last_modified: 2026-09-15 --- DATABASE # Connect your operational database to your business systems. > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Connect your application database to your CRM and ERP without maintaining custom sync scripts. Control field mapping and sync direction, and monitor record changes in Stacksync. [Book a demo](https://www.stacksync.com/book-a-demo) ## Explore database connectors Explore the data, setup, and integration workflows for each system. - [connector PostgreSQL](https://www.stacksync.com/connectors/postgresql) - [connector MySQL](https://www.stacksync.com/connectors/mysql) - [connector SQL Server](https://www.stacksync.com/connectors/sql-server) - [connector MongoDB](https://www.stacksync.com/connectors/mongodb) - [connector Oracle DB](https://www.stacksync.com/connectors/oracle-db) - [connector Amazon DynamoDB](https://www.stacksync.com/connectors/amazon-dynamodb) What do I need for database synchronization? Database synchronization moves selected records between a database and another system while preserving identity and permitted writes. Stacksync’s Postgres connector requires a generated single-column primary key and logical-replication permissions. Schema, table, or column renames require configuration updates. [Review the Postgres requirements.](https://docs.stacksync.com/two-way-sync/connectors/postgres) ## Database integration guides and resources Choose between a read model and an application write-back path. Compare capture methods, test return writes, and coordinate schema changes with the selected connector. - [deep dive How to Cut Salesforce AI Agent Costs Before MCP Metering Starts](https://www.stacksync.com/blog/reduce-salesforce-mcp-costs-ai-agents) - [deep dive The AI Agent Data Layer: Per-App MCP Servers vs a Synced Postgres Database](https://www.stacksync.com/blog/ai-agent-data-layer-mcp-vs-synced-database) - [deep dive Acumatica–Postgres Sync for Beverage Operations: Match Case and Pallet Records Across Warehouses](https://www.stacksync.com/blog/acumatica-postgres-sync-for-beverage-operations-match-case-and-pallet-records-across-warehouses) - [deep dive NetSuite–Postgres Sync for Food Brands: Reconcile Co-Packer Receipts and Finished-Goods Records](https://www.stacksync.com/blog/netsuite-postgres-sync-for-food-brands-reconcile-co-packer-receipts-and-finished-goods-records) FAQ ## Frequently asked questions ### What does database synchronization require? Select the tables and business fields, preserve record identity, and verify database permissions. A read-only model and an application using two-way sync have different write requirements. The selected database connector determines its key, change-detection, and schema restrictions. [Postgres connector requirements](https://docs.stacksync.com/two-way-sync/connectors/postgres) ### Does every database connector use log-based CDC? No. The Postgres connector uses logical replication, while the MySQL setup documents database triggers for change logging. The separate Postgres Heroku connector also uses triggers when replication rights are unavailable. Follow the guide for the exact connector and hosting environment. [MySQL change logging setup](https://docs.stacksync.com/two-way-sync/connectors/mysql) ### What primary keys does the Postgres connector require? Each selected table needs a single-column primary key with a database-generated default. Composite primary keys are unsupported. The connected role also needs the documented ownership and replication permissions; confirm the hosting-specific procedure before changing replication settings. [Postgres key and replication requirements](https://docs.stacksync.com/two-way-sync/connectors/postgres) ### Can database views participate in two-way sync? A database view cannot be a writable destination for two-way sync. View support also varies by connector. Use a supported table when both sides need to accept writes, and confirm the selected source object separately when it only supplies data. [Two-way sync and read-only objects](https://docs.stacksync.com/two-way-sync/features/two-way-sync) ### What happens when a Postgres table or column is renamed? Renaming a schema, table, or column requires updating the Stacksync configuration. Treat the rename as a coordinated schema change: inspect the affected mappings, follow the documented update procedure, and verify representative records before expanding the sync again. [Postgres schema restrictions](https://docs.stacksync.com/two-way-sync/connectors/postgres) GET STARTED ## Syncing data at scale across all industries. - POC from integration engineers - Two-way, real-time sync - Workflow automation - White-glove onboarding [Book a demo](https://www.stacksync.com/book-a-demo) FROM A CUSTOMER “We've been using Stacksync across 4 different projects and can't imagine working without it.” Alex Marinov VP Technology, Acertus Delivers Vehicle logistics powered by technology