Liaison EMP to HubSpot
Enrollment Marketing Platform (EMP) is Liaison's student-search and enrollment-marketing system. It runs omnichannel campaigns, inquiry forms, PURLs and student records.
Liaison EMP data can move into HubSpot, landing mainly in Sales Hub. 1 of 6 mapped objects move directly (Students / prospects / inquiries); 3 items need manual work and 2 do not move. Plan roughly 3-5 weeks for a small move and 10-18 weeks for a large one.
Migration checklist for Liaison EMP
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
<25k
CSV import with simple stages.
Mid migration
25k-250k
Custom objects and a SIS sync.
Large migration
>250k
Multiple feeds and delta migration.
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 Liaison EMP: what you need to get in, what lands in HubSpot, and what will not.
EMP API (details not confirmed)
Users need permission to manage exports; this is implied by the view-versus-manage split in the docs.
Choose your route
How will you move the data?
No native connector was found.
- You need: To confirm
- Permission: Users need permission to manage exports; this is implied by the view-versus-manage split in the docs.
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.
- Export Manager: filtered student exports in a chosen file format and encoding, with optional additional data and a second file of unique IDs such as college ID or CAS ID
- Recurring exports with transport options (automatic transfer, e.g. SFTP)
- Export mappings that translate EMP field values to your own terminology
- Event registration and group exports
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: 10-18 weeks, usually phased.
Talk to a partnerWhere each object lands
In Liaison EMP
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Students / prospects / inquiries | Contacts | yes | Export CSV by filter, then import with a custom Student ID property. |
| Guardians / parents | Contacts | partial | Whether EMP stores guardians as separate records is unconfirmed; this likely needs association handling. |
| Programs / majors of interest | Custom objects | partial | The usual approach is a custom object or a property on Contacts. |
| Admissions stage / application status | Deals | partial | Application status fields exist on the exported student record; map them to a Deal pipeline. |
| Event registrations / groups | Contacts | partial | Exports are available; in HubSpot they become properties or lists. |
| Campaign and email activity | Notes | manual | Analytics are reportable inside EMP; moving history is not documented. |
What to expect
These are EMP content assets and have no HubSpot equivalent; rebuild them.
These are Liaison service functions and not exportable as CRM records.
The forms are EMP-hosted.
Mapped values avoid mismatches with HubSpot dropdown options.
EMP currently sends nightly inquiry files to TargetX via Informatica.
Inventory the transports and rewire them to HubSpot or to the SIS.
Set the Multiple Values option deliberately and map the fields to HubSpot multi-checkbox properties.
Check the data licence terms with Liaison before importing prospects into HubSpot.
Apply a minimum-age and consent review.
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.
Export Manager and transports are documented by the vendor. The EMP API's auth, limits and object coverage were not confirmed. Object mapping to HubSpot rests on category-level knowledge, and no HubSpot-native connector was found.
Sources
Related migrations
Frequently asked questions
How do I migrate Liaison EMP to HubSpot?
1. Inventory the EMP exports, transports and recurring schedules. 2. Confirm with your Marketing Technologist whether the EMP API is enabled for your account. 3. Define the HubSpot Contact properties for the EMP unique ID, college ID and CAS ID. 4. Create export mappings in EMP Settings so term values match the HubSpot dropdowns.
What data can move from Liaison EMP to HubSpot?
These objects move directly: Students / prospects / inquiries. Check the mapping table for partial and manual items.
What does not move from Liaison EMP to HubSpot?
Campaign templates, viewbooks, PURLs and checklists and Print/digital campaign and Search purchase history. Plan to rebuild or retire these.
How long does a Liaison EMP to HubSpot migration take?
Small (<25k): 3-5 weeks. Mid (25k-250k): 6-10 weeks. Large (>250k): 10-18 weeks. These are planning estimates, not a quote.
What access do I need to export from Liaison EMP?
Users need permission to manage exports; this is implied by the view-versus-manage split in the docs.
Is there a native HubSpot connector for Liaison EMP?
No native connector was found. Plan a CSV, API or third-party tool route.
What compliance issues apply when moving Liaison EMP data?
Check: Minors (prospective students under 18) and Education records (FERPA, where applicable). Agree consent, retention and access rules before exporting.
Moving Liaison EMP 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