Migrate from Divalto weavy to Microsoft Dynamics 365 Sales

Divalto weavy Company records map to Microsoft Microsoft Dynamics 365 Sales Account. We extract the company name, industry classification, billing and shipping addresses, and any reference fields during the vendor-coordinated export, then map to Account fields (Name, Industry, Address fields). The Account is the first object imported because all Contact records require an AccountId parent lookup. Address handling flags the scenario where Divalto allows multiple address types per company and Dynamics 365 stores a single primary address per type; we collapse to the primary and flag any secondary addresses for the customer admin to decide on placement.

Divalto weavy Contact records map to Dynamics 365 Contact, with the AccountId resolved at import time by matching the Divalto Company name or domain to the Account created in the first phase. Standard fields (FirstName, LastName, Email, Phone, JobTitle) map directly. Any custom fields from the Divalto Development Studio are flagged for explicit mapping to either existing Contact fields or new custom fields on the Contact table in Dataverse.

Divalto weavy's suspect-to-prospect lifecycle stages map to Salesforce-equivalent Dynamics 365 Lead records. The Divalto lead status and source attribution fields migrate to Lead Status and LeadSource on Dynamics Lead. We preserve the original Divalto lifecycle stage in a custom field weavy_original_lifestage__c for reporting continuity. The customer's admin decides whether to convert migrated Leads to Contacts immediately or let them remain as Leads for assignment routing.

Divalto weavy Deals map to Dynamics 365 Opportunity. The deal name, estimated value, expected close date, stage, and owner migrate to Opportunity Name, Amount, EstimatedCloseDate, StageName, and OwnerId respectively. Stage values are extracted from the Divalto pipeline configuration during discovery and mapped to a Dynamics Sales Process that the customer configures in their destination org before migration begins.

Divalto weavy pipeline stages are configurable per organization with no standardized names. We extract the full stage list from the source during discovery and present it as a stage mapping table during scoping. Each Divalto stage maps to a Microsoft Dynamics 365 Sales Process stage value, with the probability percentage from Divalto carried into the StageProbability field. Custom stages that do not fit a standard sales process are mapped to a catch-all process or flagged for the customer to define.

Divalto weavy Activity records (calls, meetings, action items) linked to Contacts or Deals map to Dynamics 365 Task and Event records. Call activities with disposition and duration fields map to Task with TaskSubtype=Call. Meetings map to Event with StartDateTime, EndDateTime, and Location preserved. Each Activity's original timestamp is preserved in the ActivityDate field so the timeline ordering in Dynamics matches the Divalto history. Activity type classification from Divalto is stored in a custom field for any activity types that do not map cleanly to Task or Event subtypes.

Divalto weavy User profiles (Standard, Sales, Technician, Full) are extracted and mapped to Dynamics 365 User records. Matching is performed by email address. The Divalto profile assignment migrates to a custom field weavy_profile__c on the User record so the customer can reference original access levels during the transition. Users without a matching Dynamics 365 User go to a reconciliation queue for the customer's admin to provision before the Contact and Deal imports proceed.

Organizations with custom CRM objects built in the Divalto Development Studio have non-standard schemas with no documented export format. We handle this by running a pre-migration schema audit in the source environment, manually cataloguing every custom object name, field name, field type, and relationship. Each custom object is then pre-created as a Dataverse custom table with matching field types before data import begins. Lookup relationships from Divalto custom objects to standard objects (Company, Contact, Deal) are resolved at migration time using the primary keys from the previously imported standard records.

Divalto weavy document attachments linked to Companies, Contacts, and Deals are extracted as files and mapped to Dynamics 365 Annotation records (Notes with file attachments) attached to the corresponding Account, Contact, or Opportunity. If the customer's Dynamics 365 org has SharePoint integration enabled, we can alternatively route files to SharePoint document libraries and link them via SharePoint document locations on the Account or Opportunity. The choice between Annotation and SharePoint is made during scoping based on the destination org's configuration.

Divalto weavy route planning and itinerary data are mobile-first features designed for field workforce management and have no standard equivalent in Microsoft Microsoft Dynamics 365 Sales . The Field Service hub has a Resource Scheduling Optimization add-on that handles route optimization, but that is a separate product and license tier. We do not include route or itinerary data in the standard migration package. We offer a manual export of this data as a standalone CSV deliverable for the customer to archive or load into a separate system.