--- title: "Agiloft connector: setup and compatibility | Stacksync" description: "Agiloft integration guide: plan Companies and People, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/agiloft last_modified: 2026-09-15 --- Business productivity · Two-way sync platform # Agiloft integration. Connect your Agiloft 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 Attachments. - 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. - **Contracts** - **Companies** - **People** **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=agiloft) ## 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 ## Agiloft records to discuss. These Agiloft record examples help scope a technical review. They are not a list of verified Stacksync operations. Contracts Identify this record type and the operation you need to review with Stacksync. 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. ### See 3 more record examples Attachments Keep file/object ID, container, and version. A path can change and a filename can repeat. Approvals Identify this record type and the operation you need to review with Stacksync. Tasks Use a stable task/work-item ID and preserve its project or parent-ticket reference. Connection setup ## Agiloft connection requirements. Review Agiloft 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 Agiloft account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Agiloft, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Agiloft integration. Choose the object and business event that matter to the workflow. Separate record updates from side effects such as notifications, approvals, and file creation. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Agiloft **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. #### Attachments Confirm object support with Stacksync Identity Keep file/object ID, container, and version. A path can change and a filename can repeat. Fields to consider Source file ID · Container reference · Version · Metadata · Access classification Related records to resolve first Resolve folder/container and parent-record references before attaching metadata. Test before going live Test a renamed file, a new version, a moved folder, and an access-restricted document. #### Tasks 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. [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 Agiloft integration in four steps. An update reaches the intended record, preserves its relationships, and performs each approved side effect once. ### View the four setup tests and expected results 1. ### Confirm the intended Agiloft 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:** An update reaches the intended record, preserves its relationships, and performs each approved side effect once. 3. ### Test the operation your workflow needs Review one Agiloft 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 Agiloft integration. ### Diagnose record matching, delayed changes, and rejected operations A Agiloft 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 Agiloft implementation’s change-detection method for Companies, People and Attachments. 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 Agiloft 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 Agiloft workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=agiloft) ## Agiloft 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 ## Agiloft connector FAQ ### How should I plan an integration with Agiloft? Choose the object and business event that matter to the workflow. Separate record updates from side effects such as notifications, approvals, and file creation. 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 Agiloft connector write changes back? Write-back support is not established for this connection. Review the Agiloft records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Agiloft 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 Agiloft? Resolve parent organizations, business units, and currency references before dependent transactions. ### How do I validate Agiloft 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. An update reaches the intended record, preserves its relationships, and performs each approved side effect once. ### What should I include when estimating Agiloft integration costs? Estimate the number of Companies, People and Attachments records, the history to load, ongoing changes, and required environments. Include API access, the integration service, destination storage or processing, and the work to maintain mappings and recover from errors. Review current provider pricing against that workload, including any account or API upgrades. ## Explore Agiloft 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 - [Agiloft and Docusign](https://www.stacksync.com/integrations/agiloft-and-docusign) - [Agiloft and Sage 300](https://www.stacksync.com/integrations/agiloft-and-sage-300) - [Agiloft and Salesforce](https://www.stacksync.com/integrations/agiloft-and-salesforce) - [Agiloft and Epicor ERP](https://www.stacksync.com/integrations/agiloft-and-epicor-erp) - [Agiloft and Infor CRM](https://www.stacksync.com/integrations/agiloft-and-infor-crm) - [Agiloft and QAD ERP](https://www.stacksync.com/integrations/agiloft-and-qad-erp) - [Agiloft and Okta](https://www.stacksync.com/integrations/agiloft-and-okta) - [Agiloft and SharePoint](https://www.stacksync.com/integrations/agiloft-and-sharepoint) ### CRM · 31 - [Agiloft and 6sense](https://www.stacksync.com/integrations/6sense-and-agiloft) - [Agiloft and Affinity](https://www.stacksync.com/integrations/affinity-and-agiloft) - [Agiloft and Attio](https://www.stacksync.com/integrations/agiloft-and-attio) - [Agiloft and Chorusai](https://www.stacksync.com/integrations/agiloft-and-chorusai) - [Agiloft and Clearbit](https://www.stacksync.com/integrations/agiloft-and-clearbit) - [Agiloft and Close](https://www.stacksync.com/integrations/agiloft-and-close) - [Agiloft and Copper CRM](https://www.stacksync.com/integrations/agiloft-and-copper-crm) - [Agiloft and Dun & Bradstreet](https://www.stacksync.com/integrations/agiloft-and-dun-bradstreet) - [Agiloft and Freshsales](https://www.stacksync.com/integrations/agiloft-and-freshsales) - [Agiloft and Freshworks CRM](https://www.stacksync.com/integrations/agiloft-and-freshworks-crm) - [Agiloft and Gong](https://www.stacksync.com/integrations/agiloft-and-gong) - [Agiloft and Gorgias](https://www.stacksync.com/integrations/agiloft-and-gorgias) - [Agiloft and HubSpot](https://www.stacksync.com/integrations/agiloft-and-hubspot) - [Agiloft and Infor CRM](https://www.stacksync.com/integrations/agiloft-and-infor-crm) - [Agiloft and Insightly](https://www.stacksync.com/integrations/agiloft-and-insightly) - [Agiloft and Intercom](https://www.stacksync.com/integrations/agiloft-and-intercom) - [Agiloft and Kommo](https://www.stacksync.com/integrations/agiloft-and-kommo) - [Agiloft and Outreach](https://www.stacksync.com/integrations/agiloft-and-outreach) - [Agiloft and Pipedrive](https://www.stacksync.com/integrations/agiloft-and-pipedrive) - [Agiloft and Salesforce](https://www.stacksync.com/integrations/agiloft-and-salesforce) - [Agiloft and Salesloft](https://www.stacksync.com/integrations/agiloft-and-salesloft) - [Agiloft and SAP Sales Cloud](https://www.stacksync.com/integrations/agiloft-and-sap-sales-cloud) - [Agiloft and Seismic](https://www.stacksync.com/integrations/agiloft-and-seismic) - [Agiloft and Shopify](https://www.stacksync.com/integrations/agiloft-and-shopify) - [Agiloft and SugarCRM](https://www.stacksync.com/integrations/agiloft-and-sugarcrm) - [Agiloft and Veeva CRM](https://www.stacksync.com/integrations/agiloft-and-veeva-crm) - [Agiloft and Vtiger CRM](https://www.stacksync.com/integrations/agiloft-and-vtiger-crm) - [Agiloft and Xactly](https://www.stacksync.com/integrations/agiloft-and-xactly) - [Agiloft and Zoho CRM](https://www.stacksync.com/integrations/agiloft-and-zoho-crm) - [Agiloft and Zoho SalesIQ](https://www.stacksync.com/integrations/agiloft-and-zoho-salesiq) - [Agiloft and ZoomInfo](https://www.stacksync.com/integrations/agiloft-and-zoominfo) ### ERP · 24 - [Agiloft and Acumatica](https://www.stacksync.com/integrations/acumatica-and-agiloft) - [Agiloft and Brightpearl](https://www.stacksync.com/integrations/agiloft-and-brightpearl) - [Agiloft and Cin7](https://www.stacksync.com/integrations/agiloft-and-cin7) - [Agiloft and Dynamics 365 Business Central](https://www.stacksync.com/integrations/agiloft-and-microsoft-dynamics-365-business-central) - [Agiloft and Epicor ERP](https://www.stacksync.com/integrations/agiloft-and-epicor-erp) - [Agiloft and Infor LN](https://www.stacksync.com/integrations/agiloft-and-infor-ln) - [Agiloft and Infor M3](https://www.stacksync.com/integrations/agiloft-and-infor-m3) - [Agiloft and Linnworks](https://www.stacksync.com/integrations/agiloft-and-linnworks) - [Agiloft and Microsoft Dynamics GP](https://www.stacksync.com/integrations/agiloft-and-microsoft-dynamics-gp) - [Agiloft and Microsoft Dynamics NAV](https://www.stacksync.com/integrations/agiloft-and-microsoft-dynamics-nav) - [Agiloft and NetSuite](https://www.stacksync.com/integrations/agiloft-and-netsuite) - [Agiloft and Odoo](https://www.stacksync.com/integrations/agiloft-and-odoo) - [Agiloft and Plex ERP](https://www.stacksync.com/integrations/agiloft-and-plex-erp) - [Agiloft and QAD ERP](https://www.stacksync.com/integrations/agiloft-and-qad-erp) - [Agiloft and Sage 100](https://www.stacksync.com/integrations/agiloft-and-sage-100) - [Agiloft and Sage 300](https://www.stacksync.com/integrations/agiloft-and-sage-300) - [Agiloft and Sage Intacct](https://www.stacksync.com/integrations/agiloft-and-sage-intacct) - [Agiloft and Sage X3](https://www.stacksync.com/integrations/agiloft-and-sage-x3) - [Agiloft and SAP](https://www.stacksync.com/integrations/agiloft-and-sap) - [Agiloft and SAP Business ByDesign](https://www.stacksync.com/integrations/agiloft-and-sap-business-bydesign) - [Agiloft and SAP Business One](https://www.stacksync.com/integrations/agiloft-and-sap-business-one) - [Agiloft and SAP S/4HANA](https://www.stacksync.com/integrations/agiloft-and-sap-s4hana) - [Agiloft and Syspro](https://www.stacksync.com/integrations/agiloft-and-syspro) - [Agiloft and TikTok Shop](https://www.stacksync.com/integrations/agiloft-and-tiktok) ### Database · 12 - [Agiloft and Airtable](https://www.stacksync.com/integrations/agiloft-and-airtable) - [Agiloft and Amazon DynamoDB](https://www.stacksync.com/integrations/agiloft-and-amazon-dynamodb) - [Agiloft and Elasticsearch](https://www.stacksync.com/integrations/agiloft-and-elasticsearch) - [Agiloft and Firebase](https://www.stacksync.com/integrations/agiloft-and-firebase) - [Agiloft and InfluxDB](https://www.stacksync.com/integrations/agiloft-and-influxdb) - [Agiloft and MongoDB](https://www.stacksync.com/integrations/agiloft-and-mongodb) - [Agiloft and MySQL](https://www.stacksync.com/integrations/agiloft-and-mysql) - [Agiloft and Neo4j](https://www.stacksync.com/integrations/agiloft-and-neo4j) - [Agiloft and PostgreSQL](https://www.stacksync.com/integrations/agiloft-and-postgresql) - [Agiloft and SAP HANA](https://www.stacksync.com/integrations/agiloft-and-sap-hana) - [Agiloft and SQL Server](https://www.stacksync.com/integrations/agiloft-and-sql-server) - [Agiloft and Supabase](https://www.stacksync.com/integrations/agiloft-and-supabase) ### Data warehouse · 8 - [Agiloft and Amazon Redshift](https://www.stacksync.com/integrations/agiloft-and-amazon-redshift) - [Agiloft and Amazon S3](https://www.stacksync.com/integrations/agiloft-and-aws-s3) - [Agiloft and Azure Synapse Analytics](https://www.stacksync.com/integrations/agiloft-and-azure-synapse-analytics) - [Agiloft and BigQuery](https://www.stacksync.com/integrations/agiloft-and-bigquery) - [Agiloft and ClickHouse](https://www.stacksync.com/integrations/agiloft-and-clickhouse) - [Agiloft and Databricks](https://www.stacksync.com/integrations/agiloft-and-databricks) - [Agiloft and Google Cloud Platform](https://www.stacksync.com/integrations/agiloft-and-google-cloud-platform) - [Agiloft and Snowflake](https://www.stacksync.com/integrations/agiloft-and-snowflake) ### Business productivity · 31 - [Agiloft and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-agiloft) - [Agiloft and Amazon Seller Central](https://www.stacksync.com/integrations/agiloft-and-amazon-seller-central) - [Agiloft and Asana](https://www.stacksync.com/integrations/agiloft-and-asana) - [Agiloft and Atlassian](https://www.stacksync.com/integrations/agiloft-and-atlassian) - [Agiloft and Braze](https://www.stacksync.com/integrations/agiloft-and-braze) - [Agiloft and Campfire](https://www.stacksync.com/integrations/agiloft-and-campfire) - [Agiloft and ConnectWise](https://www.stacksync.com/integrations/agiloft-and-connectwise) - [Agiloft and Docusign](https://www.stacksync.com/integrations/agiloft-and-docusign) - [Agiloft and eClinicalWorks](https://www.stacksync.com/integrations/agiloft-and-eclinicalworks) - [Agiloft and Front](https://www.stacksync.com/integrations/agiloft-and-front) - [Agiloft and Gainsight](https://www.stacksync.com/integrations/agiloft-and-gainsight) - [Agiloft and GitHub](https://www.stacksync.com/integrations/agiloft-and-github) - [Agiloft and Google Sheets](https://www.stacksync.com/integrations/agiloft-and-google-sheets) - [Agiloft and Ironclad](https://www.stacksync.com/integrations/agiloft-and-ironclad) - [Agiloft and Klaviyo](https://www.stacksync.com/integrations/agiloft-and-klaviyo) - [Agiloft and Lusha](https://www.stacksync.com/integrations/agiloft-and-lusha) - [Agiloft and Microsoft 365](https://www.stacksync.com/integrations/agiloft-and-microsoft-365) - [Agiloft and Microsoft Dynamics 365](https://www.stacksync.com/integrations/agiloft-and-microsoft-dynamics-365) - [Agiloft and Microsoft Teams](https://www.stacksync.com/integrations/agiloft-and-microsoft-teams) - [Agiloft and Monday](https://www.stacksync.com/integrations/agiloft-and-monday) - [Agiloft and Notion](https://www.stacksync.com/integrations/agiloft-and-notion) - [Agiloft and Quip](https://www.stacksync.com/integrations/agiloft-and-quip) - [Agiloft and SendGrid](https://www.stacksync.com/integrations/agiloft-and-sendgrid) - [Agiloft and ServiceMax](https://www.stacksync.com/integrations/agiloft-and-servicemax) - [Agiloft and ServiceNow](https://www.stacksync.com/integrations/agiloft-and-servicenow) - [Agiloft and Slack](https://www.stacksync.com/integrations/agiloft-and-slack) - [Agiloft and Smartsheet](https://www.stacksync.com/integrations/agiloft-and-smartsheet) - [Agiloft and SysAid](https://www.stacksync.com/integrations/agiloft-and-sysaid) - [Agiloft and Twilio](https://www.stacksync.com/integrations/agiloft-and-twilio) - [Agiloft and Wrike](https://www.stacksync.com/integrations/agiloft-and-wrike) - [Agiloft and Zendesk](https://www.stacksync.com/integrations/agiloft-and-zendesk) ### Accounting and finance · 13 - [Agiloft and Adyen](https://www.stacksync.com/integrations/adyen-and-agiloft) - [Agiloft and Anaplan](https://www.stacksync.com/integrations/agiloft-and-anaplan) - [Agiloft and BILL](https://www.stacksync.com/integrations/agiloft-and-bill) - [Agiloft and Braintree](https://www.stacksync.com/integrations/agiloft-and-braintree) - [Agiloft and Chargebee](https://www.stacksync.com/integrations/agiloft-and-chargebee) - [Agiloft and Coupa](https://www.stacksync.com/integrations/agiloft-and-coupa) - [Agiloft and Navan](https://www.stacksync.com/integrations/agiloft-and-navan) - [Agiloft and QuickBooks](https://www.stacksync.com/integrations/agiloft-and-quickbooks) - [Agiloft and Ramp](https://www.stacksync.com/integrations/agiloft-and-ramp) - [Agiloft and Recurly](https://www.stacksync.com/integrations/agiloft-and-recurly) - [Agiloft and Stripe](https://www.stacksync.com/integrations/agiloft-and-stripe) - [Agiloft and Workday](https://www.stacksync.com/integrations/agiloft-and-workday) - [Agiloft and Zuora](https://www.stacksync.com/integrations/agiloft-and-zuora) ### AI · 4 - [Agiloft and Autopilot](https://www.stacksync.com/integrations/agiloft-and-autopilot) - [Agiloft and Azure OpenAI](https://www.stacksync.com/integrations/agiloft-and-azure-openai) - [Agiloft and OpenAI](https://www.stacksync.com/integrations/agiloft-and-openai) - [Agiloft and Pinecone](https://www.stacksync.com/integrations/agiloft-and-pinecone) ### Communications · 1 - [Agiloft and Gmail](https://www.stacksync.com/integrations/agiloft-and-gmail) ### Developer tools · 9 - [Agiloft and Azure Service Bus](https://www.stacksync.com/integrations/agiloft-and-azure-service-bus) - [Agiloft and Datadog](https://www.stacksync.com/integrations/agiloft-and-datadog) - [Agiloft and Jira](https://www.stacksync.com/integrations/agiloft-and-jira) - [Agiloft and JMS](https://www.stacksync.com/integrations/agiloft-and-jms) - [Agiloft and LDAP](https://www.stacksync.com/integrations/agiloft-and-ldap) - [Agiloft and New Relic](https://www.stacksync.com/integrations/agiloft-and-newrelic) - [Agiloft and Opsgenie](https://www.stacksync.com/integrations/agiloft-and-opsgenie) - [Agiloft and PagerDuty](https://www.stacksync.com/integrations/agiloft-and-pagerduty) - [Agiloft and RabbitMQ](https://www.stacksync.com/integrations/agiloft-and-rabbitmq) ### Human resources · 12 - [Agiloft and BambooHR](https://www.stacksync.com/integrations/agiloft-and-bamboohr) - [Agiloft and Ceridian Dayforce](https://www.stacksync.com/integrations/agiloft-and-ceridian-dayforce) - [Agiloft and Greenhouse](https://www.stacksync.com/integrations/agiloft-and-greenhouse) - [Agiloft and Hibob](https://www.stacksync.com/integrations/agiloft-and-hibob) - [Agiloft and Jobvite](https://www.stacksync.com/integrations/agiloft-and-jobvite) - [Agiloft and Lever](https://www.stacksync.com/integrations/agiloft-and-lever) - [Agiloft and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/agiloft-and-oracle-fusion-cloud-hcm) - [Agiloft and Paylocity](https://www.stacksync.com/integrations/agiloft-and-paylocity) - [Agiloft and SmartRecruiters](https://www.stacksync.com/integrations/agiloft-and-smartrecruiters) - [Agiloft and Success Factors](https://www.stacksync.com/integrations/agiloft-and-success-factors) - [Agiloft and UKG Pro](https://www.stacksync.com/integrations/agiloft-and-ukg-pro) - [Agiloft and UKG Ready](https://www.stacksync.com/integrations/agiloft-and-ukg-ready) ### Security and identity · 6 - [Agiloft and Active Directory](https://www.stacksync.com/integrations/active-directory-and-agiloft) - [Agiloft and Auth0](https://www.stacksync.com/integrations/agiloft-and-auth0) - [Agiloft and Azure Active Directory](https://www.stacksync.com/integrations/agiloft-and-azure-active-directory) - [Agiloft and JumpCloud](https://www.stacksync.com/integrations/agiloft-and-jumpcloud) - [Agiloft and Okta](https://www.stacksync.com/integrations/agiloft-and-okta) - [Agiloft and OneLogin](https://www.stacksync.com/integrations/agiloft-and-onelogin) ### Storage · 4 - [Agiloft and Amazon S3](https://www.stacksync.com/integrations/agiloft-and-amazon-s3) - [Agiloft and Box](https://www.stacksync.com/integrations/agiloft-and-box) - [Agiloft and Egnyte](https://www.stacksync.com/integrations/agiloft-and-egnyte) - [Agiloft and SharePoint](https://www.stacksync.com/integrations/agiloft-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/)