Migrate from Divalto weavy to Pipedrive

Divalto weavy Companies store the business entity, address, and industry data used by both sales and field technician workflows. We map company_name to Pipedrive Organization name, address fields to address_street, address_city, address_postal_code, and address_country, and industry to Pipedrive industry. The organization ID is used as the dedupe key. We preserve any custom fields defined on the Company object in Development Studio as custom Organization fields in Pipedrive created before import.

Divalto weavy Contacts carry the standard name, email, phone, and role fields plus any Development Studio custom fields. We map name, email address, phone number, and role/title to Pipedrive Person fields, and preserve owner assignments via email match against Pipedrive Users. Custom fields on Contact receive explicit type-mapped Pipedrive custom fields created in the destination account before migration begins.

Divalto weavy's suspect-to-prospect-to-client lifecycle maps to either Pipedrive's Lead object (if the prospect is unqualified) or to a Person record (if already qualified). We determine the mapping during scoping based on the customer's lead status values in Divalto weavy. Unqualified leads migrate to Pipedrive Lead; prospects and clients migrate as Person records linked to an Organization.

Divalto weavy Deals represent revenue opportunities tied to pipeline stages. We map deal title, value, expected close date, stage name, and owner email to Pipedrive Deal title, value, expected_close_date, stage_id, and owner_id. Stage mapping is the critical transform: we extract the full Divalto weavy stage list during discovery and configure matching Pipedrive pipeline stages before migration so that stage_id references resolve correctly.

Divalto weavy pipeline stages are configurable per organization with no documented API export of stage definitions. We request the stage list during vendor export coordination and replicate the stage names, probabilities, and order as Pipedrive Stages within the designated Pipeline. Custom stages defined in Development Studio receive explicit mapping notes and are flagged for manual confirmation before import.

Divalto weavy Activities capture calls, meetings, and action items logged against contacts or deals. We map activity type, date, description, and linked owner to Pipedrive Activity subject, done_date, note, and assigned_to_user_id. Activity history is migrated in full to preserve the sales timeline. Type-specific fields (call duration, meeting location) map to Pipedrive custom activity fields created during schema setup.

Divalto weavy user profiles (Standard, Sales, Technician, Full) are mapped by email match to Pipedrive User records. Divalto weavy profile assignments are preserved in a custom text field on the Pipedrive User record for audit and reporting. We resolve users by email lookup and hold any unmatched owners in a reconciliation queue for the customer's admin to provision in Pipedrive before record import.

Divalto weavy Development Studio custom objects vary per tenant with no documented schema export. We run a pre-migration schema audit to identify every custom object and field definition in the source account, then create equivalent Pipedrive custom fields on the appropriate standard object (Person, Organization, or Deal) before migration. Custom object relationships are flattened into lookup fields or multi-select picklists depending on cardinality.

Document attachments linked to companies, contacts, and deals in Divalto weavy are extracted as files and uploaded to Pipedrive File objects linked via the related Person, Organization, or Deal. Original filenames and file types are preserved. We map the parent object reference during import so files attach to the correct record in Pipedrive.

Divalto weavy's lead lifecycle statuses (suspect, prospect, client) are mapped to Pipedrive Lead status values. We extract the existing status list from the source export and configure matching status labels in Pipedrive Leads. Status transitions that have no Pipedrive equivalent are mapped to the nearest default status with a flag in a custom field for the admin to review post-migration.