--- title: "Crustdata connector: setup and compatibility | Stacksync" description: "Crustdata integration guide: plan Companies and People, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/crustdata last_modified: 2026-09-15 --- CRM · Two-way sync platform # Crustdata integration. Connect your Crustdata workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Companies, People and Headcount and Growth Metrics. - 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. - **Companies** - **People** - **Headcount and Growth Metrics** **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=crustdata) ## 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 ## Crustdata records to discuss. These Crustdata record examples help scope a technical review. They are not a list of verified Stacksync operations. Companies Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. People Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Headcount and Growth Metrics Identify a metric by definition/version, dimensions, time window, and entity key. ### See 3 more record examples Tech Stack Identify this record type and the operation you need to review with Stacksync. Screener Results Identify this record type and the operation you need to review with Stacksync. Enrichment Responses Identify this record type and the operation you need to review with Stacksync. Connection setup ## Crustdata connection requirements. Review Crustdata 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 Crustdata account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Crustdata, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Crustdata integration. Choose the owner of customer details, qualification, and commercial status separately. A customer update, a won deal, and an approved order represent different business decisions. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Crustdata **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 source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. Load related records in the right order Resolve parent organizations, business units, and currency references before dependent transactions. ### Mapping checks by record type #### Companies Confirm object support with Stacksync Identity Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. Fields to consider Source record ID · Legal or display name · Business-unit reference · Lifecycle status Related records to resolve first Resolve parent organizations, business units, and currency references before dependent transactions. Test before going live Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only. #### People Confirm object support with Stacksync Identity Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Fields to consider Source person ID · Display name · Email address · Organization reference · Consent state Related records to resolve first Resolve the organization relationship and any owner or consent references required by the destination. Test before going live Test an email change, two records sharing an email, and a person associated with multiple organizations. #### Headcount and Growth Metrics Confirm object support with Stacksync Identity Identify a metric by definition/version, dimensions, time window, and entity key. Fields to consider Metric definition · Entity reference · Time window · Value · Computed-at time Related records to resolve first Resolve entity keys, time zones, aggregation grain, and any currency/unit conversions. Test before going live Compare identical time windows and dimensions; test late-arriving data and a recalculated metric. [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 Crustdata integration in four steps. A changed contact detail updates the existing person; a sales-state change reaches only the downstream process approved to act on it. ### View the four setup tests and expected results 1. ### Confirm the intended Crustdata 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 Companies Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only. **Expected result:** A changed contact detail updates the existing person; a sales-state change reaches only the downstream process approved to act on it. 3. ### Test the operation your workflow needs Review one Crustdata 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 Crustdata integration. ### Diagnose record matching, delayed changes, and rejected operations A Crustdata record appears under the wrong destination record Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. Resolve parent organizations, business units, and currency references before dependent transactions. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Crustdata implementation’s change-detection method for Companies, People and Headcount and Growth Metrics. 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 Crustdata 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 Crustdata workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=crustdata) ## Crustdata integration guides - [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [guide Two-Way Sync Field Mapping Workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) FAQ ## Crustdata connector FAQ ### How should I plan an integration with Crustdata? Choose the owner of customer details, qualification, and commercial status separately. A customer update, a won deal, and an approved order represent different business decisions. 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 Crustdata connector write changes back? Write-back support is not established for this connection. Review the Crustdata records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Crustdata data? Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. ### Which related records should I load first for Crustdata? Resolve parent organizations, business units, and currency references before dependent transactions. ### How do I validate Crustdata changes after the initial load? Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only. A changed contact detail updates the existing person; a sales-state change reaches only the downstream process approved to act on it. ### How should I compare integration methods for Crustdata? Compare a vendor-native option if one exists, Stacksync, and a custom API or export against the same Companies, People and Headcount and Growth Metrics workflow. Confirm the connection and read/write operations with Stacksync. Test record matching, related data, update delay, and recovery. Include the ongoing work to handle schema changes and errors; a one-time export may be enough for a single copy. ## Explore Crustdata 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 - [Crustdata and Google Cloud Platform](https://www.stacksync.com/integrations/crustdata-and-google-cloud-platform) - [BigQuery and Crustdata](https://www.stacksync.com/integrations/bigquery-and-crustdata) - [Crustdata and Shopify](https://www.stacksync.com/integrations/crustdata-and-shopify) - [Crustdata and Gong](https://www.stacksync.com/integrations/crustdata-and-gong) - [Crustdata and HubSpot](https://www.stacksync.com/integrations/crustdata-and-hubspot) - [Crustdata and SugarCRM](https://www.stacksync.com/integrations/crustdata-and-sugarcrm) - [Crustdata and Databricks](https://www.stacksync.com/integrations/crustdata-and-databricks) - [Crustdata and Twitter Ads](https://www.stacksync.com/integrations/crustdata-and-twitter-ads) ### CRM · 26 - [Crustdata and Affinity](https://www.stacksync.com/integrations/affinity-and-crustdata) - [Crustdata and Attio](https://www.stacksync.com/integrations/attio-and-crustdata) - [Crustdata and Close](https://www.stacksync.com/integrations/close-and-crustdata) - [Crustdata and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-crustdata) - [Crustdata and Freshsales](https://www.stacksync.com/integrations/crustdata-and-freshsales) - [Crustdata and Freshworks CRM](https://www.stacksync.com/integrations/crustdata-and-freshworks-crm) - [Crustdata and Gong](https://www.stacksync.com/integrations/crustdata-and-gong) - [Crustdata and Gorgias](https://www.stacksync.com/integrations/crustdata-and-gorgias) - [Crustdata and HubSpot](https://www.stacksync.com/integrations/crustdata-and-hubspot) - [Crustdata and Infor CRM](https://www.stacksync.com/integrations/crustdata-and-infor-crm) - [Crustdata and Insightly](https://www.stacksync.com/integrations/crustdata-and-insightly) - [Crustdata and Intercom](https://www.stacksync.com/integrations/crustdata-and-intercom) - [Crustdata and Kommo](https://www.stacksync.com/integrations/crustdata-and-kommo) - [Crustdata and Outreach](https://www.stacksync.com/integrations/crustdata-and-outreach) - [Crustdata and Pipedrive](https://www.stacksync.com/integrations/crustdata-and-pipedrive) - [Crustdata and Salesforce](https://www.stacksync.com/integrations/crustdata-and-salesforce) - [Crustdata and Salesloft](https://www.stacksync.com/integrations/crustdata-and-salesloft) - [Crustdata and SAP Sales Cloud](https://www.stacksync.com/integrations/crustdata-and-sap-sales-cloud) - [Crustdata and Seismic](https://www.stacksync.com/integrations/crustdata-and-seismic) - [Crustdata and Shopify](https://www.stacksync.com/integrations/crustdata-and-shopify) - [Crustdata and SugarCRM](https://www.stacksync.com/integrations/crustdata-and-sugarcrm) - [Crustdata and Veeva CRM](https://www.stacksync.com/integrations/crustdata-and-veeva-crm) - [Crustdata and Vtiger CRM](https://www.stacksync.com/integrations/crustdata-and-vtiger-crm) - [Crustdata and Xactly](https://www.stacksync.com/integrations/crustdata-and-xactly) - [Crustdata and Zoho CRM](https://www.stacksync.com/integrations/crustdata-and-zoho-crm) - [Crustdata and Zoho SalesIQ](https://www.stacksync.com/integrations/crustdata-and-zoho-salesiq) ### Database · 11 - [Crustdata and Airtable](https://www.stacksync.com/integrations/airtable-and-crustdata) - [Crustdata and Elasticsearch](https://www.stacksync.com/integrations/crustdata-and-elasticsearch) - [Crustdata and Firebase](https://www.stacksync.com/integrations/crustdata-and-firebase) - [Crustdata and InfluxDB](https://www.stacksync.com/integrations/crustdata-and-influxdb) - [Crustdata and MongoDB](https://www.stacksync.com/integrations/crustdata-and-mongodb) - [Crustdata and MySQL](https://www.stacksync.com/integrations/crustdata-and-mysql) - [Crustdata and Neo4j](https://www.stacksync.com/integrations/crustdata-and-neo4j) - [Crustdata and PostgreSQL](https://www.stacksync.com/integrations/crustdata-and-postgresql) - [Crustdata and SAP HANA](https://www.stacksync.com/integrations/crustdata-and-sap-hana) - [Crustdata and SQL Server](https://www.stacksync.com/integrations/crustdata-and-sql-server) - [Crustdata and Supabase](https://www.stacksync.com/integrations/crustdata-and-supabase) ### Data warehouse · 8 - [Crustdata and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-crustdata) - [Crustdata and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-crustdata) - [Crustdata and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-crustdata) - [Crustdata and BigQuery](https://www.stacksync.com/integrations/bigquery-and-crustdata) - [Crustdata and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-crustdata) - [Crustdata and Databricks](https://www.stacksync.com/integrations/crustdata-and-databricks) - [Crustdata and Google Cloud Platform](https://www.stacksync.com/integrations/crustdata-and-google-cloud-platform) - [Crustdata and Snowflake](https://www.stacksync.com/integrations/crustdata-and-snowflake) ### Marketing · 7 - [Crustdata and Cvent](https://www.stacksync.com/integrations/crustdata-and-cvent) - [Crustdata and Demandbase](https://www.stacksync.com/integrations/crustdata-and-demandbase) - [Crustdata and Eloqua](https://www.stacksync.com/integrations/crustdata-and-eloqua) - [Crustdata and Iterable](https://www.stacksync.com/integrations/crustdata-and-iterable) - [Crustdata and Marketo](https://www.stacksync.com/integrations/crustdata-and-marketo) - [Crustdata and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/crustdata-and-salesforce-marketing-cloud) - [Crustdata and Twitter Ads](https://www.stacksync.com/integrations/crustdata-and-twitter-ads) 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/)