Migrate from Divalto weavy to Twenty CRM

Divalto weavy Companies store the business entity with address data used by both sales and field technicians. We map the company name, industry classification, billing and shipping addresses, and domain data to Twenty's Organization object. The organization name serves as the dedupe key during import. Address fields in Twenty map to the standard address compound field. Owner assignment from Divalto is preserved as a custom field pending User lookup resolution.

Divalto weavy Contact records carry standard fields plus any custom properties created in the Development Studio. We map all standard fields (name, email, phone, job title, department) and flag every custom field for explicit mapping before schema creation in Twenty. Custom field type mapping follows Twenty's supported field types: text, number, currency, date, select, and boolean. Any multi-select properties from Divalto are created as select fields with the imported options enumerated.

Divalto weavy supports a suspect-to-prospect-to-client lifecycle with a lead status field. We map the lead status, source attribution, and any scoring data to Twenty's Lead object. If the customer uses Divalto's prospect-to-client conversion, the migrated Lead record retains a custom field indicating its Divalto origin stage so that the customer can decide whether to convert it as a fresh Lead in Twenty or manually attach it to an existing Contact and Organization.

Divalto weavy Deals represent revenue-generating opportunities tied to configurable pipeline stages. We map deal name, deal value, expected close date, stage, and owner to Twenty's Opportunity object. Stage mapping is configurable because Divalto pipeline stage names are tenant-specific. We extract the full stage list during discovery, map each to a Twenty Opportunity stage, and apply a custom stage_order field to preserve relative ordering. Closed-won and closed-lost outcomes from Divalto carry their loss reason or close notes into Twenty's opportunity custom fields.

Divalto weavy pipeline stages are configurable per organization with no standardized naming. We extract the complete stage list during the discovery phase and create corresponding stages in Twenty's Opportunity pipeline. Each stage receives a display name (mapped from Divalto) and a probability percentage migrated from Divalto's stage configuration. Any custom stages the customer has added beyond the standard Divalto lifecycle are created as new Twenty stages with the customer-provided probability.

Divalto weavy Activities capture calls, meetings, and action items logged against contacts or deals. We split the migration by activity type: logged calls migrate as Twenty Task records with TaskSubtype or a custom type field set to call; calendar-meeting records migrate as Event records with start and end timestamps; standalone action items migrate as Task records. All activity histories are migrated in full to preserve the sales interaction timeline for reps referencing past touchpoints.

Divalto weavy assigns user profiles (Standard, Sales, Technician, Full) that determine feature access. We extract all Divalto user records and resolve them by email against Twenty's workspace members. Any Divalto user without a matching Twenty account is held in a reconciliation queue for the customer's admin to provision. The original Divalto profile assignment migrates as a custom select field on the Twenty workspace member record for audit and access-control auditing.

Divalto weavy organizations with custom objects built in the Development Studio have non-standard schemas that vary per tenant. There is no documented schema registry or export of custom field definitions. We run a pre-migration schema audit to manually catalogue every custom object and field, then pre-create matching custom fields in Twenty under the appropriate standard object before any data is loaded. If a Divalto custom object has no natural Twenty standard object equivalent, we map it to a new Organization custom field set or a dedicated custom field group and document the design decision for the customer's approval.

Document attachments in Divalto weavy are linked to Companies, Contacts, and Deals. We extract the files from Divalto weavy, map them to the correct parent object and record in Twenty, and preserve the original filename, MIME type, and upload timestamp. File content is uploaded to Twenty's attachment storage during the import phase. Large attachment sets (over 1,000 files) are chunked to avoid timeout during the upload phase.

Divalto weavy's route planning and itinerary data are mobile-first features specific to its field workforce management design. Twenty CRM does not have a native route object or itinerary management feature. We do not include route or itinerary data in the standard migration package. If this data is business-critical, we offer a manual export workflow as a scoped add-on: we extract the route and itinerary records from Divalto weavy as a structured CSV and deliver it alongside the migration for the customer to review and archive separately.