Migrate from Divalto weavy to Zoho CRM

Divalto weavy Company records map to Zoho CRM Accounts. The company name, industry, billing and shipping addresses, phone, website, and annual revenue fields map directly. Divalto weavy's company unique identifier becomes the Account Id for cross-referencing during Contact import. We use Account Name as the dedupe key and preserve the Divalto company ID in a custom field diva_company_id__c for reconciliation.

Contact records from Divalto weavy map to Zoho CRM Contacts with first name, last name, email, phone, mobile, job title, and address fields preserved. Any custom fields defined in the Development Studio are flagged for explicit mapping to Zoho custom fields before migration. We resolve the parent Account by matching the Divalto company name to the Zoho Account Name or ID. Contact owner maps by email match to Zoho Users.

Divalto weavy Lead records (suspect-to-prospect-to-client lifecycle) map to Zoho CRM Leads. We preserve the lead status and source fields, the Divalto lead ID, and any custom lead properties. Unlike the HubSpot-to-Salesforce split, Divalto weavy and Zoho CRM both use a separate Lead object for unqualified prospects, so no object-type split is required. We set Lead Status to a value matching the Zoho picklist defined in the destination org.

Divalto weavy Deals map to Zoho CRM Deals. We map deal name, amount, expected close date, stage, and owner. Stage mapping is explicit: each Divalto weavy pipeline stage name is mapped to a Zoho CRM Stage picklist value during the schema audit. We resolve the parent Account and Contact lookups before Deal insert.

Divalto weavy configurable pipeline stages are extracted during discovery and mapped to Zoho CRM Stage picklist values. We configure the Zoho pipeline with matching stage names, probability percentages (mapped from Divalto where available), and forecast category assignments. Any custom stages without a Zoho equivalent are added to the Stage picklist during schema setup before Deals are imported.

Divalto weavy Activities (calls, meetings, action items) map to Zoho CRM Tasks and Events. Call activities become Tasks with Task Type set to Call and Call Duration preserved; meeting activities become Events with Start DateTime and End DateTime; general action items become Tasks. We link activities to their parent Contact, Account, or Deal using the Zoho Related To field (WhoId and WhatId equivalents) resolved from the Divalto source record references.

Document attachments linked to companies, contacts, and deals in Divalto weavy are extracted as files and imported as Zoho CRM Attachments linked to the corresponding Account, Contact, or Deal record. We preserve the original filename and content type. Parent record lookup is resolved using the Divalto record ID-to-Zoho record ID cross-reference table built during the migration mapping phase.

Divalto weavy user records (Standard, Sales, Technician, Full profiles) map to Zoho CRM Users. We match by email address and preserve the Divalto profile assignment in a custom field diva_user_profile__c on the Zoho User or in a custom field on migrated records. Active users are mapped directly; inactive or archived Divalto users are flagged for the customer admin to provision in Zoho before the User-dependent record phases run.

Custom objects created in Divalto weavy's Development Studio migrate to Zoho CRM Custom Modules. We identify all custom object definitions during a pre-migration schema audit, create matching Custom Modules in Zoho with equivalent field types (text, number, date, picklist, lookup), and migrate records using Zoho's Bulk API with chunking. Lookup relationships between custom objects and standard objects are resolved using the cross-reference table before import. The Development Studio schema audit is a required first step because there is no documented schema export from Divalto weavy.

Divalto weavy tracks contacts across a lifecycle from suspect through client. If the source organization used separate Lead and Contact objects for different lifecycle stages, we consolidate them into Zoho CRM's Lead and Contact objects using status-based routing: leads (unqualified or early-stage) map to Zoho Lead; qualified contacts map to Zoho Contact attached to an Account. We preserve the original lifecycle stage in a custom field diva_lifecycle_stage__c on both Lead and Contact for reporting continuity.