webCRM to HubSpot
Danish cloud CRM covering organisations, contact persons, opportunities (pipeline), activities and orders/deliveries.
webCRM data can move into HubSpot, landing mainly in Sales Hub. 2 of 6 mapped objects move directly (Organisations and Contactpersons); 4 items need manual work and 2 do not move. Plan roughly 2-4 weeks for a small move and 8-16 weeks for a large one.
Migration checklist for webCRM
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
CSV overview exports and native import.
Mid migration
10k-100k records
Activities and associations via a tool or API.
Large migration
>100k records
API-based, with orders and heavy customisation.
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 webCRM: what you need to get in, what lands in HubSpot, and what will not.
REST API (webCRM REST API), plus an older SOAP-style web service (WebCrmApi class) with read-by-dates, read-by-id and query methods
Not documented. Creating Overviews in Utilities is the export route, and the role needed for it is not stated.
Choose your route
How will you move the data?
No native connector was found.
- You need: To confirm
- Permission: Not documented. Creating Overviews in Utilities is the export route, and the role needed for it is not stated.
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.
- Create an Overview in Utilities for Organisations, Contactpersons, Orders or Activities, then Actions > Export to a file
- Export from a report including system IDs (vendor help article 'Export All Data')
- API reads by date range or ID
- Third-party task exports such as the Zynk Workflow delivery export (webCRM Delivery XML)
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-16 weeks, usually phased.
Talk to a partnerWhere each object lands
In webCRM
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Organisations | Companies | yes | Export through an Overview; include the system ID for re-linking. |
| Contactpersons | Contacts | yes | Needs a separate Overview of datatype Contactpersons. HubSpot dedupes contacts by email. |
| Opportunities / pipeline | Deals | partial | The vendor's export-all article mentions pipeline data. Associations and stage history need checking. |
| Activities | Notes, Calls, Meetings, Tasks | partial | Activities can be exported as an Overview type. Mapping to HubSpot activity types is manual, and HubSpot does not backfill history. |
| Orders / Deliveries (with lines) | Line items, Custom objects | manual | Orders and delivery lines can be exported. No standard mapping is documented. |
| Users | Owners | manual | The API has ReturnAllUsers. Owners must exist in HubSpot before import. |
What to expect
HubSpot derives stage timestamps from movement inside HubSpot.
Not exportable as data; rebuild them in HubSpot.
Not data objects; scope note requires a rebuild.
Each Overview has a single datatype.
CSV import has limited association support.
HubSpot uses a dedicated opt-out import.
Run a sample export and reconcile counts per object before the full run.
Request API access and docs early.
Store the original dates in custom properties.
Switch the user language to English before export.
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 export path (Overviews export) and the API's existence are backed by vendor help pages. I found no vendor or HubSpot doc on auth, rate limits, certifications or a native HubSpot connector. Object mapping to HubSpot rests on general HubSpot import guidance.
Sources
Related migrations
Frequently asked questions
How do I migrate webCRM to HubSpot?
1. Inventory the entities in use: Organisations, Contactpersons, Opportunities, Activities, Orders. 2. Set the webCRM user language to English to ease field mapping. 3. Request webCRM REST API credentials and docs, or plan Overview exports. 4. List custom data fields and map them to HubSpot custom properties.
What data can move from webCRM to HubSpot?
These objects move directly: Organisations and Contactpersons. Check the mapping table for partial and manual items.
What does not move from webCRM to HubSpot?
Deal stage-change history and time-in-stage and Automations and permissions. Plan to rebuild or retire these.
How long does a webCRM to HubSpot migration take?
Small (<10k records): 2-4 weeks. Mid (10k-100k records): 4-8 weeks. Large (>100k records): 8-16 weeks. These are planning estimates, not a quote.
What access do I need to export from webCRM?
Not documented. Creating Overviews in Utilities is the export route, and the role needed for it is not stated.
What compliance issues apply when moving webCRM data?
Check: Danish and EU GDPR applies to a Danish vendor's customers. Agree consent, retention and access rules before exporting.
Moving webCRM 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