Migrate from Divalto weavy to HubSpot

Divalto Weavy contact records map 1:1 to HubSpot Contacts. All standard fields (name, email, phone, job title, address) map directly. Divalto Weavy's mobile-first architecture means some records may have been created offline — FlitStack AI flags any record with an unsynced offline flag before migration and resolves the sync state before importing.

Divalto Weavy company records map to HubSpot Companies. Company addresses and website fields map directly. If Divalto Weavy stores multiple contacts per company, those associations migrate as HubSpot's primary company association for each contact — secondary associations require post-migration cleanup.

Divalto Weavy deal records map to HubSpot Deals. Divalto Weavy's deal status field (open, won, lost, abandoned) maps to HubSpot's dealstage pipeline stages via value-by-value mapping. The pipeline property requires a HubSpot custom property since Divalto Weavy uses a single pipeline model — FlitStack AI creates the pipeline in HubSpot during schema setup.

Divalto Weavy deal status values (open, won, lost, abandoned) map to corresponding HubSpot pipeline stage values. Each status maps individually — closed-won and closed-lost map to HubSpot's closed-won and closed-lost stages. FlitStack AI generates the value map during the planning phase and validates it in the sample migration.

Divalto Weavy stores a pipeline reference on each deal as a text field. HubSpot's native pipeline model requires the pipeline field as a separate configuration object. FlitStack AI creates the HubSpot pipeline structure and maps the Divalto Weavy pipeline value to the HubSpot pipeline name via a custom property.

Divalto Weavy activity records map to HubSpot's native engagement objects. Call logs, emails, and meetings carry their original timestamps and owner references. HubSpot's engagement timeline displays these records on the associated contact, company, or deal record page. Each activity type (calls, emails, meetings) becomes a distinct record type in HubSpot with its own properties and associations to CRM records.

Divalto Weavy notes migrate to HubSpot Notes with the original note body and create date preserved. Notes are associated to the parent contact, company, or deal record via HubSpot's association model. The full note content transfers including any formatting or embedded references, maintaining the complete audit trail from the source system.

Divalto Weavy file attachments on contacts, companies, and deals are downloaded and re-uploaded to HubSpot Files. Files are re-associated to the parent CRM record. HubSpot's file size limit (25MB per file) applies — files exceeding this threshold are flagged for manual handling.

Divalto Weavy custom fields (GPS coordinates, technician IDs, route-optimization flags, offline-sync status) migrate as HubSpot custom properties. FlitStack AI creates each custom property in HubSpot with the appropriate type (text, number, date, or picklist) based on the source field's data type before the migration run.

Divalto Weavy owner references on deals and contacts resolve by email match against HubSpot users. Unmatched owners are flagged before migration — your team either creates HubSpot user accounts or assigns those records to a fallback owner. No record lands in HubSpot without a resolved owner.

Divalto Weavy's offline-sync capability means some field records may have been created while offline. FlitStack AI flags records with unsynced offline changes and resolves them before migration — the offline_sync_flag property migrates as a custom property on the contact for audit trail purposes.

Divalto Weavy's route-optimization module stores GPS coordinates and route sequences per technician visit. HubSpot has no native route or territory management feature. FlitStack AI migrates this data as a custom text property for reference — the route-optimization workflow itself must be rebuilt using a third-party route tool post-migration.

Divalto Weavy's field-service module creates service tickets with technician assignments and visit scheduling. If your Divalto Weavy instance uses field-service tickets, FlitStack AI maps these to HubSpot Tickets. Ticket-to-contact and ticket-to-company associations are preserved, and the technician assignment becomes a custom HubSpot contact property.

Divalto Weavy supports a primary contact-to-company association per contact. FlitStack AI maps this to HubSpot's primary company association on the contact record. Secondary company associations from Divalto Weavy are surfaced in a custom multi-select property for reference and post-migration admin review.

Divalto Weavy's internal record IDs are preserved on every migrated record as a custom property (Source_System_ID__c). This enables delta-run de-duplication, audit traceability, and cross-referencing between Divalto Weavy's original records and HubSpot's migrated records. The ID mapping ensures data lineage is maintained throughout the migration lifecycle and supports future sync operations if needed.