Migrate from Divalto weavy to Salesforce Sales Cloud

Divalto weavy Company records store the business entity, billing and shipping address, industry classification, and revenue range used by both sales and field technicians. We map Company Name to Account Name, the Divalto address fields to BillingAddress and ShippingAddress composites, and industry to Industry picklist. Account is the first object imported because all Contact records require an AccountId Lookup reference to satisfy Salesforce's referential integrity requirements before insert.

Divalto weavy Contact records carry standard fields (name, email, phone, title, department) plus any custom properties created in the Development Studio. We map all standard fields, flag every custom field for explicit type mapping (text, picklist, number, date, lookup), and preserve any custom field values against the mapped Contact. Custom field schema must be pre-created in Salesforce before Contact import so that no custom field data is silently dropped.

Divalto weavy supports a suspect-to-prospect-to-client lifecycle tracked through lead status fields. We map the lead status, lead source, and rating fields directly to Salesforce Lead fields. If the customer uses the prospect-to-client conversion path, we map converted prospects to Salesforce Contact with the original lead source preserved in a custom field for attribution reporting.

Divalto weavy Deals represent revenue-generating opportunities tied to pipeline stages. We map Deal Name to Opportunity Name, Deal Value to Amount, Expected Close Date to CloseDate, Stage to StageName, and Owner to OwnerId. Stage mappings are configurable per organization; we extract the full stage list during discovery and map each stage to a Salesforce Opportunity Stage with the correct probability percentage.

Divalto weavy pipeline stages are configurable per organization with no standard stage name registry. We extract the complete stage list during discovery, map each stage to a Salesforce Opportunity Stage, and configure stage probability percentages. If the customer uses multiple Divalto pipelines, we create corresponding Salesforce Record Types on Opportunity with separate Sales Processes to keep stage values scoped per line of business.

Divalto weavy Activities capture calls, meetings, and action items logged against contacts or deals. We map activity type to TaskSubtype (Call for calls, null for general tasks), activity date to ActivityDate, description to Subject and Description, and linked owner to OwnerId. Meetings map to Salesforce Event with StartDateTime, EndDateTime, and Location preserved. Each activity record carries a WhoId (Contact or Lead) and WhatId (Opportunity or Account) reference that we resolve at migration time via parent-record lookup.

Divalto weavy assigns user profiles (Standard, Sales, Technician, Full) that determine feature access. We extract every distinct user referenced on Contact, Company, Deal, and Activity records and match by email against the destination Salesforce org's User table. We preserve the original Divalto profile assignment in a custom field divalto_profile__c on the mapped User record so the customer's admin can cross-reference during the transition period.

The Development Studio allows organizations to create custom CRM objects and custom fields with no documented schema export. We identify all custom object definitions during a pre-migration schema audit by requesting screen-shared access to the Development Studio environment, manually cataloguing every object name, field name, field type, and lookup relationship. We then pre-create the destination Salesforce custom object and all custom fields using the Metadata API before any data import. Custom object API names receive the standard __c suffix per Salesforce convention.

Document attachments linked to companies, contacts, and deals in Divalto weavy are extracted as binary files and mapped to Salesforce ContentDocument records linked via ContentDocumentLink to the parent Account, Contact, or Opportunity. We preserve the original filename and file extension, and map the created date to the Salesforce ContentVersion FirstPublishLocationId. Attachments stored as Salesforce Attachment objects are used as a fallback for smaller files.

Divalto weavy's suspect-to-prospect-to-client lifecycle uses custom status values that vary per tenant. We extract the full lead status picklist during discovery and map each value to a Salesforce Lead Status value that is included in the customer's lead conversion process. Status labels that have no Salesforce equivalent are mapped to a custom Lead Status picklist that the customer's admin finalizes before production migration.

If Divalto weavy records line items or product associations against Deals, we map them to Salesforce OpportunityLineItem. We resolve the Pricebook2 reference, the Product2 reference, and the parent Opportunity at migration time. Quantity, unit price, and discount percentage migrate directly. Pricebook entries are created during the product migration phase before line items are inserted.

Divalto weavy's route planning and geocoding data are mobile-first features specific to the field workforce management use case. Salesforce Sales Cloud has no native route object, and the Field Service add-on ($50/user/mo) manages work orders and service scheduling rather than sales route optimization. We flag this gap during scoping and offer a manual export workflow as an optional add-on, but route and itinerary data is excluded from the standard migration package. The customer decides whether to export this as a standalone report before cutover.