--- title: "Sage X3 connector: setup and compatibility | Stacksync" description: "Sage X3 integration guide: plan Business Partners (Customers and Suppliers) and Bills of Material, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/sage-x3 last_modified: 2026-09-15 --- ERP · Two-way sync platform # Sage X3 integration. > 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 Sage X3 workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Business Partners (Customers and Suppliers), Bills of Material and GL Journals. Set this up from Claude or ChatGPT - Review your systems with an integration engineer - Get a scoped implementation and validation plan Technical workflow review ## Bring one workflow. Leave with a technical plan. An engineer will assess the required records, access method, and read/write operations before recommending an implementation. - **Business Partners (Customers and Suppliers)** - **Products** - **Sales Orders** **What to bring** Bring a sample record, the other system, and the change your team needs to automate. [Talk through your workflow](https://www.stacksync.com/book-a-demo?connector=sage-x3) ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Record types ## Sage X3 records to discuss. These Sage X3 record examples help scope a technical review. They are not a list of verified Stacksync operations. Business Partners (Customers and Suppliers) Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. Products Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys. Sales Orders Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices. ### See 3 more record examples Purchase Orders Retain purchase-order and line IDs together with the supplier and legal-entity context. Work Orders Identify this record type and the operation you need to review with Stacksync. Stock / Inventory by site Identify this record type and the operation you need to review with Stacksync. Connection setup ## Sage X3 connection requirements. Review Sage X3 access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion. ### Prepare access and scope for the engineering review - Identify the Sage X3 account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Sage X3, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Sage X3 integration. Choose whether the integration moves master data, reports transactions, or creates an approved financial document. Preserve entity, currency, accounting period, and header/line references. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Sage X3 **Source record ID** Keep the account and record type Record matching **Source ID ↔ destination ID** Link the same record across systems Selected destination **Destination record ID** Preserve its local key and rules *Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.* Match the same record in both systems Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. Load related records in the right order Resolve person or company type, legal entity, business role, and any billing account before transactions. ### Mapping checks by record type #### Business Partners (Customers and Suppliers) Confirm object support with Stacksync Identity Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. Fields to consider Source customer ID · Person/company classification · Legal entity or business unit · Destination identity reference Related records to resolve first Resolve person or company type, legal entity, business role, and any billing account before transactions. Test before going live Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact. #### Bills of Material Confirm object support with Stacksync Identity Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice. Fields to consider Source bill ID · Supplier reference · Entity · Line amounts and currency · Approval/posting state Related records to resolve first Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines. Test before going live Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period. #### GL Journals Confirm object support with Stacksync Identity Retain journal ID and line IDs within the legal entity and accounting period. Fields to consider Source journal ID · Account references · Debit/credit amounts · Entity · Accounting period Related records to resolve first Resolve chart-of-account, currency, entity, and dimension references before lines. Test before going live Verify balanced debits and credits, dimension requirements, and rejection for a closed period. #### Products Confirm object support with Stacksync Identity Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys. Fields to consider Source product ID · SKU or variant reference · Description · Unit of measure · Price-list reference Related records to resolve first Resolve units, variants, categories, and applicable price lists before order lines. Test before going live Test two variants of one product, a changed SKU, and a price that applies to only one market or currency. #### Sales Orders Confirm object support with Stacksync Identity Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices. Fields to consider Source order ID · Customer reference · Line references and quantities · Order status · Currency Related records to resolve first Create or locate the customer and products first; resolve taxes, currency, and fulfillment references. Test before going live Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header. #### Purchase Orders Confirm object support with Stacksync Identity Retain purchase-order and line IDs together with the supplier and legal-entity context. Fields to consider Source purchase-order ID · Supplier reference · Line references · Quantity · Approval status Related records to resolve first Resolve supplier, product, business unit, and delivery-location references before lines. Test before going live Test a partially received purchase order and an amendment after approval. [Download the field-mapping workbook (CSV)](https://www.stacksync.com/downloads/sync-planning/field-mapping-workbook.csv) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer. Setup and validation ## Validate the Sage X3 integration in four steps. Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice. ### View the four setup tests and expected results 1. ### Verify Sage X3 credentials and resource scope After confirming an implementation path, validate the selected access method with the intended account, region or workspace, and resource scope. Record the credential owner and renewal procedure, then demonstrate access to one selected object. **Expected result:** The selected resource is accessible through the approved credential, with the renewal and revocation procedure assigned to an owner. 2. ### Test record matching for Business Partners (Customers and Suppliers) Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact. **Expected result:** Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice. 3. ### Test the operation your workflow needs Review one Sage X3 record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration. **Expected result:** The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair. 4. ### Test recovery and name the support owner For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity. **Expected result:** The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors. [Use the production-readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) to record test results, assign support owners, and agree on when to go live. Troubleshooting ## Troubleshoot your Sage X3 integration. ### Diagnose record matching, delayed changes, and rejected operations A Sage X3 record appears under the wrong destination record Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. Resolve person or company type, legal entity, business role, and any billing account before transactions. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Sage X3 implementation’s change-detection method for Business Partners (Customers and Suppliers), Bills of Material and GL Journals. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture. One operation succeeds while another is rejected Check the specific Sage X3 object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available. [Review retry, replay, and recovery behavior](https://www.stacksync.com/blog/two-way-sync-error-handling-retries-replay) before repeating an operation that may already have succeeded. [Review your Sage X3 workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=sage-x3) ## Sage X3 integration guides - [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [guide How Digital Innovation Is Reshaping Modern Business Operations](https://www.stacksync.com/blog/how-digital-innovation-is-reshaping-modern-business-operations) FAQ ## Sage X3 connector FAQ ### How should I plan an integration with Sage X3? Choose whether the integration moves master data, reports transactions, or creates an approved financial document. Preserve entity, currency, accounting period, and header/line references. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding. ### Can the Sage X3 connector write changes back? Write-back support is not established for this connection. Review the Sage X3 records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Sage X3 data? Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. ### Which related records should I load first for Sage X3? Resolve person or company type, legal entity, business role, and any billing account before transactions. ### How do I validate Sage X3 changes after the initial load? Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact. Reconcile totals within the same entity and currency. A repeated delivery does not post the same financial transaction twice. ### What will we cover in a Sage X3 integration demo? Start with one workflow and a sample record from Business Partners (Customers and Suppliers), Bills of Material and GL Journals. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document. AI assistant ## Set up Sage X3 from Claude or ChatGPT Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste. ### 1. Add the Stacksync MCP server Server URL `https://mcp.stacksync.com/mcp` #### In Claude 1. Open Customize → Connectors, select + Add, then Add custom connector. 2. Name it Stacksync and enter https://mcp.stacksync.com/mcp. 3. Select Connect, sign in to Stacksync and choose your workspace. #### In ChatGPT 1. Open Settings → Apps → Advanced settings and turn on Developer mode. 2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth. 3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat. ##### Set up Codex or Claude Code #### Codex ``` codex mcp add stacksync --url https://mcp.stacksync.com/mcp codex mcp login stacksync ``` Complete the browser sign-in with your Stacksync account, then start a new Codex session. #### 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. Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet. Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: [setup steps in the docs](https://docs.stacksync.com/mcp). ### 2. Ask your assistant > Create a sync between my Sage X3 and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Sage X3. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Sage X3 record changes.” - “Create a Genie that answers questions about our Sage X3 data in Slack.” #### What happens next - Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat. - Gives you a secure sign-in link for each app it connects; you open it and sign in to that app. - Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first. New to Stacksync? [Create an account](https://app.stacksync.com/signup) first, then sign in from your assistant. ## Explore Sage X3 connections Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair. ### Start with these integration guides - [Sage X3 and Salesforce](https://www.stacksync.com/integrations/sage-x3-and-salesforce) - [Pendo and Sage X3](https://www.stacksync.com/integrations/pendo-and-sage-x3) - [Magento and Sage X3](https://www.stacksync.com/integrations/magento-and-sage-x3) - [Sage X3 and Stripe](https://www.stacksync.com/integrations/sage-x3-and-stripe) - [Sage X3 and Shopify](https://www.stacksync.com/integrations/sage-x3-and-shopify) - [Docusign and Sage X3](https://www.stacksync.com/integrations/docusign-and-sage-x3) - [Creatio CRM and Sage X3](https://www.stacksync.com/integrations/creatio-crm-and-sage-x3) - [Sage X3 and ServiceNow](https://www.stacksync.com/integrations/sage-x3-and-servicenow) ### CRM · 42 - [Sage X3 and Affinity](https://www.stacksync.com/integrations/affinity-and-sage-x3) - [Sage X3 and Attio](https://www.stacksync.com/integrations/attio-and-sage-x3) - [Sage X3 and Chorusai](https://www.stacksync.com/integrations/chorusai-and-sage-x3) - [Sage X3 and Clari](https://www.stacksync.com/integrations/clari-and-sage-x3) - [Sage X3 and Close](https://www.stacksync.com/integrations/close-and-sage-x3) - [Sage X3 and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-sage-x3) - [Sage X3 and Creatio CRM](https://www.stacksync.com/integrations/creatio-crm-and-sage-x3) - [Sage X3 and DealCloud](https://www.stacksync.com/integrations/dealcloud-and-sage-x3) - [Sage X3 and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-sage-x3) - [Sage X3 and Folk CRM](https://www.stacksync.com/integrations/folk-crm-and-sage-x3) - [Sage X3 and Freshsales](https://www.stacksync.com/integrations/freshsales-and-sage-x3) - [Sage X3 and Freshworks CRM](https://www.stacksync.com/integrations/freshworks-crm-and-sage-x3) - [Sage X3 and Gladly](https://www.stacksync.com/integrations/gladly-and-sage-x3) - [Sage X3 and Gong](https://www.stacksync.com/integrations/gong-and-sage-x3) - [Sage X3 and Gorgias](https://www.stacksync.com/integrations/gorgias-and-sage-x3) - [Sage X3 and HubSpot](https://www.stacksync.com/integrations/hubspot-and-sage-x3) - [Sage X3 and Infor CRM](https://www.stacksync.com/integrations/infor-crm-and-sage-x3) - [Sage X3 and Insightly](https://www.stacksync.com/integrations/insightly-and-sage-x3) - [Sage X3 and Intercom](https://www.stacksync.com/integrations/intercom-and-sage-x3) - [Sage X3 and Kommo](https://www.stacksync.com/integrations/kommo-and-sage-x3) - [Sage X3 and Kustomer](https://www.stacksync.com/integrations/kustomer-and-sage-x3) - [Sage X3 and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/microsoft-dynamics-365-sales-and-sage-x3) - [Sage X3 and Nimble](https://www.stacksync.com/integrations/nimble-and-sage-x3) - [Sage X3 and Nutshell](https://www.stacksync.com/integrations/nutshell-and-sage-x3) - [Sage X3 and Oracle CX Sales](https://www.stacksync.com/integrations/oracle-cx-sales-and-sage-x3) - [Sage X3 and Outreach](https://www.stacksync.com/integrations/outreach-and-sage-x3) - [Sage X3 and Pipedrive](https://www.stacksync.com/integrations/pipedrive-and-sage-x3) - [Sage X3 and Salesforce](https://www.stacksync.com/integrations/sage-x3-and-salesforce) - [Sage X3 and Salesloft](https://www.stacksync.com/integrations/sage-x3-and-salesloft) - [Sage X3 and SAP Sales Cloud](https://www.stacksync.com/integrations/sage-x3-and-sap-sales-cloud) - [Sage X3 and Seismic](https://www.stacksync.com/integrations/sage-x3-and-seismic) - [Sage X3 and Shopify](https://www.stacksync.com/integrations/sage-x3-and-shopify) - [Sage X3 and Streak CRM](https://www.stacksync.com/integrations/sage-x3-and-streak-crm) - [Sage X3 and SugarCRM](https://www.stacksync.com/integrations/sage-x3-and-sugarcrm) - [Sage X3 and Twenty CRM](https://www.stacksync.com/integrations/sage-x3-and-twenty-crm) - [Sage X3 and Veeva CRM](https://www.stacksync.com/integrations/sage-x3-and-veeva-crm) - [Sage X3 and Vitally](https://www.stacksync.com/integrations/sage-x3-and-vitally) - [Sage X3 and Vtiger CRM](https://www.stacksync.com/integrations/sage-x3-and-vtiger-crm) - [Sage X3 and Xactly](https://www.stacksync.com/integrations/sage-x3-and-xactly) - [Sage X3 and Zoho CRM](https://www.stacksync.com/integrations/sage-x3-and-zoho-crm) - [Sage X3 and Zoho SalesIQ](https://www.stacksync.com/integrations/sage-x3-and-zoho-salesiq) - [Sage X3 and ZoomInfo](https://www.stacksync.com/integrations/sage-x3-and-zoominfo) ### ERP · 38 - [Sage X3 and Acumatica](https://www.stacksync.com/integrations/acumatica-and-sage-x3) - [Sage X3 and Blue Yonder WMS](https://www.stacksync.com/integrations/blue-yonder-wms-and-sage-x3) - [Sage X3 and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-sage-x3) - [Sage X3 and Cin7](https://www.stacksync.com/integrations/cin7-and-sage-x3) - [Sage X3 and DEAR Inventory](https://www.stacksync.com/integrations/dear-inventory-and-sage-x3) - [Sage X3 and Dynamics 365 Business Central](https://www.stacksync.com/integrations/microsoft-dynamics-365-business-central-and-sage-x3) - [Sage X3 and Dynamics 365 F&O](https://www.stacksync.com/integrations/dynamics-365-finance-operations-and-sage-x3) - [Sage X3 and Epicor ERP](https://www.stacksync.com/integrations/epicor-erp-and-sage-x3) - [Sage X3 and Extensiv (3PL Central)](https://www.stacksync.com/integrations/extensiv-3pl-central-and-sage-x3) - [Sage X3 and Fishbowl Manufacturing](https://www.stacksync.com/integrations/fishbowl-manufacturing-and-sage-x3) - [Sage X3 and Global Shop Solutions](https://www.stacksync.com/integrations/global-shop-solutions-and-sage-x3) - [Sage X3 and Infor CloudSuite](https://www.stacksync.com/integrations/infor-cloudsuite-and-sage-x3) - [Sage X3 and Infor LN](https://www.stacksync.com/integrations/infor-ln-and-sage-x3) - [Sage X3 and Infor M3](https://www.stacksync.com/integrations/infor-m3-and-sage-x3) - [Sage X3 and Infor WMS](https://www.stacksync.com/integrations/infor-wms-and-sage-x3) - [Sage X3 and Linnworks](https://www.stacksync.com/integrations/linnworks-and-sage-x3) - [Sage X3 and Logiwa WMS](https://www.stacksync.com/integrations/logiwa-wms-and-sage-x3) - [Sage X3 and Macola ERP](https://www.stacksync.com/integrations/macola-erp-and-sage-x3) - [Sage X3 and Manhattan Associates WMS](https://www.stacksync.com/integrations/manhattan-associates-wms-and-sage-x3) - [Sage X3 and Microsoft Dynamics GP](https://www.stacksync.com/integrations/microsoft-dynamics-gp-and-sage-x3) - [Sage X3 and Microsoft Dynamics NAV](https://www.stacksync.com/integrations/microsoft-dynamics-nav-and-sage-x3) - [Sage X3 and NetSuite](https://www.stacksync.com/integrations/netsuite-and-sage-x3) - [Sage X3 and Odoo](https://www.stacksync.com/integrations/odoo-and-sage-x3) - [Sage X3 and Oracle Fusion ERP](https://www.stacksync.com/integrations/oracle-fusion-erp-and-sage-x3) - [Sage X3 and Plex ERP](https://www.stacksync.com/integrations/plex-erp-and-sage-x3) - [Sage X3 and QAD ERP](https://www.stacksync.com/integrations/qad-erp-and-sage-x3) - [Sage X3 and Rootstock ERP](https://www.stacksync.com/integrations/rootstock-erp-and-sage-x3) - [Sage X3 and Sage 100](https://www.stacksync.com/integrations/sage-100-and-sage-x3) - [Sage X3 and Sage 300](https://www.stacksync.com/integrations/sage-300-and-sage-x3) - [Sage X3 and Sage Intacct](https://www.stacksync.com/integrations/sage-intacct-and-sage-x3) - [Sage X3 and SAP](https://www.stacksync.com/integrations/sage-x3-and-sap) - [Sage X3 and SAP Business ByDesign](https://www.stacksync.com/integrations/sage-x3-and-sap-business-bydesign) - [Sage X3 and SAP Business One](https://www.stacksync.com/integrations/sage-x3-and-sap-business-one) - [Sage X3 and SAP S/4HANA](https://www.stacksync.com/integrations/sage-x3-and-sap-s4hana) - [Sage X3 and SuiteAnalytics](https://www.stacksync.com/integrations/sage-x3-and-suite-analytics) - [Sage X3 and Syspro](https://www.stacksync.com/integrations/sage-x3-and-syspro) - [Sage X3 and TikTok Shop](https://www.stacksync.com/integrations/sage-x3-and-tiktok) - [Sage X3 and Unleashed Software](https://www.stacksync.com/integrations/sage-x3-and-unleashed-software) ### Database · 49 - [Sage X3 and Airtable](https://www.stacksync.com/integrations/airtable-and-sage-x3) - [Sage X3 and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-sage-x3) - [Sage X3 and Amazon DynamoDB](https://www.stacksync.com/integrations/dynamo-db-and-sage-x3) - [Sage X3 and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-sage-x3) - [Sage X3 and Amazon Lightsail](https://www.stacksync.com/integrations/amazon-lightsail-and-sage-x3) - [Sage X3 and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-sage-x3) - [Sage X3 and Apache Cassandra](https://www.stacksync.com/integrations/apache-cassandra-and-sage-x3) - [Sage X3 and AWS Aurora MySQL](https://www.stacksync.com/integrations/aws-aurora-mysql-and-sage-x3) - [Sage X3 and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-sage-x3) - [Sage X3 and Azure Cosmos DB](https://www.stacksync.com/integrations/azure-cosmos-db-and-sage-x3) - [Sage X3 and Azure SQL Database](https://www.stacksync.com/integrations/azure-sql-database-and-sage-x3) - [Sage X3 and Citus](https://www.stacksync.com/integrations/citus-and-sage-x3) - [Sage X3 and CockroachDB](https://www.stacksync.com/integrations/cockroachdb-and-sage-x3) - [Sage X3 and Couchbase](https://www.stacksync.com/integrations/couchbase-and-sage-x3) - [Sage X3 and DuckDB](https://www.stacksync.com/integrations/duckdb-and-sage-x3) - [Sage X3 and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-sage-x3) - [Sage X3 and Firebase](https://www.stacksync.com/integrations/firebase-and-sage-x3) - [Sage X3 and Google AlloyDB](https://www.stacksync.com/integrations/google-alloydb-and-sage-x3) - [Sage X3 and Google Cloud Spanner](https://www.stacksync.com/integrations/google-cloud-spanner-and-sage-x3) - [Sage X3 and Google Cloud SQL](https://www.stacksync.com/integrations/google-cloud-sql-and-sage-x3) - [Sage X3 and IBM AS/400](https://www.stacksync.com/integrations/ibm-as400-and-sage-x3) - [Sage X3 and IBM Db2](https://www.stacksync.com/integrations/ibm-db2-and-sage-x3) - [Sage X3 and IBM Informix](https://www.stacksync.com/integrations/ibm-informix-and-sage-x3) - [Sage X3 and InterSystems IRIS](https://www.stacksync.com/integrations/intersystems-iris-and-sage-x3) - [Sage X3 and JDBC](https://www.stacksync.com/integrations/jdbc-and-sage-x3) - [Sage X3 and MariaDB](https://www.stacksync.com/integrations/mariadb-and-sage-x3) - [Sage X3 and MarkLogic](https://www.stacksync.com/integrations/marklogic-and-sage-x3) - [Sage X3 and MongoDB](https://www.stacksync.com/integrations/mongodb-and-sage-x3) - [Sage X3 and MySQL](https://www.stacksync.com/integrations/mysql-and-sage-x3) - [Sage X3 and Neo4j](https://www.stacksync.com/integrations/neo4j-and-sage-x3) - [Sage X3 and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/oci-database-and-sage-x3) - [Sage X3 and OpenSearch](https://www.stacksync.com/integrations/opensearch-and-sage-x3) - [Sage X3 and Oracle DB](https://www.stacksync.com/integrations/oracle-db-and-sage-x3) - [Sage X3 and Postgres Heroku](https://www.stacksync.com/integrations/postgres-heroku-and-sage-x3) - [Sage X3 and PostgreSQL](https://www.stacksync.com/integrations/postgresql-and-sage-x3) - [Sage X3 and RavenDB](https://www.stacksync.com/integrations/ravendb-and-sage-x3) - [Sage X3 and Redis Enterprise](https://www.stacksync.com/integrations/redis-enterprise-and-sage-x3) - [Sage X3 and Reltio](https://www.stacksync.com/integrations/reltio-and-sage-x3) - [Sage X3 and Render Postgres](https://www.stacksync.com/integrations/render-postgres-and-sage-x3) - [Sage X3 and SAP ASE (Sybase)](https://www.stacksync.com/integrations/sage-x3-and-sap-ase-sybase) - [Sage X3 and SAP HANA](https://www.stacksync.com/integrations/sage-x3-and-sap-hana) - [Sage X3 and Scaleway Postgres](https://www.stacksync.com/integrations/sage-x3-and-scaleway-postgres) - [Sage X3 and SingleStore](https://www.stacksync.com/integrations/sage-x3-and-singlestore) - [Sage X3 and SQL Server](https://www.stacksync.com/integrations/sage-x3-and-sql-server) - [Sage X3 and Supabase](https://www.stacksync.com/integrations/sage-x3-and-supabase) - [Sage X3 and TiDB](https://www.stacksync.com/integrations/sage-x3-and-tidb) - [Sage X3 and TimescaleDB](https://www.stacksync.com/integrations/sage-x3-and-timescaledb) - [Sage X3 and VoltDB](https://www.stacksync.com/integrations/sage-x3-and-voltdb) - [Sage X3 and YugabyteDB](https://www.stacksync.com/integrations/sage-x3-and-yugabytedb) ### Data warehouse · 29 - [Sage X3 and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-sage-x3) - [Sage X3 and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-sage-x3) - [Sage X3 and Apache Doris](https://www.stacksync.com/integrations/apache-doris-and-sage-x3) - [Sage X3 and Apache Druid](https://www.stacksync.com/integrations/apache-druid-and-sage-x3) - [Sage X3 and Apache Hive](https://www.stacksync.com/integrations/apache-hive-and-sage-x3) - [Sage X3 and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-sage-x3) - [Sage X3 and Apache Kylin](https://www.stacksync.com/integrations/apache-kylin-and-sage-x3) - [Sage X3 and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-sage-x3) - [Sage X3 and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-sage-x3) - [Sage X3 and BigQuery](https://www.stacksync.com/integrations/bigquery-and-sage-x3) - [Sage X3 and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-sage-x3) - [Sage X3 and Cloudera Data Platform](https://www.stacksync.com/integrations/cloudera-data-platform-and-sage-x3) - [Sage X3 and Databricks](https://www.stacksync.com/integrations/databricks-and-sage-x3) - [Sage X3 and Dremio](https://www.stacksync.com/integrations/dremio-and-sage-x3) - [Sage X3 and Exasol](https://www.stacksync.com/integrations/exasol-and-sage-x3) - [Sage X3 and Firebolt](https://www.stacksync.com/integrations/firebolt-and-sage-x3) - [Sage X3 and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-sage-x3) - [Sage X3 and Greenplum](https://www.stacksync.com/integrations/greenplum-and-sage-x3) - [Sage X3 and IBM Netezza](https://www.stacksync.com/integrations/ibm-netezza-and-sage-x3) - [Sage X3 and Materialize](https://www.stacksync.com/integrations/materialize-and-sage-x3) - [Sage X3 and MotherDuck](https://www.stacksync.com/integrations/motherduck-and-sage-x3) - [Sage X3 and Rockset](https://www.stacksync.com/integrations/rockset-and-sage-x3) - [Sage X3 and Snowflake](https://www.stacksync.com/integrations/sage-x3-and-snowflake) - [Sage X3 and Starburst Enterprise](https://www.stacksync.com/integrations/sage-x3-and-starburst-enterprise) - [Sage X3 and StarRocks](https://www.stacksync.com/integrations/sage-x3-and-starrocks) - [Sage X3 and Teradata Vantage](https://www.stacksync.com/integrations/sage-x3-and-teradata-vantage) - [Sage X3 and Tinybird](https://www.stacksync.com/integrations/sage-x3-and-tinybird) - [Sage X3 and Vertica](https://www.stacksync.com/integrations/sage-x3-and-vertica) - [Sage X3 and Yellowbrick](https://www.stacksync.com/integrations/sage-x3-and-yellowbrick) ### Business productivity · 28 - [Sage X3 and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-sage-x3) - [Sage X3 and Agiloft](https://www.stacksync.com/integrations/agiloft-and-sage-x3) - [Sage X3 and Amazon Seller Central](https://www.stacksync.com/integrations/amazon-seller-central-and-sage-x3) - [Sage X3 and Asana](https://www.stacksync.com/integrations/asana-and-sage-x3) - [Sage X3 and Braze](https://www.stacksync.com/integrations/braze-and-sage-x3) - [Sage X3 and Campfire](https://www.stacksync.com/integrations/campfire-and-sage-x3) - [Sage X3 and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-sage-x3) - [Sage X3 and Customer.io](https://www.stacksync.com/integrations/customer-io-and-sage-x3) - [Sage X3 and Docusign](https://www.stacksync.com/integrations/docusign-and-sage-x3) - [Sage X3 and Front](https://www.stacksync.com/integrations/front-and-sage-x3) - [Sage X3 and Gainsight](https://www.stacksync.com/integrations/gainsight-and-sage-x3) - [Sage X3 and Gatekeeper](https://www.stacksync.com/integrations/gatekeeper-and-sage-x3) - [Sage X3 and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-sage-x3) - [Sage X3 and Ironclad](https://www.stacksync.com/integrations/ironclad-and-sage-x3) - [Sage X3 and Klaviyo](https://www.stacksync.com/integrations/klaviyo-and-sage-x3) - [Sage X3 and Microsoft 365](https://www.stacksync.com/integrations/microsoft-365-and-sage-x3) - [Sage X3 and Microsoft Dynamics 365](https://www.stacksync.com/integrations/microsoft-dynamics-365-and-sage-x3) - [Sage X3 and Microsoft Teams](https://www.stacksync.com/integrations/microsoft-teams-and-sage-x3) - [Sage X3 and Monday](https://www.stacksync.com/integrations/monday-and-sage-x3) - [Sage X3 and Notion](https://www.stacksync.com/integrations/notion-and-sage-x3) - [Sage X3 and Orderful](https://www.stacksync.com/integrations/orderful-and-sage-x3) - [Sage X3 and Quip](https://www.stacksync.com/integrations/quip-and-sage-x3) - [Sage X3 and ServiceMax](https://www.stacksync.com/integrations/sage-x3-and-servicemax) - [Sage X3 and ServiceNow](https://www.stacksync.com/integrations/sage-x3-and-servicenow) - [Sage X3 and Smartsheet](https://www.stacksync.com/integrations/sage-x3-and-smartsheet) - [Sage X3 and SysAid](https://www.stacksync.com/integrations/sage-x3-and-sysaid) - [Sage X3 and Wrike](https://www.stacksync.com/integrations/sage-x3-and-wrike) - [Sage X3 and Zendesk](https://www.stacksync.com/integrations/sage-x3-and-zendesk) ### Accounting and finance · 17 - [Sage X3 and Adyen](https://www.stacksync.com/integrations/adyen-and-sage-x3) - [Sage X3 and Anaplan](https://www.stacksync.com/integrations/anaplan-and-sage-x3) - [Sage X3 and BILL](https://www.stacksync.com/integrations/bill-and-sage-x3) - [Sage X3 and Braintree](https://www.stacksync.com/integrations/braintree-and-sage-x3) - [Sage X3 and Chargebee](https://www.stacksync.com/integrations/chargebee-and-sage-x3) - [Sage X3 and Coupa](https://www.stacksync.com/integrations/coupa-and-sage-x3) - [Sage X3 and Hyperline](https://www.stacksync.com/integrations/hyperline-and-sage-x3) - [Sage X3 and LogiSense](https://www.stacksync.com/integrations/logisense-and-sage-x3) - [Sage X3 and Navan](https://www.stacksync.com/integrations/navan-and-sage-x3) - [Sage X3 and Pigment](https://www.stacksync.com/integrations/pigment-and-sage-x3) - [Sage X3 and QuickBooks](https://www.stacksync.com/integrations/quickbooks-and-sage-x3) - [Sage X3 and Ramp](https://www.stacksync.com/integrations/ramp-and-sage-x3) - [Sage X3 and Recurly](https://www.stacksync.com/integrations/recurly-and-sage-x3) - [Sage X3 and Rillet](https://www.stacksync.com/integrations/rillet-and-sage-x3) - [Sage X3 and Stripe](https://www.stacksync.com/integrations/sage-x3-and-stripe) - [Sage X3 and Workday](https://www.stacksync.com/integrations/sage-x3-and-workday) - [Sage X3 and Zuora](https://www.stacksync.com/integrations/sage-x3-and-zuora) ### AI · 5 - [Sage X3 and Anthropic](https://www.stacksync.com/integrations/anthropic-and-sage-x3) - [Sage X3 and Autopilot](https://www.stacksync.com/integrations/autopilot-and-sage-x3) - [Sage X3 and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-sage-x3) - [Sage X3 and OpenAI](https://www.stacksync.com/integrations/openai-and-sage-x3) - [Sage X3 and Pinecone](https://www.stacksync.com/integrations/pinecone-and-sage-x3) ### Analytics · 7 - [Sage X3 and Adobe Analytics](https://www.stacksync.com/integrations/adobeanalytics-and-sage-x3) - [Sage X3 and Microsoft Power BI](https://www.stacksync.com/integrations/microsoft-power-bi-and-sage-x3) - [Sage X3 and Mixpanel](https://www.stacksync.com/integrations/mixpanel-and-sage-x3) - [Sage X3 and Pendo](https://www.stacksync.com/integrations/pendo-and-sage-x3) - [Sage X3 and Splunk](https://www.stacksync.com/integrations/sage-x3-and-splunk) - [Sage X3 and Tableau](https://www.stacksync.com/integrations/sage-x3-and-tableau) - [Sage X3 and Treasure Data](https://www.stacksync.com/integrations/sage-x3-and-treasuredata) ### E-commerce · 8 - [Sage X3 and Akeneo](https://www.stacksync.com/integrations/akeneo-and-sage-x3) - [Sage X3 and BigCommerce](https://www.stacksync.com/integrations/bigcommerce-and-sage-x3) - [Sage X3 and ChannelEngine](https://www.stacksync.com/integrations/channelengine-and-sage-x3) - [Sage X3 and EasyPost](https://www.stacksync.com/integrations/easypost-and-sage-x3) - [Sage X3 and Magento](https://www.stacksync.com/integrations/magento-and-sage-x3) - [Sage X3 and NuORDER](https://www.stacksync.com/integrations/nuorder-and-sage-x3) - [Sage X3 and Shipwire](https://www.stacksync.com/integrations/sage-x3-and-shipwire) - [Sage X3 and Shopware](https://www.stacksync.com/integrations/sage-x3-and-shopware) ### Human resources · 14 - [Sage X3 and BambooHR](https://www.stacksync.com/integrations/bamboohr-and-sage-x3) - [Sage X3 and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-sage-x3) - [Sage X3 and D2L Brightspace](https://www.stacksync.com/integrations/d2l-brightspace-and-sage-x3) - [Sage X3 and Greenhouse](https://www.stacksync.com/integrations/greenhouse-and-sage-x3) - [Sage X3 and Hibob](https://www.stacksync.com/integrations/hibob-and-sage-x3) - [Sage X3 and Jobvite](https://www.stacksync.com/integrations/jobvite-and-sage-x3) - [Sage X3 and Lever](https://www.stacksync.com/integrations/lever-and-sage-x3) - [Sage X3 and Namely](https://www.stacksync.com/integrations/namely-and-sage-x3) - [Sage X3 and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/oracle-fusion-cloud-hcm-and-sage-x3) - [Sage X3 and Paylocity](https://www.stacksync.com/integrations/paylocity-and-sage-x3) - [Sage X3 and SmartRecruiters](https://www.stacksync.com/integrations/sage-x3-and-smartrecruiters) - [Sage X3 and Success Factors](https://www.stacksync.com/integrations/sage-x3-and-success-factors) - [Sage X3 and UKG Pro](https://www.stacksync.com/integrations/sage-x3-and-ukg-pro) - [Sage X3 and UKG Ready](https://www.stacksync.com/integrations/sage-x3-and-ukg-ready) ### Marketing · 9 - [Sage X3 and Bingads](https://www.stacksync.com/integrations/bingads-and-sage-x3) - [Sage X3 and Cvent](https://www.stacksync.com/integrations/cvent-and-sage-x3) - [Sage X3 and Demandbase](https://www.stacksync.com/integrations/demandbase-and-sage-x3) - [Sage X3 and Eloqua](https://www.stacksync.com/integrations/eloqua-and-sage-x3) - [Sage X3 and Iterable](https://www.stacksync.com/integrations/iterable-and-sage-x3) - [Sage X3 and Marketo](https://www.stacksync.com/integrations/marketo-and-sage-x3) - [Sage X3 and RollWorks](https://www.stacksync.com/integrations/rollworks-and-sage-x3) - [Sage X3 and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/sage-x3-and-salesforce-marketing-cloud) - [Sage X3 and Twitter Ads](https://www.stacksync.com/integrations/sage-x3-and-twitter-ads) ### Security and identity · 6 - [Sage X3 and Active Directory](https://www.stacksync.com/integrations/active-directory-and-sage-x3) - [Sage X3 and Auth0](https://www.stacksync.com/integrations/auth0-and-sage-x3) - [Sage X3 and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-sage-x3) - [Sage X3 and JumpCloud](https://www.stacksync.com/integrations/jumpcloud-and-sage-x3) - [Sage X3 and Okta](https://www.stacksync.com/integrations/okta-and-sage-x3) - [Sage X3 and OneLogin](https://www.stacksync.com/integrations/onelogin-and-sage-x3) ### Storage · 4 - [Sage X3 and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-sage-x3) - [Sage X3 and Box](https://www.stacksync.com/integrations/box-and-sage-x3) - [Sage X3 and Egnyte](https://www.stacksync.com/integrations/egnyte-and-sage-x3) - [Sage X3 and SharePoint](https://www.stacksync.com/integrations/sage-x3-and-sharepoint) SECURITY ## Security teams trust Stacksync 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. [Learn more about security](https://www.stacksync.com/security) | | | | --- | --- | | | SOC 2 Type II | | | ISO 27001 | | | HIPAA BAA | | | GDPR | | | CCPA | | | DPF US-EU-UK-CH | → SECURITY WITH BENEFITS ### 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: [OAuth 2](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more ## Connect the systems your business runs on. Build your next workflow with Stacksync. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)