Salesforce 
HubSpot 
NetSuite 
Zendesk 
Microsoft Dynamics 365 Sales 
Dynamics 365 F&O 
Attio 
Pipedrive 
Zoho CRM 
Campfire 
Rillet 
Front 
Shopify 
Amazon Seller Central 
SendGrid Keep supported MariaDB and MySQL records aligned with two-way data sync. Give each team access to current data while controlling which system can update each field.
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 MariaDB and MySQL workflow to test, define what success looks like, and decide who handles failed updates.
Explore the record types and read/write requirements for each system.
Record types covered in the setup guide
| Record type | Coverage and requirements |
|---|---|
| Tables | See connector requirements. Confirm field permissions and sync direction. |
Record types covered in the setup guide
| Record type | Coverage and requirements |
|---|---|
| Tables | See connector requirements. Confirm field permissions and sync direction. |
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Use the worksheets and reference checks to capture record identity, ownership, and the result your business expects.
Implementation reference
Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.
Download the mapping worksheetCSV · No email required · Record matching, ownership, and test cases
Choose the tables you need in MariaDB and MySQL, 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.
Architecture decision
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.
Workflow reference
Open a workflow to see its trigger, record relationships, and expected result.
Starting event: A selected source table needs an operational replica, a reporting projection, or a migration copy.
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.
Production readiness
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Check that each connected account can read and write the chosen objects. Exercise both directions with a test record before enabling production changes.
Only an approved, supported direction and permitted fields are written.
Use an actual MariaDB and MySQL table. Compare key uniqueness, nulls, decimal precision, timezone conversions, and counts within identical filters.
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Failure recovery
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Check the MariaDB and MySQL connector guides, account permissions, and any operations marked On Request.
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Compare current source values, destination validation, identity mappings, and any side effects already completed.
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.
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Detect changesStacksync creates database triggers for change logging. Trigger permissions and binary-log settings must allow their creation.
Apply updatesSelected writable fields update in MySQL. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Detect changesStacksync creates database triggers for change logging. Trigger permissions and binary-log settings must allow their creation.
Apply updatesSelected writable fields update in MariaDB. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
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.
Setup guides: Authorize MariaDB
Setup guides: Authorize MySQL
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 MariaDB and MySQL planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Use SSO and SCIM to manage access, secure connection options to reach your systems, and record-level retry and revert controls to resolve sync errors.
Stacksync connects MariaDB and MySQL with two-way sync for supported records. Authorize the accounts, select the record types, and map compatible fields. Both connectors support reading and writing; object permissions determine the available fields. Use the Issues dashboard to inspect and resolve rejected updates.
Both connectors support reading and writing data, but the chosen objects and fields must also permit both directions. Read-only fields remain one-way. Stacksync database-view sync is one-way; it does not write back to the view.
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Use one auto-generated primary key per selected table and grant the connected user the required table permissions. Use one auto-generated primary key per selected table and grant the connected user the required table permissions. Use the pair worksheet to record ownership and acceptance criteria.
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
Choose the tables you need in MariaDB and MySQL, 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.
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.
Walk through your MariaDB and MySQL records, field mappings, and requirements with an integration engineer.
Review documented support, sync direction, and setup requirements on each pair page. Search all 483 integrations listed for MariaDB and MySQL.
