Migrate from Divalto weavy to Freshsales

Divalto weavy Company records map directly to Freshsales Account. We extract the company name, industry classification, billing address, and shipping address from the source export, then map them to the corresponding Freshsales Account fields. The source export's unique company identifier is preserved in a custom field divalto_id__c for audit and reconciliation. Parent-company hierarchies in Divalto weavy map to Freshsales parent Account relationships if the destination Account already exists from a prior import phase.

Divalto weavy Contact records map to Freshsales Contact with standard field mapping for name, email, phone, mobile, job title, and address fields. Any custom fields created in the Development Studio are flagged for explicit mapping to Freshsales custom fields that we pre-create in the destination account before import. We use email as the deduplication key and flag duplicate Contact records for customer review before insert.

Divalto weavy's suspect-to-prospect-to-client lifecycle stages map to Freshsales Lead Status values. We extract the current stage name and the lead source field and map them to Freshsales lead_status and lead_source respectively. Any custom lead fields from the Development Studio migrate to Freshsales custom fields on the Lead object. Prospects in late stages (sales-qualified or client) may be migrated as Contacts attached to Accounts instead if the customer's Freshsales admin prefers to skip the Lead object entirely.

Divalto weavy Deals map to Freshsales Deal records. We map deal name, deal value, expected close date, stage, and owner. Stage names from Divalto weavy's configurable pipeline are mapped to Freshsales deal stage values, which are also configurable in the destination. Owner resolution uses email matching against the Freshsales User table; unresolved owners are held in a reconciliation queue for admin provisioning.

Divalto weavy's configurable pipeline stages are extracted during discovery and mapped to Freshsales deal stage values. Each stage's probability percentage migrates to the corresponding Freshsales stage probability field. We flag any custom stages that have no obvious Freshsales equivalent for explicit customer review before import.

Divalto weavy Activities (calls, meetings, action items) map to Freshsales Task and Event records. Call activities become Task records with subtype=Call and duration preserved in a custom field. Meeting activities become Event records with start time, end time, and location preserved. We link each activity to its parent Contact or Deal via the WhoId and WhatId references, which we resolve at migration time using the email and deal name lookup keys established during the earlier import phases.

Organizations with custom objects or custom fields built in the Development Studio have schemas that vary per tenant and have no documented export format. We handle this by running a pre-migration schema audit that manually catalogues every custom object and field definition, then pre-creates equivalent Freshsales custom fields before any data loads. Custom object relationships to standard objects (Company, Contact, Deal) are recreated as Freshsales lookup or association fields. This step adds one to two weeks to the discovery phase but prevents silent data loss on non-standard fields.

Divalto weavy user profiles (Standard, Sales, Technician, Full) are extracted from the source data and mapped to Freshsales User records. We resolve by matching the user email address between the two platforms. Any Divalto weavy user who does not have an active Freshsales license is flagged for the customer's admin to provision before the Contact and Deal import phases begin, because OwnerId references on Deals and Contacts require a valid User lookup.