--- title: "NextGen Healthcare connector | Stacksync" description: "NextGen Healthcare integration guide: plan Clinical Documents, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/nextgen-healthcare last_modified: 2026-09-15 --- Business productivity · Two-way sync platform # NextGen Healthcare 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 NextGen Healthcare workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Clinical Documents. 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. - **Patients** - **Appointments** - **Encounters** **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=nextgen-healthcare) ## 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 ## NextGen Healthcare records to discuss. These NextGen Healthcare record examples help scope a technical review. They are not a list of verified Stacksync operations. Patients Identify this record type and the operation you need to review with Stacksync. Appointments Identify this record type and the operation you need to review with Stacksync. Encounters Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Providers Identify this record type and the operation you need to review with Stacksync. Clinical Documents Keep file/object ID, container, and version. A path can change and a filename can repeat. Medications & Allergies Identify this record type and the operation you need to review with Stacksync. Connection setup ## NextGen Healthcare connection requirements. Review NextGen Healthcare 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 NextGen Healthcare account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for NextGen Healthcare, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your NextGen Healthcare 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 NextGen Healthcare **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 Keep file/object ID, container, and version. A path can change and a filename can repeat. Load related records in the right order Resolve folder/container and parent-record references before attaching metadata. ### Mapping checks by record type #### Clinical Documents 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. [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 NextGen Healthcare 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 NextGen Healthcare 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 Clinical Documents Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test a renamed file, a new version, a moved folder, and an access-restricted document. **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 NextGen Healthcare 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 NextGen Healthcare integration. ### Diagnose record matching, delayed changes, and rejected operations A NextGen Healthcare record appears under the wrong destination record Keep file/object ID, container, and version. A path can change and a filename can repeat. Resolve folder/container and parent-record references before attaching metadata. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected NextGen Healthcare implementation’s change-detection method for Clinical Documents. 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 NextGen Healthcare 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 NextGen Healthcare workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=nextgen-healthcare) ## NextGen Healthcare 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 ## NextGen Healthcare connector FAQ ### How should I plan an integration with NextGen Healthcare? 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 NextGen Healthcare connector write changes back? Write-back support is not established for this connection. Review the NextGen Healthcare records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for NextGen Healthcare data? Keep file/object ID, container, and version. A path can change and a filename can repeat. ### Which related records should I load first for NextGen Healthcare? Resolve folder/container and parent-record references before attaching metadata. ### How do I validate NextGen Healthcare changes after the initial load? Test a renamed file, a new version, a moved folder, and an access-restricted document. An update reaches the intended record, preserves its relationships, and performs each approved side effect once. ### What will we cover in a NextGen Healthcare integration demo? Start with one workflow and a sample record from Clinical Documents. 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 NextGen Healthcare 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 NextGen Healthcare and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use NextGen Healthcare. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a NextGen Healthcare record changes.” - “Create a Genie that answers questions about our NextGen Healthcare 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 NextGen Healthcare 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 - [NetSuite and NextGen Healthcare](https://www.stacksync.com/integrations/netsuite-and-nextgen-healthcare) - [NextGen Healthcare and Rockset](https://www.stacksync.com/integrations/nextgen-healthcare-and-rockset) - [Azure SQL Database and NextGen Healthcare](https://www.stacksync.com/integrations/azure-sql-database-and-nextgen-healthcare) - [NextGen Healthcare and SharePoint](https://www.stacksync.com/integrations/nextgen-healthcare-and-sharepoint) - [NextGen Healthcare and Okta](https://www.stacksync.com/integrations/nextgen-healthcare-and-okta) - [Google Cloud Platform and NextGen Healthcare](https://www.stacksync.com/integrations/google-cloud-platform-and-nextgen-healthcare) - [Docusign and NextGen Healthcare](https://www.stacksync.com/integrations/docusign-and-nextgen-healthcare) - [NextGen Healthcare and Smartsheet](https://www.stacksync.com/integrations/nextgen-healthcare-and-smartsheet) ### CRM · 21 - [NextGen Healthcare and 6sense](https://www.stacksync.com/integrations/6sense-and-nextgen-healthcare) - [NextGen Healthcare and Apollo.io](https://www.stacksync.com/integrations/apollo-io-and-nextgen-healthcare) - [NextGen Healthcare and Chorusai](https://www.stacksync.com/integrations/chorusai-and-nextgen-healthcare) - [NextGen Healthcare and Clearbit](https://www.stacksync.com/integrations/clearbit-and-nextgen-healthcare) - [NextGen Healthcare and Close](https://www.stacksync.com/integrations/close-and-nextgen-healthcare) - [NextGen Healthcare and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-nextgen-healthcare) - [NextGen Healthcare and Creatio CRM](https://www.stacksync.com/integrations/creatio-crm-and-nextgen-healthcare) - [NextGen Healthcare and Drift](https://www.stacksync.com/integrations/drift-and-nextgen-healthcare) - [NextGen Healthcare and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-nextgen-healthcare) - [NextGen Healthcare and Gong](https://www.stacksync.com/integrations/gong-and-nextgen-healthcare) - [NextGen Healthcare and HubSpot](https://www.stacksync.com/integrations/hubspot-and-nextgen-healthcare) - [NextGen Healthcare and Infor CRM](https://www.stacksync.com/integrations/infor-crm-and-nextgen-healthcare) - [NextGen Healthcare and Outreach](https://www.stacksync.com/integrations/nextgen-healthcare-and-outreach) - [NextGen Healthcare and Salesforce](https://www.stacksync.com/integrations/nextgen-healthcare-and-salesforce) - [NextGen Healthcare and Salesloft](https://www.stacksync.com/integrations/nextgen-healthcare-and-salesloft) - [NextGen Healthcare and Seismic](https://www.stacksync.com/integrations/nextgen-healthcare-and-seismic) - [NextGen Healthcare and Shopify](https://www.stacksync.com/integrations/nextgen-healthcare-and-shopify) - [NextGen Healthcare and Veeva CRM](https://www.stacksync.com/integrations/nextgen-healthcare-and-veeva-crm) - [NextGen Healthcare and Vtiger CRM](https://www.stacksync.com/integrations/nextgen-healthcare-and-vtiger-crm) - [NextGen Healthcare and Xactly](https://www.stacksync.com/integrations/nextgen-healthcare-and-xactly) - [NextGen Healthcare and ZoomInfo](https://www.stacksync.com/integrations/nextgen-healthcare-and-zoominfo) ### ERP · 4 - [NextGen Healthcare and NetSuite](https://www.stacksync.com/integrations/netsuite-and-nextgen-healthcare) - [NextGen Healthcare and Sage Intacct](https://www.stacksync.com/integrations/nextgen-healthcare-and-sage-intacct) - [NextGen Healthcare and SAP](https://www.stacksync.com/integrations/nextgen-healthcare-and-sap) - [NextGen Healthcare and Unleashed Software](https://www.stacksync.com/integrations/nextgen-healthcare-and-unleashed-software) ### Database · 17 - [NextGen Healthcare and Airtable](https://www.stacksync.com/integrations/airtable-and-nextgen-healthcare) - [NextGen Healthcare and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-nextgen-healthcare) - [NextGen Healthcare and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-nextgen-healthcare) - [NextGen Healthcare and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-nextgen-healthcare) - [NextGen Healthcare and Azure Cosmos DB](https://www.stacksync.com/integrations/azure-cosmos-db-and-nextgen-healthcare) - [NextGen Healthcare and Azure SQL Database](https://www.stacksync.com/integrations/azure-sql-database-and-nextgen-healthcare) - [NextGen Healthcare and Google AlloyDB](https://www.stacksync.com/integrations/google-alloydb-and-nextgen-healthcare) - [NextGen Healthcare and Google Cloud SQL](https://www.stacksync.com/integrations/google-cloud-sql-and-nextgen-healthcare) - [NextGen Healthcare and IBM AS/400](https://www.stacksync.com/integrations/ibm-as400-and-nextgen-healthcare) - [NextGen Healthcare and InfluxDB](https://www.stacksync.com/integrations/influxdb-and-nextgen-healthcare) - [NextGen Healthcare and InterSystems IRIS](https://www.stacksync.com/integrations/intersystems-iris-and-nextgen-healthcare) - [NextGen Healthcare and MongoDB](https://www.stacksync.com/integrations/mongodb-and-nextgen-healthcare) - [NextGen Healthcare and MySQL](https://www.stacksync.com/integrations/mysql-and-nextgen-healthcare) - [NextGen Healthcare and PostgreSQL](https://www.stacksync.com/integrations/nextgen-healthcare-and-postgresql) - [NextGen Healthcare and SAP HANA](https://www.stacksync.com/integrations/nextgen-healthcare-and-sap-hana) - [NextGen Healthcare and SQL Server](https://www.stacksync.com/integrations/nextgen-healthcare-and-sql-server) - [NextGen Healthcare and Supabase](https://www.stacksync.com/integrations/nextgen-healthcare-and-supabase) ### Data warehouse · 13 - [NextGen Healthcare and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-nextgen-healthcare) - [NextGen Healthcare and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-nextgen-healthcare) - [NextGen Healthcare and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-nextgen-healthcare) - [NextGen Healthcare and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-nextgen-healthcare) - [NextGen Healthcare and BigQuery](https://www.stacksync.com/integrations/bigquery-and-nextgen-healthcare) - [NextGen Healthcare and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-nextgen-healthcare) - [NextGen Healthcare and Databricks](https://www.stacksync.com/integrations/databricks-and-nextgen-healthcare) - [NextGen Healthcare and Dremio](https://www.stacksync.com/integrations/dremio-and-nextgen-healthcare) - [NextGen Healthcare and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-nextgen-healthcare) - [NextGen Healthcare and Greenplum](https://www.stacksync.com/integrations/greenplum-and-nextgen-healthcare) - [NextGen Healthcare and Rockset](https://www.stacksync.com/integrations/nextgen-healthcare-and-rockset) - [NextGen Healthcare and Snowflake](https://www.stacksync.com/integrations/nextgen-healthcare-and-snowflake) - [NextGen Healthcare and Starburst Enterprise](https://www.stacksync.com/integrations/nextgen-healthcare-and-starburst-enterprise) ### Business productivity · 18 - [NextGen Healthcare and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-nextgen-healthcare) - [NextGen Healthcare and Asana](https://www.stacksync.com/integrations/asana-and-nextgen-healthcare) - [NextGen Healthcare and Docusign](https://www.stacksync.com/integrations/docusign-and-nextgen-healthcare) - [NextGen Healthcare and eClinicalWorks](https://www.stacksync.com/integrations/eclinicalworks-and-nextgen-healthcare) - [NextGen Healthcare and Gainsight](https://www.stacksync.com/integrations/gainsight-and-nextgen-healthcare) - [NextGen Healthcare and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-nextgen-healthcare) - [NextGen Healthcare and Ironclad](https://www.stacksync.com/integrations/ironclad-and-nextgen-healthcare) - [NextGen Healthcare and Lusha](https://www.stacksync.com/integrations/lusha-and-nextgen-healthcare) - [NextGen Healthcare and Microsoft Dynamics 365](https://www.stacksync.com/integrations/microsoft-dynamics-365-and-nextgen-healthcare) - [NextGen Healthcare and Monday](https://www.stacksync.com/integrations/monday-and-nextgen-healthcare) - [NextGen Healthcare and Notion](https://www.stacksync.com/integrations/nextgen-healthcare-and-notion) - [NextGen Healthcare and Quip](https://www.stacksync.com/integrations/nextgen-healthcare-and-quip) - [NextGen Healthcare and ServiceMax](https://www.stacksync.com/integrations/nextgen-healthcare-and-servicemax) - [NextGen Healthcare and Smartsheet](https://www.stacksync.com/integrations/nextgen-healthcare-and-smartsheet) - [NextGen Healthcare and SysAid](https://www.stacksync.com/integrations/nextgen-healthcare-and-sysaid) - [NextGen Healthcare and Twilio](https://www.stacksync.com/integrations/nextgen-healthcare-and-twilio) - [NextGen Healthcare and Wrike](https://www.stacksync.com/integrations/nextgen-healthcare-and-wrike) - [NextGen Healthcare and Zendesk](https://www.stacksync.com/integrations/nextgen-healthcare-and-zendesk) ### Accounting and finance · 11 - [NextGen Healthcare and Adyen](https://www.stacksync.com/integrations/adyen-and-nextgen-healthcare) - [NextGen Healthcare and BILL](https://www.stacksync.com/integrations/bill-and-nextgen-healthcare) - [NextGen Healthcare and Braintree](https://www.stacksync.com/integrations/braintree-and-nextgen-healthcare) - [NextGen Healthcare and Coupa](https://www.stacksync.com/integrations/coupa-and-nextgen-healthcare) - [NextGen Healthcare and Navan](https://www.stacksync.com/integrations/navan-and-nextgen-healthcare) - [NextGen Healthcare and QuickBooks](https://www.stacksync.com/integrations/nextgen-healthcare-and-quickbooks) - [NextGen Healthcare and Ramp](https://www.stacksync.com/integrations/nextgen-healthcare-and-ramp) - [NextGen Healthcare and Recurly](https://www.stacksync.com/integrations/nextgen-healthcare-and-recurly) - [NextGen Healthcare and Stripe](https://www.stacksync.com/integrations/nextgen-healthcare-and-stripe) - [NextGen Healthcare and Workday](https://www.stacksync.com/integrations/nextgen-healthcare-and-workday) - [NextGen Healthcare and Zuora](https://www.stacksync.com/integrations/nextgen-healthcare-and-zuora) ### AI · 4 - [NextGen Healthcare and Autopilot](https://www.stacksync.com/integrations/autopilot-and-nextgen-healthcare) - [NextGen Healthcare and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-nextgen-healthcare) - [NextGen Healthcare and OpenAI](https://www.stacksync.com/integrations/nextgen-healthcare-and-openai) - [NextGen Healthcare and Pinecone](https://www.stacksync.com/integrations/nextgen-healthcare-and-pinecone) ### Developer tools · 9 - [NextGen Healthcare and Azure Service Bus](https://www.stacksync.com/integrations/azure-service-bus-and-nextgen-healthcare) - [NextGen Healthcare and Datadog](https://www.stacksync.com/integrations/datadog-and-nextgen-healthcare) - [NextGen Healthcare and Jira](https://www.stacksync.com/integrations/jira-and-nextgen-healthcare) - [NextGen Healthcare and JMS](https://www.stacksync.com/integrations/jms-and-nextgen-healthcare) - [NextGen Healthcare and LDAP](https://www.stacksync.com/integrations/ldap-and-nextgen-healthcare) - [NextGen Healthcare and New Relic](https://www.stacksync.com/integrations/newrelic-and-nextgen-healthcare) - [NextGen Healthcare and Opsgenie](https://www.stacksync.com/integrations/nextgen-healthcare-and-opsgenie) - [NextGen Healthcare and PagerDuty](https://www.stacksync.com/integrations/nextgen-healthcare-and-pagerduty) - [NextGen Healthcare and RabbitMQ](https://www.stacksync.com/integrations/nextgen-healthcare-and-rabbitmq) ### Human resources · 11 - [NextGen Healthcare and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-nextgen-healthcare) - [NextGen Healthcare and Greenhouse](https://www.stacksync.com/integrations/greenhouse-and-nextgen-healthcare) - [NextGen Healthcare and Hibob](https://www.stacksync.com/integrations/hibob-and-nextgen-healthcare) - [NextGen Healthcare and Jobvite](https://www.stacksync.com/integrations/jobvite-and-nextgen-healthcare) - [NextGen Healthcare and Lever](https://www.stacksync.com/integrations/lever-and-nextgen-healthcare) - [NextGen Healthcare and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/nextgen-healthcare-and-oracle-fusion-cloud-hcm) - [NextGen Healthcare and Paylocity](https://www.stacksync.com/integrations/nextgen-healthcare-and-paylocity) - [NextGen Healthcare and SmartRecruiters](https://www.stacksync.com/integrations/nextgen-healthcare-and-smartrecruiters) - [NextGen Healthcare and Success Factors](https://www.stacksync.com/integrations/nextgen-healthcare-and-success-factors) - [NextGen Healthcare and UKG Pro](https://www.stacksync.com/integrations/nextgen-healthcare-and-ukg-pro) - [NextGen Healthcare and UKG Ready](https://www.stacksync.com/integrations/nextgen-healthcare-and-ukg-ready) ### Security and identity · 6 - [NextGen Healthcare and Active Directory](https://www.stacksync.com/integrations/active-directory-and-nextgen-healthcare) - [NextGen Healthcare and Auth0](https://www.stacksync.com/integrations/auth0-and-nextgen-healthcare) - [NextGen Healthcare and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-nextgen-healthcare) - [NextGen Healthcare and JumpCloud](https://www.stacksync.com/integrations/jumpcloud-and-nextgen-healthcare) - [NextGen Healthcare and Okta](https://www.stacksync.com/integrations/nextgen-healthcare-and-okta) - [NextGen Healthcare and OneLogin](https://www.stacksync.com/integrations/nextgen-healthcare-and-onelogin) ### Storage · 4 - [NextGen Healthcare and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-nextgen-healthcare) - [NextGen Healthcare and Box](https://www.stacksync.com/integrations/box-and-nextgen-healthcare) - [NextGen Healthcare and Egnyte](https://www.stacksync.com/integrations/egnyte-and-nextgen-healthcare) - [NextGen Healthcare and SharePoint](https://www.stacksync.com/integrations/nextgen-healthcare-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/)