TargetX to HubSpot
Higher-ed recruitment and retention CRM built on the Salesforce platform. It is now part of Liaison.
TargetX data can move into HubSpot, landing mainly in Sales Hub. 1 of 7 mapped objects move directly (Contact (applicants/prospects/students)); 4 items need manual work and 2 do not move. Plan roughly 6-10 weeks for a small move and 18-32 weeks for a large one.
Migration checklist for TargetX
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 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
<50k contacts
Contacts and applications only.
Mid migration
50k-250k contacts
Adds custom objects, workflows and one SIS integration.
Large migration
>250k contacts
Multiple campuses, heavy customisation and several integrations.
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 TargetX: what you need to get in, what lands in HubSpot, and what will not.
Salesforce platform APIs (REST/SOAP/Bulk), because TargetX runs as a managed package on Salesforce
Salesforce org login or connected app with API access. Package object names (hed__/TargetX namespaces) are not confirmed by sources.
Salesforce System Administrator or a profile with API Enabled and View All Data
Choose your route
How will you move the data?
No native connector was found.
- You need: Salesforce org login or connected app with API access. Package object names (hed__/TargetX namespaces) are not confirmed by sources.
- Permission: Salesforce System Administrator or a profile with API Enabled and View All Data
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.
- Salesforce Data Export (weekly/monthly CSV)
- Data Loader / report CSV export
- Salesforce API extraction
- A review reports documented export objects (Contact, Application, Enrollment, Test, Essay, Financial Aid, Recommendation, Relationship), reached via Informatica task flows and Salesforce APIs
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: 18-32 weeks, usually phased.
Talk to a partnerWhere each object lands
In TargetX
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contact (applicants/prospects/students) | Contacts | yes | Contact is a documented export object. Dedupe on email and keep the Salesforce ID as a custom property. |
| Account / Relationship (guardians, schools, households) | Companies | partial | Guardians are better as Contacts with associations. Relationship is a documented export object. Label mapping is manual. |
| Application | Deals | partial | Application is a documented export object. Map the admissions stage to a deal pipeline stage. Use a custom object if there are multiple applications per student. |
| Programmes / Academic programs | Custom objects | manual | No source describes the programme object. Treat it as a custom object or a deal property. |
| Enquiries / inquiries / cases | Tickets | manual | Applies only if the Service Hub is used. It depends on the org configuration. |
| Activities (tasks, emails, events) | Notes | partial | Activity history needs a custom API or CSV import, e.g. as Notes, Tasks or Meetings. |
| Test, Essay, Recommendation, Financial Aid | Custom objects | manual | Documented export objects. Move only what the admissions team needs. Keep financial aid in the SIS. |
What to expect
Per the analyst scope these stay in the SIS/LMS.
Platform-specific configuration with no HubSpot equivalent. Rebuild as HubSpot workflows and forms.
Stage logic lives in the Salesforce/TargetX configuration.
Templates and journeys do not export as HubSpot assets.
Salesforce reports are not portable.
Student information stays in those systems, so connect them to HubSpot.
Run a schema inventory and a field-by-field mapping workbook before the import.
Define a data boundary and import only recruitment-relevant fields.
Align cutover with the renewal date and run in parallel.
Dedupe and set a unique ID property before the import.
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.
Product, ownership and Salesforce base are sourced. Salesforce API and export mechanics, object mapping to HubSpot, rate limits and governance details rest on category-level knowledge. Vendor and HubSpot docs were not retrieved.
Sources
Related migrations
Frequently asked questions
How do I migrate TargetX to HubSpot?
1. Confirm the Salesforce org edition, API access and the TargetX package version. 2. Inventory the TargetX objects (Contact, Application, Enrollment, Test, Essay, Financial Aid, Recommendation, Relationship) and the custom fields on each. 3. Decide which data stays in the SIS/LMS and exclude grades, fee ledgers and financial aid. 4. Create a connected app or an integration user with read-only API access.
What data can move from TargetX to HubSpot?
These objects move directly: Contact (applicants/prospects/students). Check the mapping table for partial and manual items.
What does not move from TargetX to HubSpot?
Grades, fee ledgers and learning delivery data and TargetX package automations, communication workflows, application forms and the Schools App. Plan to rebuild or retire these.
How long does a TargetX to HubSpot migration take?
Small (<50k contacts): 6-10 weeks. Mid (50k-250k contacts): 10-18 weeks. Large (>250k contacts): 18-32 weeks. These are planning estimates, not a quote.
What access do I need to export from TargetX?
Salesforce org login or connected app with API access. Package object names (hed__/TargetX namespaces) are not confirmed by sources. Salesforce System Administrator or a profile with API Enabled and View All Data
What compliance issues apply when moving TargetX data?
Check: Student education records (FERPA in the US), Minors / under-18 applicants, Financial aid data and GDPR for international applicants. Agree consent, retention and access rules before exporting.
Moving TargetX 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