Infor CRM to HubSpot
Infor CRM (formerly SalesLogix) is a horizontal CRM with web and mobile clients, available on-premises or as single-tenant cloud. The v10 release adds AI features.
Infor CRM data can move into HubSpot, landing mainly in Sales Hub. 3 of 7 mapped objects move directly (Accounts, Contacts and Opportunities); 4 items need manual work and 2 do not move. Plan roughly 3-5 weeks for a small move and 10-20 weeks for a large one.
Migration checklist for Infor CRM
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 6 doneDuring
0 of 6 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
Few customizations.
Mid migration
50k-500k
Custom fields and sales processes.
Large migration
>500k
Heavy customization, integrations and activity history.
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 Infor CRM: what you need to get in, what lands in HubSpot, and what will not.
SData REST API (Atom/XML by default, JSON with format=json)
SData endpoint URL (server, port, SSL) plus a CRM user, typically ADMIN or a read-all integration user.
Admin access to the web host or Application Architect is likely needed to confirm SData entity exposure.
Choose your route
How will you move the data?
No native connector was found.
- You need: SData endpoint URL (server, port, SSL) plus a CRM user, typically ADMIN or a read-all integration user.
- Permission: Admin access to the web host or Application Architect is likely needed to confirm SData entity exposure.
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.
- SData REST API queries with where clauses and nested payloads
- Direct SQL access to the SLX database (on-premises)
- Swagger API docs view in the web client (v9.1 docs)
- CSV export from client groups (not sourced here)
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-20 weeks, usually phased.
Talk to a partnerWhere each object lands
In Infor CRM
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Accounts | Companies | yes | Accounts is an SData resource path. |
| Contacts | Contacts | yes | Contacts is a documented SData resource kind. |
| Opportunities | Deals | yes | Opportunities are exposed in SData. Sales process stages must be mapped to HubSpot pipelines. |
| Opportunity Products | Line items | partial | Price level, warehouse and CPQ status fields exist and need mapping. |
| Activities / History (notes, calls, meetings, to-dos) | Notes, Calls, Meetings, Tasks | partial | Not confirmed in sources. Audit activity and association export coverage via SData. |
| Users | Owners | manual | Users are exposed via SData. Match them to HubSpot owners by email. |
| Tickets / Defects | Tickets | partial | Not sourced. Depends on whether Infor CRM Service is used. |
What to expect
These live in Application Architect or the plugin table, not as data. Rebuild them in HubSpot.
No HubSpot import path. Rebuild them manually.
Infor business rules and processes are not portable.
Report definitions don't transfer.
Picklists are exposed through the SData system endpoint.
Sales processes are stored as XML plugins.
Reconcile record counts and sample associations against the source database.
Audit entity SData settings before extraction.
Check your version against Infor's lifecycle policy.
Store the SLX ID in a custom unique-value property.
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.
The SData API is documented by Infor docs and a vendor-partner site (Customer FX). I found no HubSpot doc for Infor CRM, so object mapping and the rest rest on category-level knowledge.
Sources
Related migrations
Frequently asked questions
How do I migrate Infor CRM to HubSpot?
1. Identify the Infor CRM version and hosting (on-premises or cloud). 2. Confirm the SData endpoint at /sdata/slx/dynamic/-/ responds and set up a read-only integration user. 3. Inventory entities and custom fields in Application Architect and their SData exposure. 4. Export Opportunity sales process definitions and stages.
What data can move from Infor CRM to HubSpot?
These objects move directly: Accounts, Contacts and Opportunities. Check the mapping table for partial and manual items.
What does not move from Infor CRM to HubSpot?
Workflows, sales process definitions and business rules and Security profiles and team permissions. Plan to rebuild or retire these.
How long does a Infor CRM to HubSpot migration take?
Small (<50k): 3-5 weeks. Mid (50k-500k): 6-10 weeks. Large (>500k): 10-20 weeks. These are planning estimates, not a quote.
What access do I need to export from Infor CRM?
SData endpoint URL (server, port, SSL) plus a CRM user, typically ADMIN or a read-all integration user. Admin access to the web host or Application Architect is likely needed to confirm SData entity exposure.
What compliance issues apply when moving Infor CRM data?
Check: Free-text notes may contain sensitive data and Check for financial data if the ERP back office is integrated. Agree consent, retention and access rules before exporting.
Moving Infor CRM 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