Eka Care to HubSpot
Indian digital health platform with EMR, patient records, prescriptions, payments and ABDM interoperability, plus a public developer platform.
Eka Care data can move into HubSpot, landing mainly in Sales Hub. 0 of 5 mapped objects move directly; 3 items need manual work and 2 do not move. Plan roughly 2-4 weeks for a small move and 8-14 weeks for a large one.
Migration checklist for Eka Care
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 6 doneDuring
0 of 6 doneAfter
0 of 6 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<5k contacts
Single clinic, CSV-based.
Mid migration
5k-50k contacts
Multiple clinics, API pulls.
Large migration
>50k contacts
Multi-site, consent and compliance work.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Eka Care: what you need to get in, what lands in HubSpot, and what will not.
REST (Eka Developer Platform)
Client credentials or business auth token from Eka; patient-scoped calls also need an X-Pt-Id header.
Choose your route
How will you move the data?
No native connector was found.
- You need: Client credentials or business auth token from Eka; patient-scoped calls also need an X-Pt-Id header.
- Permission: To confirm
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Clinic and doctor entity APIs
- EMR, patient and records APIs
- Privacy 'Request User Data' API, which delivers data via webhook
Limits: To confirm
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 8-14 weeks, usually phased.
Talk to a partnerWhere each object lands
In Eka Care
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Patient demographics/contact | Contacts | partial | Move only permitted enquiry and contact fields. Keep clinical fields out of HubSpot. |
| Clinic / business entity | Companies | partial | Clinic IDs and names are available through the API; map them to Companies or a custom property. |
| Appointments | Meetings | manual | The searches did not confirm an appointment export endpoint. Confirm with Eka before planning. |
| Referral sources / enquiries | Deals | manual | Not documented in the sources reviewed. Likely built from a CSV or an API pull. |
| Medical records, prescriptions, lab reports | Files | no | Keep these in Eka or the EHR, per the scope note. HubSpot is not a clinical store. |
What to expect
The scope retains these in the clinical system, and they are sensitive health data.
These are tied to India's ABDM consent-based exchange.
The public docs reviewed do not describe them.
The source schema is not documented.
Consent states must be recreated by hand.
Allowlist fields, use sensitive properties only if needed, and get legal sign-off.
Request a data extract from Eka or build API pulls.
Scope only permitted patients.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
Eka's developer docs confirm APIs and auth headers, but the searches found no documented bulk export, appointment or enquiry object schema, rate limits, or HubSpot connector. Object mapping and governance rest on category-level analyst knowledge.
Sources
Related migrations
Frequently asked questions
How do I migrate Eka Care to HubSpot?
1. Confirm with Eka which APIs and exports your account can use. 2. Get a business auth token and Client Login credentials. 3. List the permitted non-clinical fields and obtain legal sign-off. 4. Pull clinic_id and doctor IDs from /dr/v1/business/entities.
What does not move from Eka Care to HubSpot?
Clinical records, EHR and treatment workflows and ABDM care contexts and consent artefacts. Plan to rebuild or retire these.
How long does a Eka Care to HubSpot migration take?
Small (<5k contacts): 2-4 weeks. Mid (5k-50k contacts): 4-8 weeks. Large (>50k contacts): 8-14 weeks. These are planning estimates, not a quote.
What access do I need to export from Eka Care?
Client credentials or business auth token from Eka; patient-scoped calls also need an X-Pt-Id header.
What compliance issues apply when moving Eka Care data?
Check: Health data, Possibly minors' data, India DPDP Act applicability and ABDM consent rules. Agree consent, retention and access rules before exporting.
Moving Eka Care into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner