--- title: "Vitally connector: setup and compatibility | Stacksync" description: "Vitally integration guide: plan Account and User, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/vitally last_modified: 2026-09-15 --- CRM · Two-way sync platform # Vitally integration. Connect your Vitally workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Account, User and Task. - 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. - **Account** - **User** - **Organization** **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=vitally) ## 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 ## Vitally records to discuss. These Vitally record examples help scope a technical review. They are not a list of verified Stacksync operations. Account 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. User Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. Organization Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Task Use a stable task/work-item ID and preserve its project or parent-ticket reference. Note Identify this record type and the operation you need to review with Stacksync. Conversation Retain message ID, conversation/thread ID, channel, and sender identity. Connection setup ## Vitally connection requirements. Review Vitally 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 Vitally account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Vitally, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Vitally 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 Vitally **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 #### Account 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. #### User Confirm object support with Stacksync Identity Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. Fields to consider Source user ID · Tenant reference · Account status · Group references Related records to resolve first Resolve tenant and group references and establish a protected administrative-account policy. Test before going live Test a renamed login, disabled account, missing group, and a user existing in two tenants. #### Task Confirm object support with Stacksync Identity Use a stable task/work-item ID and preserve its project or parent-ticket reference. Fields to consider Source task ID · Parent reference · Assignee · Status · Due date Related records to resolve first Resolve project, user, and parent-item references before the task. Test before going live Test a reassignment, an unsupported status transition, a deleted parent, and a due date across time zones. #### Conversation Confirm object support with Stacksync Identity Retain message ID, conversation/thread ID, channel, and sender identity. Fields to consider Source message ID · Thread reference · Delivery state · Timestamp · Related record ID Related records to resolve first Resolve conversation, participant, and customer context before associating messages. Test before going live Test a delivery-state change, repeated message, private conversation, and reply linked to the correct thread. [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 Vitally 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. ### Verify Vitally 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 Account 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 Vitally 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 Vitally integration. ### Diagnose record matching, delayed changes, and rejected operations A Vitally 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 Vitally implementation’s change-detection method for Account, User and Task. 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 Vitally 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 Vitally workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=vitally) ## Vitally 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 ## Vitally connector FAQ ### How should I plan an integration with Vitally? 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 Vitally connector write changes back? Write-back support is not established for this connection. Review the Vitally records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Vitally 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 Vitally? Resolve parent organizations, business units, and currency references before dependent transactions. ### How do I validate Vitally 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. ### What will we cover in a Vitally integration demo? Start with one workflow and a sample record from Account, User and Task. 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. ## Explore Vitally 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 - [HubSpot and Vitally](https://www.stacksync.com/integrations/hubspot-and-vitally) - [Vitally and Zendesk](https://www.stacksync.com/integrations/vitally-and-zendesk) - [BigQuery and Vitally](https://www.stacksync.com/integrations/bigquery-and-vitally) - [Amazon Redshift and Vitally](https://www.stacksync.com/integrations/amazon-redshift-and-vitally) - [Salesforce and Vitally](https://www.stacksync.com/integrations/salesforce-and-vitally) - [Twitter Ads and Vitally](https://www.stacksync.com/integrations/twitter-ads-and-vitally) - [Snowflake and Vitally](https://www.stacksync.com/integrations/snowflake-and-vitally) - [Campfire and Vitally](https://www.stacksync.com/integrations/campfire-and-vitally) ### CRM · 31 - [Vitally and 6sense](https://www.stacksync.com/integrations/6sense-and-vitally) - [Vitally and Affinity](https://www.stacksync.com/integrations/affinity-and-vitally) - [Vitally and Attio](https://www.stacksync.com/integrations/attio-and-vitally) - [Vitally and Chorusai](https://www.stacksync.com/integrations/chorusai-and-vitally) - [Vitally and Clearbit](https://www.stacksync.com/integrations/clearbit-and-vitally) - [Vitally and Close](https://www.stacksync.com/integrations/close-and-vitally) - [Vitally and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-vitally) - [Vitally and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-vitally) - [Vitally and Freshsales](https://www.stacksync.com/integrations/freshsales-and-vitally) - [Vitally and Freshworks CRM](https://www.stacksync.com/integrations/freshworks-crm-and-vitally) - [Vitally and Gong](https://www.stacksync.com/integrations/gong-and-vitally) - [Vitally and Gorgias](https://www.stacksync.com/integrations/gorgias-and-vitally) - [Vitally and HubSpot](https://www.stacksync.com/integrations/hubspot-and-vitally) - [Vitally and Infor CRM](https://www.stacksync.com/integrations/infor-crm-and-vitally) - [Vitally and Insightly](https://www.stacksync.com/integrations/insightly-and-vitally) - [Vitally and Intercom](https://www.stacksync.com/integrations/intercom-and-vitally) - [Vitally and Kommo](https://www.stacksync.com/integrations/kommo-and-vitally) - [Vitally and Outreach](https://www.stacksync.com/integrations/outreach-and-vitally) - [Vitally and Pipedrive](https://www.stacksync.com/integrations/pipedrive-and-vitally) - [Vitally and Salesforce](https://www.stacksync.com/integrations/salesforce-and-vitally) - [Vitally and Salesloft](https://www.stacksync.com/integrations/salesloft-and-vitally) - [Vitally and SAP Sales Cloud](https://www.stacksync.com/integrations/sap-sales-cloud-and-vitally) - [Vitally and Seismic](https://www.stacksync.com/integrations/seismic-and-vitally) - [Vitally and Shopify](https://www.stacksync.com/integrations/shopify-and-vitally) - [Vitally and SugarCRM](https://www.stacksync.com/integrations/sugarcrm-and-vitally) - [Vitally and Veeva CRM](https://www.stacksync.com/integrations/veeva-crm-and-vitally) - [Vitally and Vtiger CRM](https://www.stacksync.com/integrations/vitally-and-vtiger-crm) - [Vitally and Xactly](https://www.stacksync.com/integrations/vitally-and-xactly) - [Vitally and Zoho CRM](https://www.stacksync.com/integrations/vitally-and-zoho-crm) - [Vitally and Zoho SalesIQ](https://www.stacksync.com/integrations/vitally-and-zoho-salesiq) - [Vitally and ZoomInfo](https://www.stacksync.com/integrations/vitally-and-zoominfo) ### ERP · 19 - [Vitally and Acumatica](https://www.stacksync.com/integrations/acumatica-and-vitally) - [Vitally and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-vitally) - [Vitally and Cin7](https://www.stacksync.com/integrations/cin7-and-vitally) - [Vitally and Epicor ERP](https://www.stacksync.com/integrations/epicor-erp-and-vitally) - [Vitally and Infor LN](https://www.stacksync.com/integrations/infor-ln-and-vitally) - [Vitally and Infor M3](https://www.stacksync.com/integrations/infor-m3-and-vitally) - [Vitally and Linnworks](https://www.stacksync.com/integrations/linnworks-and-vitally) - [Vitally and NetSuite](https://www.stacksync.com/integrations/netsuite-and-vitally) - [Vitally and Odoo](https://www.stacksync.com/integrations/odoo-and-vitally) - [Vitally and Plex ERP](https://www.stacksync.com/integrations/plex-erp-and-vitally) - [Vitally and QAD ERP](https://www.stacksync.com/integrations/qad-erp-and-vitally) - [Vitally and Sage 100](https://www.stacksync.com/integrations/sage-100-and-vitally) - [Vitally and Sage 300](https://www.stacksync.com/integrations/sage-300-and-vitally) - [Vitally and Sage Intacct](https://www.stacksync.com/integrations/sage-intacct-and-vitally) - [Vitally and Sage X3](https://www.stacksync.com/integrations/sage-x3-and-vitally) - [Vitally and SAP](https://www.stacksync.com/integrations/sap-and-vitally) - [Vitally and SAP Business ByDesign](https://www.stacksync.com/integrations/sap-business-bydesign-and-vitally) - [Vitally and SAP Business One](https://www.stacksync.com/integrations/sap-business-one-and-vitally) - [Vitally and SAP S/4HANA](https://www.stacksync.com/integrations/sap-s4hana-and-vitally) ### Database · 9 - [Vitally and Airtable](https://www.stacksync.com/integrations/airtable-and-vitally) - [Vitally and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-vitally) - [Vitally and MariaDB](https://www.stacksync.com/integrations/mariadb-and-vitally) - [Vitally and MongoDB](https://www.stacksync.com/integrations/mongodb-and-vitally) - [Vitally and MySQL](https://www.stacksync.com/integrations/mysql-and-vitally) - [Vitally and PostgreSQL](https://www.stacksync.com/integrations/postgresql-and-vitally) - [Vitally and SAP HANA](https://www.stacksync.com/integrations/sap-hana-and-vitally) - [Vitally and SQL Server](https://www.stacksync.com/integrations/sql-server-and-vitally) - [Vitally and Supabase](https://www.stacksync.com/integrations/supabase-and-vitally) ### Data warehouse · 8 - [Vitally and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-vitally) - [Vitally and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-vitally) - [Vitally and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-vitally) - [Vitally and BigQuery](https://www.stacksync.com/integrations/bigquery-and-vitally) - [Vitally and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-vitally) - [Vitally and Databricks](https://www.stacksync.com/integrations/databricks-and-vitally) - [Vitally and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-vitally) - [Vitally and Snowflake](https://www.stacksync.com/integrations/snowflake-and-vitally) ### Business productivity · 29 - [Vitally and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-vitally) - [Vitally and Amazon Seller Central](https://www.stacksync.com/integrations/amazon-seller-central-and-vitally) - [Vitally and Asana](https://www.stacksync.com/integrations/asana-and-vitally) - [Vitally and Atlassian](https://www.stacksync.com/integrations/atlassian-and-vitally) - [Vitally and Braze](https://www.stacksync.com/integrations/braze-and-vitally) - [Vitally and Campfire](https://www.stacksync.com/integrations/campfire-and-vitally) - [Vitally and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-vitally) - [Vitally and Docusign](https://www.stacksync.com/integrations/docusign-and-vitally) - [Vitally and Front](https://www.stacksync.com/integrations/front-and-vitally) - [Vitally and Gainsight](https://www.stacksync.com/integrations/gainsight-and-vitally) - [Vitally and GitHub](https://www.stacksync.com/integrations/github-and-vitally) - [Vitally and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-vitally) - [Vitally and Ironclad](https://www.stacksync.com/integrations/ironclad-and-vitally) - [Vitally and Klaviyo](https://www.stacksync.com/integrations/klaviyo-and-vitally) - [Vitally and Lusha](https://www.stacksync.com/integrations/lusha-and-vitally) - [Vitally and Microsoft 365](https://www.stacksync.com/integrations/microsoft-365-and-vitally) - [Vitally and Microsoft Dynamics 365](https://www.stacksync.com/integrations/microsoft-dynamics-365-and-vitally) - [Vitally and Monday](https://www.stacksync.com/integrations/monday-and-vitally) - [Vitally and Notion](https://www.stacksync.com/integrations/notion-and-vitally) - [Vitally and Quip](https://www.stacksync.com/integrations/quip-and-vitally) - [Vitally and Resend](https://www.stacksync.com/integrations/resend-and-vitally) - [Vitally and SendGrid](https://www.stacksync.com/integrations/sendgrid-and-vitally) - [Vitally and ServiceMax](https://www.stacksync.com/integrations/servicemax-and-vitally) - [Vitally and ServiceNow](https://www.stacksync.com/integrations/servicenow-and-vitally) - [Vitally and Smartsheet](https://www.stacksync.com/integrations/smartsheet-and-vitally) - [Vitally and SysAid](https://www.stacksync.com/integrations/sysaid-and-vitally) - [Vitally and Twilio](https://www.stacksync.com/integrations/twilio-and-vitally) - [Vitally and Wrike](https://www.stacksync.com/integrations/vitally-and-wrike) - [Vitally and Zendesk](https://www.stacksync.com/integrations/vitally-and-zendesk) ### Accounting and finance · 12 - [Vitally and Adyen](https://www.stacksync.com/integrations/adyen-and-vitally) - [Vitally and Anaplan](https://www.stacksync.com/integrations/anaplan-and-vitally) - [Vitally and BILL](https://www.stacksync.com/integrations/bill-and-vitally) - [Vitally and Braintree](https://www.stacksync.com/integrations/braintree-and-vitally) - [Vitally and Chargebee](https://www.stacksync.com/integrations/chargebee-and-vitally) - [Vitally and Coupa](https://www.stacksync.com/integrations/coupa-and-vitally) - [Vitally and Navan](https://www.stacksync.com/integrations/navan-and-vitally) - [Vitally and QuickBooks](https://www.stacksync.com/integrations/quickbooks-and-vitally) - [Vitally and Ramp](https://www.stacksync.com/integrations/ramp-and-vitally) - [Vitally and Recurly](https://www.stacksync.com/integrations/recurly-and-vitally) - [Vitally and Stripe](https://www.stacksync.com/integrations/stripe-and-vitally) - [Vitally and Zuora](https://www.stacksync.com/integrations/vitally-and-zuora) ### AI · 4 - [Vitally and Autopilot](https://www.stacksync.com/integrations/autopilot-and-vitally) - [Vitally and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-vitally) - [Vitally and OpenAI](https://www.stacksync.com/integrations/openai-and-vitally) - [Vitally and Pinecone](https://www.stacksync.com/integrations/pinecone-and-vitally) ### Analytics · 6 - [Vitally and Adobe Analytics](https://www.stacksync.com/integrations/adobeanalytics-and-vitally) - [Vitally and Microsoft Power BI](https://www.stacksync.com/integrations/microsoft-power-bi-and-vitally) - [Vitally and Mixpanel](https://www.stacksync.com/integrations/mixpanel-and-vitally) - [Vitally and Pendo](https://www.stacksync.com/integrations/pendo-and-vitally) - [Vitally and Splunk](https://www.stacksync.com/integrations/splunk-and-vitally) - [Vitally and Tableau](https://www.stacksync.com/integrations/tableau-and-vitally) ### Communications · 6 - [Vitally and Aircall](https://www.stacksync.com/integrations/aircall-and-vitally) - [Vitally and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-vitally) - [Vitally and Gmail](https://www.stacksync.com/integrations/gmail-and-vitally) - [Vitally and Infobip](https://www.stacksync.com/integrations/infobip-and-vitally) - [Vitally and RingCentral](https://www.stacksync.com/integrations/ringcentral-and-vitally) - [Vitally and Zoom](https://www.stacksync.com/integrations/vitally-and-zoom) ### E-commerce · 6 - [Vitally and Akeneo](https://www.stacksync.com/integrations/akeneo-and-vitally) - [Vitally and BigCommerce](https://www.stacksync.com/integrations/bigcommerce-and-vitally) - [Vitally and EasyPost](https://www.stacksync.com/integrations/easypost-and-vitally) - [Vitally and Magento](https://www.stacksync.com/integrations/magento-and-vitally) - [Vitally and Shipwire](https://www.stacksync.com/integrations/shipwire-and-vitally) - [Vitally and Shopware](https://www.stacksync.com/integrations/shopware-and-vitally) ### Human resources · 11 - [Vitally and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-vitally) - [Vitally and Greenhouse](https://www.stacksync.com/integrations/greenhouse-and-vitally) - [Vitally and Hibob](https://www.stacksync.com/integrations/hibob-and-vitally) - [Vitally and Jobvite](https://www.stacksync.com/integrations/jobvite-and-vitally) - [Vitally and Lever](https://www.stacksync.com/integrations/lever-and-vitally) - [Vitally and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/oracle-fusion-cloud-hcm-and-vitally) - [Vitally and Paylocity](https://www.stacksync.com/integrations/paylocity-and-vitally) - [Vitally and SmartRecruiters](https://www.stacksync.com/integrations/smartrecruiters-and-vitally) - [Vitally and Success Factors](https://www.stacksync.com/integrations/success-factors-and-vitally) - [Vitally and UKG Pro](https://www.stacksync.com/integrations/ukg-pro-and-vitally) - [Vitally and UKG Ready](https://www.stacksync.com/integrations/ukg-ready-and-vitally) ### Marketing · 8 - [Vitally and Bingads](https://www.stacksync.com/integrations/bingads-and-vitally) - [Vitally and Cvent](https://www.stacksync.com/integrations/cvent-and-vitally) - [Vitally and Demandbase](https://www.stacksync.com/integrations/demandbase-and-vitally) - [Vitally and Eloqua](https://www.stacksync.com/integrations/eloqua-and-vitally) - [Vitally and Iterable](https://www.stacksync.com/integrations/iterable-and-vitally) - [Vitally and Marketo](https://www.stacksync.com/integrations/marketo-and-vitally) - [Vitally and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/salesforce-marketing-cloud-and-vitally) - [Vitally and Twitter Ads](https://www.stacksync.com/integrations/twitter-ads-and-vitally) ### Security and identity · 6 - [Vitally and Active Directory](https://www.stacksync.com/integrations/active-directory-and-vitally) - [Vitally and Auth0](https://www.stacksync.com/integrations/auth0-and-vitally) - [Vitally and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-vitally) - [Vitally and JumpCloud](https://www.stacksync.com/integrations/jumpcloud-and-vitally) - [Vitally and Okta](https://www.stacksync.com/integrations/okta-and-vitally) - [Vitally and OneLogin](https://www.stacksync.com/integrations/onelogin-and-vitally) ### Storage · 4 - [Vitally and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-vitally) - [Vitally and Box](https://www.stacksync.com/integrations/box-and-vitally) - [Vitally and Egnyte](https://www.stacksync.com/integrations/egnyte-and-vitally) - [Vitally and SharePoint](https://www.stacksync.com/integrations/sharepoint-and-vitally) 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/)