Migrate from Divalto weavy to HighLevel

Divalto weavy Companies store business entity data with billing and shipping addresses used by both sales and field technicians. We map company name, industry, website, and address fields to HighLevel Contact records at the organization level. The HighLevel Contact object holds both individual and organization data; we extract the organization-level fields and populate the contact_company field in HighLevel for later reporting and filtering by company.

Divalto weavy Contact records carry standard fields (name, email, phone, address) plus any custom properties from the Development Studio. We map all standard fields and flag custom fields for explicit mapping to HighLevel Custom Fields. Email and phone serve as dedupe keys during import to prevent duplicate Contact creation. Owner assignment from Divalto weavy maps to HighLevel Assigned To via email match against HighLevel User records.

Divalto weavy supports a suspect-to-prospect-to-client lifecycle. We map Leads to HighLevel Contacts with the original lifecycle status preserved in a Custom Field. If the customer has advanced pipeline stages that represent deals in progress, we map those to HighLevel Opportunities with the appropriate status value. The split rule is defined during scoping based on the customer's stage naming conventions.

Divalto weavy Deals represent revenue-generating opportunities tied to pipeline stages. We map deal name, value (mapped to HighLevel Opportunity amount), expected close date, stage, and owner. Stage names from Divalto weavy are mapped to HighLevel pipeline stage values, and the customer configures the HighLevel pipeline and stage labels before migration so the mapping is in place at import time.

Divalto weavy pipeline stages are configurable per organization. We extract the full stage list during discovery and create corresponding stages in HighLevel's Pipeline builder. Custom stage names (e.g., Proforma, Negotiation, Contract Sent) are mapped explicitly, and any stages that do not have a HighLevel equivalent are flagged for the customer to configure before migration begins.

Divalto weavy Activities capture calls, meetings, and action items logged against contacts or deals. We map activity type to HighLevel task type (Call, Appointment, or General Task), preserve the date and description, and link to the parent Contact or Opportunity via HighLevel's relationship model. Activity history migrates in full to preserve the timeline that sales reps rely on for context during customer conversations.

Divalto weavy assigns user profiles (Standard, Sales, Technician, Full) that determine feature access. We map user records and preserve the profile assignment in a Custom Field (divalto_profile) in HighLevel. Users are matched by email address, and any HighLevel User that does not have a corresponding Divalto weavy user is reconciled with the customer admin before Contact and Deal import to avoid orphaned owner assignments.

Divalto weavy Development Studio custom objects have non-standard schemas that vary per tenant. We run a pre-migration schema audit to catalog every custom object and field definition, then pre-create the equivalent Custom Objects in HighLevel using typed fields (text, number, date, dropdown, checkbox). Custom object records import after parent standard objects (Contact, Opportunity) to satisfy lookup dependencies. The customer configures lookup relationships in HighLevel before migration runs.

Document attachments linked to companies, contacts, and deals in Divalto weavy are extracted as files and mapped to the correct parent object in HighLevel. HighLevel supports file attachments on Contacts and Opportunities. Original file names and types are preserved. Large files (>25MB per HighLevel's upload limit) are flagged for manual handoff because they cannot be uploaded via the standard API.