Migrate from Divalto weavy to Mailchimp

Divalto weavy Contact records migrate directly to Mailchimp Subscribers within a designated Audience. We map the contact's email address as the Subscriber email (required for Mailchimp), first name to FNAME merge tag, last name to LNAME merge tag, phone to PHONE merge tag, and address fields to ADDRESS merge tag. Any custom fields on the Divalto contact created in the Development Studio map to custom merge tags in Mailchimp that we create during migration. Duplicate email detection uses Mailchimp's built-in dedupe on email address. The contact's owner assignment in Divalto does not map to a Mailchimp field; owner tracking requires a separate administrative spreadsheet.

Divalto weavy Company records carry business entity data (company name, industry, billing address, website) that has no native equivalent in Mailchimp. We resolve the Company-to-Contact relationship from Divalto weavy during migration and apply company-level data as merge tags on each related Subscriber. COMPANY_NAME maps to a custom COMPANY merge tag; INDUSTRY maps to INDUSTRY; WEBSITE maps to WEBSITE. Subscribers without a linked Company receive a blank merge tag. This is a denormalization step because Mailchimp does not have a separate Company object; all company context lives on the individual subscriber record.

Divalto weavy Lead records (prospects in the suspect-to-client lifecycle) migrate as Subscribers with a LEAD_STATUS custom merge tag carrying the original Divalto stage value. If the lead has not yet been converted to a Contact in Divalto weavy, we preserve the lead source and score in custom merge tags (LEAD_SOURCE, LEAD_SCORE) so the marketing team can segment based on original lead origin. Lead conversion data (converted date, converted-to Contact reference) is preserved as text fields but cannot create a relationship in Mailchimp's flat subscriber model.

Divalto weavy Deals (Opportunities) with deal name, value, stage, expected close date, and owner have no Mailchimp equivalent. Mailchimp does not manage revenue pipeline, deal stages, or opportunity records. We extract the full Deal inventory during scoping and deliver it as a CSV export for the customer's records. If the customer requires deal tracking post-migration, we recommend a separate CRM tool (Salesforce, HubSpot, Pipedrive) and do not include Deal data in the Mailchimp load. This is an explicit scope exclusion documented in the migration handoff.

Pipeline stages in Divalto weavy are configurable per organization and tie directly to Deal management. Mailchimp has no pipeline or stage concept. We extract the complete stage list and probability mapping during discovery and include it in the Deal export CSV. If the customer uses pipeline stages to drive marketing segments (e.g., active pipeline customers excluded from re-engagement campaigns), we translate stage-based logic into Mailchimp segment filters using custom merge tags populated from the Deal export.

Divalto weavy Activities (calls, meetings, tasks, notes) with type, date, description, and linked owner represent the sales interaction history. Mailchimp does not have a native activity log for sales calls or meetings; it tracks email engagement (opens, clicks, bounces) only. We do not migrate Divalto activity history into Mailchimp. We deliver the activity history as a CSV export linked by contact email for the customer's administrative records. If email engagement data exists in Divalto weavy (sent emails tracked in Divalto), we map those to Mailchimp campaign activity where the email address overlap allows a match.

Divalto weavy contact Segments (the platform's built-in segmentation feature) map to Mailchimp Audiences. The official Divalto-Mailchimp integration synchronizes segments to Mailchimp in real time, but a structured migration replays the full segment membership during the initial load, ensuring each Divalto segment maps to a dedicated Mailchimp Audience or a Mailchimp Tag within a unified Audience. We map segment membership as Tags in Mailchimp (e.g., a Divalto segment 'Enterprise Prospects' becomes a Mailchimp Tag 'Enterprise_Prospects') and optionally as a segment filter if the customer prefers dynamic membership over static Tags.

Divalto weavy Users with profile assignments (Standard, Sales, Technician, Full) map to Mailchimp workspace Users. We extract the user list and map email addresses to Mailchimp user invitations. Profile roles do not have direct Mailchimp equivalents; Mailchimp uses Account-level roles (Admin, Author, Manager, Viewer). We preserve the Divalto profile as a text field in the user handoff document. Migration of inactive Divalto users depends on whether the customer wants them provisioned in Mailchimp or held for reconciliation.

Divalto weavy custom objects and custom fields built in the Development Studio have no native Mailchimp equivalent. We identify every custom object definition during discovery and evaluate whether the data maps to a contact-level attribute (eligible for Mailchimp merge tag) or a related-record attribute (requires archival). Custom fields on Contact that represent customer attributes (industry vertical, contract tier, renewal date) map to Mailchimp merge tags. Custom objects that represent independent entities (projects, contracts, vehicles) do not migrate to Mailchimp and are documented in the handoff for the customer's admin to decide on archival or alternative system storage.