Home
Documentation
  1. HIPAA Compliance

Migrating to the HIPAA Environment

What You'll Learn

This article covers what happens when your Knack app is migrated to the HIPAA environment. It explains what to expect during the migration, what changes afterward, and what you need to do before and after to make sure everything works correctly.

What Is the HIPAA Environment?

When you sign up for a Knack HIPAA plan, your app is migrated to a dedicated infrastructure that meets HIPAA compliance requirements. This environment is separate from Knack's standard shared infrastructure and is hosted in the United States (Oregon, US).

The migration moves your app, records, files, and backups to this dedicated environment. Once migrated, your data stays in the HIPAA environment.

Before Migration

Prepare for the migration by completing these steps:

  • Do not upload any PHI to your app until the migration is complete. Your app is not HIPAA compliant until it's running on the HIPAA environment with a signed BAA in place.
  • Document any custom API integrations. After migration, your API endpoint will change. You'll need to update every integration that calls the Knack API.
  • Document any Flows or third-party connections. These may need to be reconfigured after migration.
  • Notify your team. Let anyone who uses the app or its API know that there will be downtime during the migration.
  • Export a backup of your data. While Knack handles the migration, having your own backup is a good practice.

During Migration

During the migration process:

  • Your app should not be used. Do not create, update, or delete records while the migration is in progress. If records are modified during migration, it could cause the migration to fail or result in data loss.
  • Expect downtime. The app will not be accessible to your users or through the API during the migration window. The Knack team will coordinate timing with you.
⚠️

Do not use the app during migration. This is critical. Any changes made during migration risk data loss or a failed migration. Wait until Knack confirms the migration is complete before resuming use.

After Migration

Once the migration is complete:

Update Your API Endpoint

All API calls must now be sent to:

usgc-api.knack.com

Calls to api.knack.com will no longer work for your app. Update every integration, script, or third-party connection that uses the Knack API.

This includes:

  • Custom JavaScript or server-side code
  • Flows that use custom API calls
  • Third-party tools like Make (formerly Integromat) or Zapier
  • Any embedded scripts that call the API

Verify Your Flows

Check each Flow connected to your app to make sure it's working correctly after migration. Some Flows may need to be reconfigured to use the new endpoint.

Test Your App

Before opening the app back up to users:

  • Log in and verify your data is intact
  • Test key workflows (creating records, editing records, submitting forms)
  • Verify that login and authentication work correctly
  • Check that connected pages and elements display the right data
  • Confirm that any API integrations return expected results

Enable Your Security Settings

Review and configure your HIPAA security settings. Some settings are enabled by default on HIPAA plans, but others are optional and should be turned on:

  • Verify inactivity logout is set appropriately
  • Enable all recommended password settings
  • Confirm failed login lockout is active
  • Enable secure browser (HTTPS) if not already on
  • Consider enabling IP whitelisting if your users access the app from known locations

See HIPAA Security Settings for details on each setting.

Post-Migration Checklist

  • API endpoint updated to usgc-api.knack.com in all integrations
  • Flows verified and working
  • App tested (records, forms, logins, permissions)
  • HIPAA security settings reviewed and configured
  • BAA signed and on file
  • Team notified that the app is live on the HIPAA environment
  • PHI can now be added to the app

Next Steps

Updated about 7 hours ago