Divalto weavy to HubSpot
French SaaS CRM for sales, field technicians and service. It has a mobile app and a customer-portal module, and it integrates with the Divalto ERP and other ERPs.
Divalto weavy data can move into HubSpot, landing mainly in Sales Hub. 2 of 7 mapped objects move directly (Tiers (thirdparty: customers and prospects) and Contacts); 4 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 Divalto weavy
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 6 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
<20k records
CSV-based, contacts, companies and deals only.
Mid migration
20k-200k records
Includes activities and some rebuild work.
Large migration
>200k records
ERP integration, service objects and custom objects.
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 Divalto weavy: what you need to get in, what lands in HubSpot, and what will not.
REST OData (read-only raw access to CRM/ERP database tables and views) plus WebServices/webhooks
Admin portal import/export page; table export must be enabled per profile in the profile manager.
Choose your route
How will you move the data?
No native connector was found.
- You need: To confirm
- Permission: Admin portal import/export page; table export must be enabled per profile in the profile manager.
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.
- Admin CSV export by table (Import/Export page)
- Per-profile Excel export of lists/tables, if enabled
- Read-only OData REST API over HTTPS, using physical table and field names
- Event-based system-table export (e.g. LinkToWeavy export of webhook and page URLs)
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 Divalto weavy
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Tiers (thirdparty: customers and prospects) | Companies | yes | Exportable via CSV or OData. Tiers are the core account entity. |
| Contacts | Contacts | yes | Exportable via CSV or OData. Association to the tier needs a key in the export. |
| Opportunities / sales pipeline | Deals | partial | Vendor docs confirm pipeline sharing but not the table names. Confirm the schema before mapping. |
| Activities (calls, meetings, tasks, emails) | Notes, Calls, Emails, Meetings, Tasks | partial | Export coverage is unverified, and TEXT/BLOB fields are not exposed by OData. Audit this first. |
| Users / sales structure | Owners | manual | Users are linked to the commercial structure and accounts. Recreate users and owners in HubSpot and map by email. |
| Interventions, equipment, contracts, sites | Custom objects, Tickets | manual | Service/technician entities exist (intervention, equipment, contract, site). Mapping is an analyst proposal. |
| Catalogue articles | Products | partial | The catalogue is used when there is no ERP sync. Otherwise articles live in the ERP. |
What to expect
OData excludes TEXT/BLOB fields and some hidden system fields.
These are configuration, not data. They must be rebuilt in HubSpot.
Names are not translated into business aliases, so the database schema is needed.
Divalto profiles combine portal pages with read/write rights.
There is no config export. Scope note requires a rebuild.
The CRM syncs with the ERP and optionally Webmecanik, so these links need replacing.
Audit tables and views via OData against CSV exports before cutover.
Decide the system of record and keep ERP codes as unique HubSpot properties.
Request access and credentials early.
Rely on vendor docs, which confirm OData and webservices.
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.
Vendor docs confirm CSV export, a read-only OData API and webservices. They do not give a full object schema, auth details, rate limits or a HubSpot connector. Object mapping is therefore category-level analyst knowledge.
Sources
Related migrations
Frequently asked questions
How do I migrate Divalto weavy to HubSpot?
1. Inventory CRM tables and views with the Divalto partner and get the schema. 2. Request OData access, or confirm which tables the admin CSV export covers. 3. Enable table export rights for the migration profile. 4. Decide whether the ERP or HubSpot owns customer/tier data.
What data can move from Divalto weavy to HubSpot?
These objects move directly: Tiers (thirdparty: customers and prospects) and Contacts. Check the mapping table for partial and manual items.
What does not move from Divalto weavy to HubSpot?
TEXT/BLOB fields via OData and Automations, workflows, profiles/permissions and reports. Plan to rebuild or retire these.
How long does a Divalto weavy to HubSpot migration take?
Small (<20k records): 3-5 weeks. Mid (20k-200k records): 6-10 weeks. Large (>200k records): 10-18 weeks. These are planning estimates, not a quote.
What access do I need to export from Divalto weavy?
Admin portal import/export page; table export must be enabled per profile in the profile manager.
What compliance issues apply when moving Divalto weavy data?
Check: Possible customer health or financial data in free-text notes, if captured and Technician interventions may include site or personal addresses. Agree consent, retention and access rules before exporting.
Moving Divalto weavy 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