OroCRM to HubSpot
Open-source, Symfony/PHP CRM built on OroPlatform. It covers accounts, contacts, leads, opportunities, cases, campaigns and workflows.
OroCRM data can move into HubSpot, landing mainly in Sales Hub. 0 of 8 mapped objects move directly; 4 items need manual work and 3 do not move. Plan roughly 2-4 weeks for a small move and 10-20 weeks for a large one.
Migration checklist for OroCRM
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
<10k records
Mostly CSV export.
Mid migration
10k-250k records
API extraction, custom fields and activities.
Large migration
>250k records
Multi-org, heavy customization, DB-level extraction.
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 OroCRM: what you need to get in, what lands in HubSpot, and what will not.
REST API conforming to JSON:API, with an auto-generated sandbox and OpenAPI dump
A dedicated API user with an API key or OAuth client, and the base URL of the self-hosted or OroCloud instance.
An admin or role with ACL read access to the exported entities. By default only custom entities, dictionaries and enumerations are exposed, so an admin must enable other entities in API configuration.
Choose your route
How will you move the data?
No native connector was found.
- You need: A dedicated API user with an API key or OAuth client, and the base URL of the self-hosted or OroCloud instance.
- Permission: An admin or role with ACL read access to the exported entities. By default only custom entities, dictionaries and enumerations are exposed, so an admin must enable other entities in API configuration.
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.
- REST JSON:API read of enabled entities
- API sandbox at /admin/api/doc
- CLI oro:api:dump and OpenAPI dump
- Grid/UI CSV export (category-level, not verified here)
- Direct database access on self-hosted installs
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 OroCRM
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts | Contacts | partial | Entity must be enabled for the API or exported via CSV. Match on email. |
| Accounts / Business customers | Companies | partial | Oro splits accounts from business customers, so decide which maps to Companies. |
| Opportunities | Deals | partial | Workflow steps and probability need mapping to deal pipeline stages. |
| Leads | Contacts | partial | Map lead status to Lead status or lifecycle stage. Record choice not verified. |
| Cases | Tickets | partial | Cases exist in OroCRM. Mapping to Tickets is analyst judgement. |
| Activities (calls, emails, tasks, events, notes) | Calls, Emails, Tasks, Meetings, Notes | manual | Coverage of the activity export and its associations must be audited per entity. |
| Users (owners) | Owners (users) | manual | Create HubSpot users first and map owners by email. |
| Sales pipelines / workflows | Deal pipelines | manual | Rebuild stages by hand. |
What to expect
These are platform configuration with no HubSpot import path. Rebuild them as HubSpot workflows.
HubSpot permissions and teams are structured differently.
Rebuild them in HubSpot reporting and lists.
Only custom entities, dictionaries and enumerations are exposed by default.
They do not transfer as data.
The scope note flags this as a discovery focus.
Oro supports custom entities and fields, and the 7.0 package includes serialised fields.
Export the activity-target links and import with association keys.
Configure the API early and run oro:api:dump to list the available resources.
Confirm the version first and consider upgrading or using direct DB export.
Dedupe on email before 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.
The product, its JSON:API and its auth packages are backed by Oro docs, GitHub and Packagist. I did not open Oro's import/export docs, the object-level API coverage or a HubSpot connector page. Object mapping and the export path therefore rest on category-level knowledge.
Sources
Related migrations
Frequently asked questions
How do I migrate OroCRM to HubSpot?
1. Record the Oro version and hosting (self-hosted or OroCloud). 2. Create an API user with an API key or OAuth client. 3. Run oro:api:dump to see which entities are exposed, then enable the missing ones. 4. Inventory custom fields, entities, workflows and ACL roles.
What does not move from OroCRM to HubSpot?
Workflows and business process automation, Roles/ACL and organizations/business units and Saved reports, dashboards and segments. Plan to rebuild or retire these.
How long does a OroCRM to HubSpot migration take?
Small (<10k records): 2-4 weeks. Mid (10k-250k records): 4-10 weeks. Large (>250k records): 10-20 weeks. These are planning estimates, not a quote.
What access do I need to export from OroCRM?
A dedicated API user with an API key or OAuth client, and the base URL of the self-hosted or OroCloud instance. An admin or role with ACL read access to the exported entities. By default only custom entities, dictionaries and enumerations are exposed, so an admin must enable other entities in API configuration.
What compliance issues apply when moving OroCRM data?
Check: Financial services customers may hold regulated data and Review for health or minors data case by case. Agree consent, retention and access rules before exporting.
Moving OroCRM 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