--- title: "Rootstock ERP connector: setup and compatibility | Stacksync" description: "Rootstock ERP integration guide: plan Bills of Material and Items / Products, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/rootstock-erp last_modified: 2026-09-15 --- ERP · Two-way sync platform # Rootstock ERP 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 Rootstock ERP workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Bills of Material, Items / Products and Sales Orders. 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. - **Sales Orders** - **Work Orders** - **Purchase 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=rootstock-erp) ## 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 ## Rootstock ERP records to discuss. These Rootstock ERP record examples help scope a technical review. They are not a list of verified Stacksync operations. Sales Orders Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices. Work Orders Identify this record type and the operation you need to review with Stacksync. Purchase Orders Retain purchase-order and line IDs together with the supplier and legal-entity context. ### See 3 more record examples Items / Products Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys. Bills of Material Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice. Inventory Balances Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient. Connection setup ## Rootstock ERP connection requirements. Review Rootstock ERP 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 Rootstock ERP account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Rootstock ERP, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Rootstock ERP 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 Rootstock ERP **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 Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice. Load related records in the right order Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines. ### Mapping checks by record type #### 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. #### Items / 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. #### Inventory Balances Confirm object support with Stacksync Identity Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient. Fields to consider Product reference · Location reference · Quantity type · Quantity · As-of time Related records to resolve first Resolve product, unit, warehouse/location, and lot/serial references. Test before going live Test the same SKU in two locations, a reservation, and an older snapshot arriving late. #### Receipts and Shipments Confirm object support with Stacksync Identity Retain shipment/fulfillment and line IDs, order reference, and carrier context. Fields to consider Source shipment ID · Order/line references · Carrier · Tracking reference · Fulfillment status Related records to resolve first Resolve order lines, delivery address, carrier, and any partial-fulfillment references. Test before going live Test split shipments, multiple tracking references, partial returns, and a carrier status arriving out of order. [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 Rootstock ERP 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. ### Confirm the intended Rootstock ERP account and grant After confirming an implementation path, validate the selected access method with the intended account and environment. Check that the authorizing user can grant access to the selected objects; test reauthorization without changing the mapped record identity. **Expected result:** The connection reaches the intended account, and the integration owner can renew or revoke the grant through the agreed procedure. 2. ### Test record matching for Bills of Material Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period. **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 Rootstock ERP 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 Rootstock ERP integration. ### Diagnose record matching, delayed changes, and rejected operations A Rootstock ERP record appears under the wrong destination record Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice. Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Rootstock ERP implementation’s change-detection method for Bills of Material, Items / Products and Sales Orders. 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 Rootstock ERP 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 Rootstock ERP workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=rootstock-erp) ## Rootstock ERP 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 ## Rootstock ERP connector FAQ ### How should I plan an integration with Rootstock ERP? 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 Rootstock ERP connector write changes back? Write-back support is not established for this connection. Review the Rootstock ERP records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Rootstock ERP data? Retain the supplier-bill ID, supplier, legal entity, and document reference; distinguish it from a customer invoice. ### Which related records should I load first for Rootstock ERP? Resolve supplier, expense/account codes, entity, currency, and accounting period before bill lines. ### How do I validate Rootstock ERP changes after the initial load? Test a duplicate supplier document number in another entity, a partially paid bill, and a closed period. 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 Rootstock ERP integration demo? Start with one workflow and a sample record from Bills of Material, Items / Products and Sales Orders. 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 Rootstock ERP 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 Rootstock ERP and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Rootstock ERP. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Rootstock ERP record changes.” - “Create a Genie that answers questions about our Rootstock ERP 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 Rootstock ERP 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 - [Rootstock ERP and Shopify](https://www.stacksync.com/integrations/rootstock-erp-and-shopify) - [Rootstock ERP and Salesforce](https://www.stacksync.com/integrations/rootstock-erp-and-salesforce) - [Rootstock ERP and Snowflake](https://www.stacksync.com/integrations/rootstock-erp-and-snowflake) - [HubSpot and Rootstock ERP](https://www.stacksync.com/integrations/hubspot-and-rootstock-erp) - [Rootstock ERP and Workday](https://www.stacksync.com/integrations/rootstock-erp-and-workday) - [Dynamics 365 Business Central and Rootstock ERP](https://www.stacksync.com/integrations/microsoft-dynamics-365-business-central-and-rootstock-erp) - [Rockset and Rootstock ERP](https://www.stacksync.com/integrations/rockset-and-rootstock-erp) - [NetSuite and Rootstock ERP](https://www.stacksync.com/integrations/netsuite-and-rootstock-erp) ### CRM · 30 - [Rootstock ERP and Affinity](https://www.stacksync.com/integrations/affinity-and-rootstock-erp) - [Rootstock ERP and Attio](https://www.stacksync.com/integrations/attio-and-rootstock-erp) - [Rootstock ERP and Chorusai](https://www.stacksync.com/integrations/chorusai-and-rootstock-erp) - [Rootstock ERP and Close](https://www.stacksync.com/integrations/close-and-rootstock-erp) - [Rootstock ERP and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-rootstock-erp) - [Rootstock ERP and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-rootstock-erp) - [Rootstock ERP and Freshsales](https://www.stacksync.com/integrations/freshsales-and-rootstock-erp) - [Rootstock ERP and Freshworks CRM](https://www.stacksync.com/integrations/freshworks-crm-and-rootstock-erp) - [Rootstock ERP and Gong](https://www.stacksync.com/integrations/gong-and-rootstock-erp) - [Rootstock ERP and Gorgias](https://www.stacksync.com/integrations/gorgias-and-rootstock-erp) - [Rootstock ERP and HubSpot](https://www.stacksync.com/integrations/hubspot-and-rootstock-erp) - [Rootstock ERP and Infor CRM](https://www.stacksync.com/integrations/infor-crm-and-rootstock-erp) - [Rootstock ERP and Insightly](https://www.stacksync.com/integrations/insightly-and-rootstock-erp) - [Rootstock ERP and Intercom](https://www.stacksync.com/integrations/intercom-and-rootstock-erp) - [Rootstock ERP and Kommo](https://www.stacksync.com/integrations/kommo-and-rootstock-erp) - [Rootstock ERP and Nimble](https://www.stacksync.com/integrations/nimble-and-rootstock-erp) - [Rootstock ERP and Outreach](https://www.stacksync.com/integrations/outreach-and-rootstock-erp) - [Rootstock ERP and Pipedrive](https://www.stacksync.com/integrations/pipedrive-and-rootstock-erp) - [Rootstock ERP and Salesforce](https://www.stacksync.com/integrations/rootstock-erp-and-salesforce) - [Rootstock ERP and Salesloft](https://www.stacksync.com/integrations/rootstock-erp-and-salesloft) - [Rootstock ERP and SAP Sales Cloud](https://www.stacksync.com/integrations/rootstock-erp-and-sap-sales-cloud) - [Rootstock ERP and Seismic](https://www.stacksync.com/integrations/rootstock-erp-and-seismic) - [Rootstock ERP and Shopify](https://www.stacksync.com/integrations/rootstock-erp-and-shopify) - [Rootstock ERP and SugarCRM](https://www.stacksync.com/integrations/rootstock-erp-and-sugarcrm) - [Rootstock ERP and Veeva CRM](https://www.stacksync.com/integrations/rootstock-erp-and-veeva-crm) - [Rootstock ERP and Vtiger CRM](https://www.stacksync.com/integrations/rootstock-erp-and-vtiger-crm) - [Rootstock ERP and Xactly](https://www.stacksync.com/integrations/rootstock-erp-and-xactly) - [Rootstock ERP and Zoho CRM](https://www.stacksync.com/integrations/rootstock-erp-and-zoho-crm) - [Rootstock ERP and Zoho SalesIQ](https://www.stacksync.com/integrations/rootstock-erp-and-zoho-salesiq) - [Rootstock ERP and ZoomInfo](https://www.stacksync.com/integrations/rootstock-erp-and-zoominfo) ### ERP · 24 - [Rootstock ERP and Acumatica](https://www.stacksync.com/integrations/acumatica-and-rootstock-erp) - [Rootstock ERP and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-rootstock-erp) - [Rootstock ERP and Cin7](https://www.stacksync.com/integrations/cin7-and-rootstock-erp) - [Rootstock ERP and Dynamics 365 Business Central](https://www.stacksync.com/integrations/microsoft-dynamics-365-business-central-and-rootstock-erp) - [Rootstock ERP and Epicor ERP](https://www.stacksync.com/integrations/epicor-erp-and-rootstock-erp) - [Rootstock ERP and Infor LN](https://www.stacksync.com/integrations/infor-ln-and-rootstock-erp) - [Rootstock ERP and Infor M3](https://www.stacksync.com/integrations/infor-m3-and-rootstock-erp) - [Rootstock ERP and Linnworks](https://www.stacksync.com/integrations/linnworks-and-rootstock-erp) - [Rootstock ERP and Microsoft Dynamics GP](https://www.stacksync.com/integrations/microsoft-dynamics-gp-and-rootstock-erp) - [Rootstock ERP and Microsoft Dynamics NAV](https://www.stacksync.com/integrations/microsoft-dynamics-nav-and-rootstock-erp) - [Rootstock ERP and NetSuite](https://www.stacksync.com/integrations/netsuite-and-rootstock-erp) - [Rootstock ERP and Odoo](https://www.stacksync.com/integrations/odoo-and-rootstock-erp) - [Rootstock ERP and Plex ERP](https://www.stacksync.com/integrations/plex-erp-and-rootstock-erp) - [Rootstock ERP and QAD ERP](https://www.stacksync.com/integrations/qad-erp-and-rootstock-erp) - [Rootstock ERP and Sage 100](https://www.stacksync.com/integrations/rootstock-erp-and-sage-100) - [Rootstock ERP and Sage 300](https://www.stacksync.com/integrations/rootstock-erp-and-sage-300) - [Rootstock ERP and Sage Intacct](https://www.stacksync.com/integrations/rootstock-erp-and-sage-intacct) - [Rootstock ERP and Sage X3](https://www.stacksync.com/integrations/rootstock-erp-and-sage-x3) - [Rootstock ERP and SAP](https://www.stacksync.com/integrations/rootstock-erp-and-sap) - [Rootstock ERP and SAP Business ByDesign](https://www.stacksync.com/integrations/rootstock-erp-and-sap-business-bydesign) - [Rootstock ERP and SAP Business One](https://www.stacksync.com/integrations/rootstock-erp-and-sap-business-one) - [Rootstock ERP and SAP S/4HANA](https://www.stacksync.com/integrations/rootstock-erp-and-sap-s4hana) - [Rootstock ERP and Syspro](https://www.stacksync.com/integrations/rootstock-erp-and-syspro) - [Rootstock ERP and TikTok Shop](https://www.stacksync.com/integrations/rootstock-erp-and-tiktok) ### Database · 12 - [Rootstock ERP and Airtable](https://www.stacksync.com/integrations/airtable-and-rootstock-erp) - [Rootstock ERP and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-rootstock-erp) - [Rootstock ERP and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-rootstock-erp) - [Rootstock ERP and Firebase](https://www.stacksync.com/integrations/firebase-and-rootstock-erp) - [Rootstock ERP and MongoDB](https://www.stacksync.com/integrations/mongodb-and-rootstock-erp) - [Rootstock ERP and MySQL](https://www.stacksync.com/integrations/mysql-and-rootstock-erp) - [Rootstock ERP and Neo4j](https://www.stacksync.com/integrations/neo4j-and-rootstock-erp) - [Rootstock ERP and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/oci-database-and-rootstock-erp) - [Rootstock ERP and PostgreSQL](https://www.stacksync.com/integrations/postgresql-and-rootstock-erp) - [Rootstock ERP and SAP HANA](https://www.stacksync.com/integrations/rootstock-erp-and-sap-hana) - [Rootstock ERP and SQL Server](https://www.stacksync.com/integrations/rootstock-erp-and-sql-server) - [Rootstock ERP and Supabase](https://www.stacksync.com/integrations/rootstock-erp-and-supabase) ### Data warehouse · 9 - [Rootstock ERP and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-rootstock-erp) - [Rootstock ERP and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-rootstock-erp) - [Rootstock ERP and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-rootstock-erp) - [Rootstock ERP and BigQuery](https://www.stacksync.com/integrations/bigquery-and-rootstock-erp) - [Rootstock ERP and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-rootstock-erp) - [Rootstock ERP and Databricks](https://www.stacksync.com/integrations/databricks-and-rootstock-erp) - [Rootstock ERP and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-rootstock-erp) - [Rootstock ERP and Rockset](https://www.stacksync.com/integrations/rockset-and-rootstock-erp) - [Rootstock ERP and Snowflake](https://www.stacksync.com/integrations/rootstock-erp-and-snowflake) ### Business productivity · 22 - [Rootstock ERP and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-rootstock-erp) - [Rootstock ERP and Amazon Seller Central](https://www.stacksync.com/integrations/amazon-seller-central-and-rootstock-erp) - [Rootstock ERP and Asana](https://www.stacksync.com/integrations/asana-and-rootstock-erp) - [Rootstock ERP and Braze](https://www.stacksync.com/integrations/braze-and-rootstock-erp) - [Rootstock ERP and Campfire](https://www.stacksync.com/integrations/campfire-and-rootstock-erp) - [Rootstock ERP and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-rootstock-erp) - [Rootstock ERP and Docusign](https://www.stacksync.com/integrations/docusign-and-rootstock-erp) - [Rootstock ERP and Front](https://www.stacksync.com/integrations/front-and-rootstock-erp) - [Rootstock ERP and Gainsight](https://www.stacksync.com/integrations/gainsight-and-rootstock-erp) - [Rootstock ERP and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-rootstock-erp) - [Rootstock ERP and Ironclad](https://www.stacksync.com/integrations/ironclad-and-rootstock-erp) - [Rootstock ERP and Klaviyo](https://www.stacksync.com/integrations/klaviyo-and-rootstock-erp) - [Rootstock ERP and Microsoft Dynamics 365](https://www.stacksync.com/integrations/microsoft-dynamics-365-and-rootstock-erp) - [Rootstock ERP and Microsoft Teams](https://www.stacksync.com/integrations/microsoft-teams-and-rootstock-erp) - [Rootstock ERP and Monday](https://www.stacksync.com/integrations/monday-and-rootstock-erp) - [Rootstock ERP and Notion](https://www.stacksync.com/integrations/notion-and-rootstock-erp) - [Rootstock ERP and Quip](https://www.stacksync.com/integrations/quip-and-rootstock-erp) - [Rootstock ERP and ServiceMax](https://www.stacksync.com/integrations/rootstock-erp-and-servicemax) - [Rootstock ERP and Smartsheet](https://www.stacksync.com/integrations/rootstock-erp-and-smartsheet) - [Rootstock ERP and SysAid](https://www.stacksync.com/integrations/rootstock-erp-and-sysaid) - [Rootstock ERP and Wrike](https://www.stacksync.com/integrations/rootstock-erp-and-wrike) - [Rootstock ERP and Zendesk](https://www.stacksync.com/integrations/rootstock-erp-and-zendesk) ### Accounting and finance · 13 - [Rootstock ERP and Adyen](https://www.stacksync.com/integrations/adyen-and-rootstock-erp) - [Rootstock ERP and Anaplan](https://www.stacksync.com/integrations/anaplan-and-rootstock-erp) - [Rootstock ERP and BILL](https://www.stacksync.com/integrations/bill-and-rootstock-erp) - [Rootstock ERP and Braintree](https://www.stacksync.com/integrations/braintree-and-rootstock-erp) - [Rootstock ERP and Chargebee](https://www.stacksync.com/integrations/chargebee-and-rootstock-erp) - [Rootstock ERP and Coupa](https://www.stacksync.com/integrations/coupa-and-rootstock-erp) - [Rootstock ERP and Navan](https://www.stacksync.com/integrations/navan-and-rootstock-erp) - [Rootstock ERP and QuickBooks](https://www.stacksync.com/integrations/quickbooks-and-rootstock-erp) - [Rootstock ERP and Ramp](https://www.stacksync.com/integrations/ramp-and-rootstock-erp) - [Rootstock ERP and Recurly](https://www.stacksync.com/integrations/recurly-and-rootstock-erp) - [Rootstock ERP and Stripe](https://www.stacksync.com/integrations/rootstock-erp-and-stripe) - [Rootstock ERP and Workday](https://www.stacksync.com/integrations/rootstock-erp-and-workday) - [Rootstock ERP and Zuora](https://www.stacksync.com/integrations/rootstock-erp-and-zuora) ### AI · 4 - [Rootstock ERP and Autopilot](https://www.stacksync.com/integrations/autopilot-and-rootstock-erp) - [Rootstock ERP and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-rootstock-erp) - [Rootstock ERP and OpenAI](https://www.stacksync.com/integrations/openai-and-rootstock-erp) - [Rootstock ERP and Pinecone](https://www.stacksync.com/integrations/pinecone-and-rootstock-erp) ### Analytics · 6 - [Rootstock ERP and Adobe Analytics](https://www.stacksync.com/integrations/adobeanalytics-and-rootstock-erp) - [Rootstock ERP and Microsoft Power BI](https://www.stacksync.com/integrations/microsoft-power-bi-and-rootstock-erp) - [Rootstock ERP and Mixpanel](https://www.stacksync.com/integrations/mixpanel-and-rootstock-erp) - [Rootstock ERP and Pendo](https://www.stacksync.com/integrations/pendo-and-rootstock-erp) - [Rootstock ERP and Splunk](https://www.stacksync.com/integrations/rootstock-erp-and-splunk) - [Rootstock ERP and Tableau](https://www.stacksync.com/integrations/rootstock-erp-and-tableau) ### E-commerce · 6 - [Rootstock ERP and Akeneo](https://www.stacksync.com/integrations/akeneo-and-rootstock-erp) - [Rootstock ERP and BigCommerce](https://www.stacksync.com/integrations/bigcommerce-and-rootstock-erp) - [Rootstock ERP and EasyPost](https://www.stacksync.com/integrations/easypost-and-rootstock-erp) - [Rootstock ERP and Magento](https://www.stacksync.com/integrations/magento-and-rootstock-erp) - [Rootstock ERP and Shipwire](https://www.stacksync.com/integrations/rootstock-erp-and-shipwire) - [Rootstock ERP and Shopware](https://www.stacksync.com/integrations/rootstock-erp-and-shopware) ### Human resources · 12 - [Rootstock ERP and BambooHR](https://www.stacksync.com/integrations/bamboohr-and-rootstock-erp) - [Rootstock ERP and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-rootstock-erp) - [Rootstock ERP and Greenhouse](https://www.stacksync.com/integrations/greenhouse-and-rootstock-erp) - [Rootstock ERP and Hibob](https://www.stacksync.com/integrations/hibob-and-rootstock-erp) - [Rootstock ERP and Jobvite](https://www.stacksync.com/integrations/jobvite-and-rootstock-erp) - [Rootstock ERP and Lever](https://www.stacksync.com/integrations/lever-and-rootstock-erp) - [Rootstock ERP and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/oracle-fusion-cloud-hcm-and-rootstock-erp) - [Rootstock ERP and Paylocity](https://www.stacksync.com/integrations/paylocity-and-rootstock-erp) - [Rootstock ERP and SmartRecruiters](https://www.stacksync.com/integrations/rootstock-erp-and-smartrecruiters) - [Rootstock ERP and Success Factors](https://www.stacksync.com/integrations/rootstock-erp-and-success-factors) - [Rootstock ERP and UKG Pro](https://www.stacksync.com/integrations/rootstock-erp-and-ukg-pro) - [Rootstock ERP and UKG Ready](https://www.stacksync.com/integrations/rootstock-erp-and-ukg-ready) ### Marketing · 8 - [Rootstock ERP and Bingads](https://www.stacksync.com/integrations/bingads-and-rootstock-erp) - [Rootstock ERP and Cvent](https://www.stacksync.com/integrations/cvent-and-rootstock-erp) - [Rootstock ERP and Demandbase](https://www.stacksync.com/integrations/demandbase-and-rootstock-erp) - [Rootstock ERP and Eloqua](https://www.stacksync.com/integrations/eloqua-and-rootstock-erp) - [Rootstock ERP and Iterable](https://www.stacksync.com/integrations/iterable-and-rootstock-erp) - [Rootstock ERP and Marketo](https://www.stacksync.com/integrations/marketo-and-rootstock-erp) - [Rootstock ERP and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/rootstock-erp-and-salesforce-marketing-cloud) - [Rootstock ERP and Twitter Ads](https://www.stacksync.com/integrations/rootstock-erp-and-twitter-ads) ### Security and identity · 6 - [Rootstock ERP and Active Directory](https://www.stacksync.com/integrations/active-directory-and-rootstock-erp) - [Rootstock ERP and Auth0](https://www.stacksync.com/integrations/auth0-and-rootstock-erp) - [Rootstock ERP and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-rootstock-erp) - [Rootstock ERP and JumpCloud](https://www.stacksync.com/integrations/jumpcloud-and-rootstock-erp) - [Rootstock ERP and Okta](https://www.stacksync.com/integrations/okta-and-rootstock-erp) - [Rootstock ERP and OneLogin](https://www.stacksync.com/integrations/onelogin-and-rootstock-erp) ### Storage · 4 - [Rootstock ERP and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-rootstock-erp) - [Rootstock ERP and Box](https://www.stacksync.com/integrations/box-and-rootstock-erp) - [Rootstock ERP and Egnyte](https://www.stacksync.com/integrations/egnyte-and-rootstock-erp) - [Rootstock ERP and SharePoint](https://www.stacksync.com/integrations/rootstock-erp-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/)