HIPAA Ticket Data Migration: Which Help Desks Sign a BAA
HIPAA ticket data migration: which help desks sign a BAA, on which plans, where PHI hides in tickets and what must survive the move. Read the guide.
Published Updated 11 min read

On this page
- What is the BAA chain in a ticket migration?
- Which help desks sign a BAA?
- Where does PHI hide in help desk tickets?
- How should attachments move under HIPAA?
- What happens to HIPAA audit logs in a migration?
- Encryption and token hygiene in the migration pipeline
- Retention and decommissioning the source
- Rate limits and delta sync for 24/7 healthcare desks
- How MigrateX does this
- HIPAA ticket data migration FAQ
- Changelog
HIPAA ticket data migration means moving help desk records that contain protected health information (PHI) from one platform to another without breaking the chain of business associate agreements (BAAs) or losing the audit trail. The target help desk must sign a BAA on the plan you buy, and so must every vendor in between that touches the data.
This guide is for MSPs, SIs and platform sellers moving a healthcare client's tickets. It compares what five help desks sign today, then covers where PHI hides and what must survive cutover.
Example: an MSP moves a clinic's Zendesk account to Jira Service Management. The script copies attachment URLs into the new tickets instead of the files. Zendesk's "require authentication for download" setting was never turned on, so every lab result on those links still opens for anyone with the URL.
What is the BAA chain in a ticket migration?
The BAA chain is the line of contracts that follows PHI to every vendor that creates, receives, maintains or transmits it. In a migration it runs: covered entity (the clinic or health plan), MSP or SI, migration vendor, then the source and target platforms.
HHS states the rule plainly: "A business associate must establish a BAA with its subcontractor before disclosing PHI to the subcontractor for work to be done for a covered entity" (HHS business associates FAQ, as of 4 Nov 2026). Downstream subcontractors are business associates too, and a business associate is directly liable for certain HIPAA provisions.
Encryption doesn't exempt a vendor. HHS says a cloud provider is a business associate "even if the CSP processes or stores only encrypted ePHI and lacks an encryption key for the data" (HHS cloud computing guidance, as of 4 Nov 2026).
Hiring a migration partner does not hand your obligations to someone else. It makes the chain contractual and auditable: each link has a signed BAA, a scope and a party you can ask for evidence.
Which help desks sign a BAA?
Most major help desks sign a BAA, but only on specific plans and for specific products. This is what each vendor's own pages say.
| Platform | Plan needed | How the BAA is signed | Excluded from PHI use | Migration gotcha |
|---|---|---|---|---|
| Zendesk | Suite Professional, Enterprise or Enterprise Plus, plus Advanced Compliance | DocuSign | Early Access, Built by Zendesk and Marketplace apps, social messaging integrations | Attachments open to anyone with the URL unless "require authentication for download" is on |
| Freshdesk | Enterprise, per Freshworks' HIPAA ticketing page | Not stated; ask Freshworks | Freshworks products outside Freshdesk, Freshchat, Freshcaller and Freshdesk Omnichannel | PHI belongs only in encrypted custom fields; default fields can't be encrypted |
| Freshservice | Enterprise ("Other Freshservice plans are expressly excluded") | Guide says a BAA "may be available"; ask Freshworks | All non-Enterprise plans | Deleting a ticket deletes its activity log; encrypted field values aren't visible through the API |
| Jira Service Management | Standard, Premium or Enterprise (not Free or trial) | Admin form (Standard, Premium); account rep (Enterprise) | Third-party apps without their own BAA | No PHI in metadata or naming fields, including file names |
| HubSpot | Enterprise subscriptions | Accepted during Sensitive Data setup | Chatbots, personalization tokens, playbooks, sandboxes, the files tool | A property's Sensitive Data setting can't be changed after creation |
| ServiceNow | Not stated; the BAA is requested per subscription service | Tell your ServiceNow sales support representative, then request a BAA | None listed; third-party access to data in some products is governed by product-specific terms | ServiceNow must be told before ePHI is stored in the instance, so sign before the test load |
Last verified 4 Nov 2026 from each vendor's pages linked below. Plans and exclusions change; re-check before you sign.
Is Zendesk HIPAA compliant?
Zendesk can be used for PHI when the account has the Advanced Compliance add-on on Zendesk Suite Professional, Enterprise or Enterprise Plus, and you sign its BAA through DocuSign (Zendesk Advanced Compliance, as of 4 Nov 2026). Early Access Programs and Built by Zendesk apps "are not covered by the Healthcare Agreement and should not be used with PHI".
Zendesk's security configuration requirements (change log updated 13 May 2026) matter most for a move:
- Without "require authentication for download", "any unrestricted attachment may be accessed by anyone with access to the correct URL".
- "End-User attachments on messaging channels are currently not scanned for malware in Zendesk."
- The subscriber assumes responsibility for the security implications of third parties with API access to PHI. Your migration tool is one of them.
- AI agent conversations turned into tickets "cannot currently be redacted"; deletion is possible only by deleting the ticket.
Moving off Zendesk? See our guide to exporting tickets from Zendesk and the Zendesk platform page.
Freshdesk and Freshservice
Freshworks says its BAA scope "is limited to Freshdesk, Freshchat Freshcaller, and Freshdesk Omnichannel products", and that the BAA stays valid only while customers follow its secured operating environment specifications (Freshworks HIPAA commitment article, modified 2 Aug 2023, as of 4 Nov 2026). Freshworks' HIPAA ticketing page lists a signed BAA on the Freshdesk Enterprise plan and the rule "Store PHI only in encrypted custom fields. Default fields cannot be encrypted."
Freshservice has its own HIPAA configuration guide (modified 31 Oct 2026). It applies to Freshservice Enterprise only. Three lines change migration planning:
- "It is the Customer's responsibility to download their logs from Freshworks systems to ensure that data is not lost", and Freshworks does not keep them for the full mandatory retention period.
- Deleting a ticket deletes its Ticket Activity Log. Export the log first.
- Encrypted field values "are never stored in plain text" and are "not visible via other services, including third-party services, APIs, and MCPs". Plan how those values leave Freshservice before you need them out.
Is Jira Service Management HIPAA compliant?
Atlassian signs BAAs for Standard, Premium and Enterprise plans of Jira, Jira Service Management, Jira Product Discovery and Confluence; "Free and trial plans are not eligible" (Atlassian HIPAA compliance, as of 4 Nov 2026). Standard and Premium customers sign through a form in Atlassian Administration, and the signatory has 90 days before the link expires (Atlassian BAA article).
Atlassian says you must "read and follow" its HIPAA guide "before inputting any PHI" (Atlassian Trust Center). The HIPAA Implementation Guide adds two rules a migration can break without anyone noticing:
- "Ensure that you don't input PHI into Atlassian Support tickets, surveys, or any metadata or naming fields." File names are one of its examples. Attachments named after patients need renaming before load.
- Third-party apps need their own BAA. A Marketplace app installed for the migration is in scope.
For Zendesk sources, see the Zendesk to Jira Service Management migration page.
Is HubSpot HIPAA compliant?
HubSpot stores sensitive data on Enterprise subscriptions once a Super Admin turns the feature on. To store HIPAA-covered data you must select both the Health/Medical Data and HIPAA-covered entity checkboxes, and accept the BAA as part of setup (HubSpot sensitive data article, updated 21 Sep 2026).
"Once a property is created, its Sensitive Data setting cannot be changed", so field mapping has to be final before import. HubSpot's sensitive data tools article (updated 24 Sep 2026) adds that only files uploaded after Sensitive Data is on get extra encryption, and that an account storing HIPAA data "cannot migrate to another data center". Neither addresses tickets specifically; confirm ticket coverage with HubSpot.
Does ServiceNow sign a BAA?
Yes. ServiceNow lets covered entities and their business associates store ePHI in their instance "provided they enter into a BAA with ServiceNow". Customers must tell ServiceNow through their sales support representative before storing ePHI, then request a BAA for that subscription service (ServiceNow Security and HIPAA white paper, dated 16 Jul 2026, as of 4 Nov 2026).
The same paper says ServiceNow "will not enter into a BAA that requires ServiceNow to carry out the customer's covered entity obligations", and that the customer keeps primary responsibility for its HIPAA compliance, including giving individuals access to their ePHI.
Where does PHI hide in help desk tickets?
PHI sits wherever a patient or agent can type or attach something. Scope these before mapping:
| Location | Why it carries PHI | What to check |
|---|---|---|
| Ticket subject and comments | Patients describe symptoms, medications and appointments in free text | Whether the target field is covered and, where required, encrypted |
| Attachments and inline images | Lab results, referral letters, insurance cards, screenshots of portals | Authenticated download, file names, size limits |
| Side conversations | Agents forward details to clinics or billing | Zendesk makes the subscriber responsible for PHI in them |
| Survey and CSAT comments | Free text with no field controls | Whether the target treats survey text as covered data |
| AI agent and chat transcripts | Full patient conversations | Zendesk: can't be redacted once a ticket |
| Report and CSV exports | Copies outside the help desk | Where they're stored, who has them, when they're deleted |
Migrations multiply the last row. Every export file, staging bucket and mapping sheet with sample values is a new PHI copy that needs an owner and a deletion date.
How should attachments move under HIPAA?
Attachments should move as files: downloaded with authentication, checked and re-uploaded, never as links back to the source.
- Turn on authenticated download at the source, such as Zendesk's "require authentication for download".
- Re-host every file. Links to the old platform break at cancellation and leave PHI on a system you no longer control.
- Scan for malware. Zendesk does not scan end-user attachments on messaging channels, so files coming from that channel have never been checked.
- Rename where the target requires it. Jira Service Management bars PHI in file names.
- Checksum before and after. Matching hashes show the file arrived unaltered.
# Hash each downloaded attachment, then compare with a hash of the file fetched back from the target
sha256sum staging/attachments/* > source-hashes.txt
sha256sum target-check/attachments/* > target-hashes.txt
diff <(cut -d' ' -f1 source-hashes.txt | sort) <(cut -d' ' -f1 target-hashes.txt | sort)
What happens to HIPAA audit logs in a migration?
Audit logs usually do not transfer. The target logs each import as a new event by the migration user; the source's record of who viewed and changed each ticket stays behind.
HIPAA's audit controls standard requires "mechanisms to record and examine activity in information systems that contain or use ePHI", and the integrity standard requires electronic measures "to confirm that ePHI has not been improperly altered or destroyed" (HHS Security Rule summary, as of 4 Nov 2026). For a migration that means three things:
- Export source audit logs before cutover and keep them as records. Freshservice tells customers to download their own logs, and Zendesk does not return archived tickets from its Listing Ticket Audits endpoint (Zendesk archiving article, as of 4 Nov 2026), so pull audits per ticket.
- Store the source ticket ID on every target record so an auditor can trace one to the other.
- Validate at record level, not by count. A per-record report of source ID, target ID and status is the integrity evidence; see our guide to data migration validation.
Encryption and token hygiene in the migration pipeline
The Security Rule requires technical measures "to guard against unauthorized access to ePHI that is being transmitted over an electronic network" (HHS Security Rule summary). A migration adds hops (source API, staging, transformation, target API), and each needs encryption in transit and at rest.
Credentials are the other half:
- One token per service, so you can revoke the migration's access alone.
- Prefer OAuth. Zendesk now labels API tokens deprecated and tells existing customers they "will have to migrate to OAuth access tokens", warning that API tokens "can be used to impersonate anyone in the account, including admins" (Zendesk security and auth docs, as of 4 Nov 2026).
- Rotate or delete at cutover. Zendesk notes that "Deleting a token deactivates it permanently". Delete the migration's tokens on both platforms once reconciliation is signed off.
GET /api/v2/tickets/{ticket_id}/audits.json HTTP/1.1
Host: {subdomain}.zendesk.com
Authorization: Bearer {oauth_access_token}
Retention and decommissioning the source
HIPAA requires Security Rule documentation to be kept "until six years after the later of" its creation date or the date it was last in effect (HHS Security Rule summary). Retention for patient records is set by other rules, including state law.
Before you cancel the source:
- Export audit and activity logs, and configuration that served as a policy.
- Confirm reconciliation is signed.
- Delete staging copies, export files and mapping spreadsheets that held sample data.
- Ask the source vendor when data is deleted after cancellation. A BAA must require return or destruction of PHI at termination where feasible (HHS cloud computing guidance).
- Get written confirmation of deletion from every party in the chain, the migration vendor included.
Rate limits and delta sync for 24/7 healthcare desks
Healthcare desks rarely accept a long freeze. Load history first, delta-sync tickets changed since the last run, then freeze briefly for the final pass. Rate limits on both sides set the bulk load time, and the delta needs the same attachment, audit and encryption controls.
How MigrateX does this
MigrateX is SOC 2 Type II, GDPR compliant and HIPAA compliant, with a DPA and BAA available. Each migration runs isolated in the region you choose, with TLS 1.2+ in transit and AES-256 at rest. Credentials are deleted at completion, cached data is purged on request or after 7 days, and every record gets an exportable source ID to destination ID to status trail. Details are on our security page.
For a US specialty healthcare provider, we moved 28,000+ tickets from kickoff to handover in 5 weeks.
Start with a free 100-record sample under a signed BAA, and get a fixed quote within 24 hours: talk to us.
Facts checked November 4, 2026 from HHS business associates FAQ, HHS Security Rule summary, Zendesk Advanced Compliance, Freshservice HIPAA configuration guide, Atlassian HIPAA compliance, HubSpot sensitive data and ServiceNow Security and HIPAA white paper. No vendor paid for this article. How we research
HIPAA ticket data migration FAQ
Does a migration vendor need to sign a BAA?
Yes, if it creates, receives, maintains or transmits PHI. HHS says this applies even to a provider holding only encrypted data without the key. Buyers' procurement teams ask about it early, as our guide to procurement security questions explains.
Is Zendesk HIPAA compliant out of the box?
No. Zendesk supports PHI only with the Advanced Compliance add-on on Suite Professional, Enterprise or Enterprise Plus, a signed BAA, and the recommended security configuration, such as authenticated attachment downloads.
Is there a HIPAA certification for help desk software?
No. Vendors say they are HIPAA compliant or sign a BAA; compliance depends on how you configure and use the product.
Do audit logs move with the tickets?
Usually not. Export source audit and activity logs before cutover, and keep the source ticket ID on each target record.
Can we test the migration on real patient tickets?
Yes, once the BAA chain is signed. The sample is a disclosure and needs the same controls as the full run.
Changelog
- 10 Apr 2026: First published as "How to Handle Healthcare Migrations Without the Liability Trap".
- 4 Nov 2026: Rewritten and moved from /blog/healthcare-migrations-liability-trap. Added the BAA chain, a vendor BAA comparison verified 4 Nov 2026, PHI locations, attachments, audit logs, token hygiene and decommissioning; removed outdated compliance status and unsourced claims.
This article is general information, not legal advice. HIPAA obligations depend on your role and contracts; talk to your counsel and privacy officer before moving PHI.
Written by
Ayush BothraFounding Member, MigrateX
Ayush writes about ITSM platforms, pricing and what it takes to move a service desk to a new platform without losing its history.


