Migrate from solve 360 to Mailchimp

solve 360 Contacts map directly to Mailchimp subscribers within a single audience. Email address is the primary identifier and dedupe key. Standard fields (first name, last name, phone, address) migrate to Mailchimp's native and address-type merge fields. Any user-defined custom fields on the Contact record (text, number, date, selection types) become Mailchimp merge fields with matching type. Solve 360's lifecycle stage or status property migrates as a Mailchimp tag so segments can reproduce the original stage distribution.

solve 360 Companies do not have a standalone equivalent in Mailchimp because Mailchimp has no Account or Organization object. Company name and domain from solve 360 migrate as a COMPANY-NAME merge field on each subscriber. If a Contact is linked to a Company in solve 360, the company name is attached to that contact's subscriber profile. We create the COMPANY-NAME merge field in the destination audience before contact import. Multiple contacts linked to the same company share the same merge field value; Mailchimp has no concept of a shared organizational record.

solve 360 user assignments (who owns a Contact, Company, or Deal) map to Mailchimp subscriber tags or a OWNER merge field. We extract the full owner list from solve 360 during discovery, then apply owner tags during migration. If the destination team uses Mailchimp collaboratively, the OWNER tag helps route internal accountability without a formal assignment model. Note that Mailchimp has no concept of record-level permission sets or ownership-based access control.

solve 360 tags on Contacts and Companies migrate to Mailchimp tags as native equivalents. We extract every distinct tag from the solve 360 API, deduplicate the list, and apply the full tag set to each subscriber record during import. Tag preservation is one of the most important migration requirements for marketing teams because it underpins audience segmentation and campaign targeting in Mailchimp.

solve 360 custom fields on Contacts and Companies are created as Mailchimp merge fields before subscriber import. Field types map as follows: text and selection fields become text-type merge fields; number fields become number-type merge fields; date fields become date-type merge fields. We export the full field schema from solve 360 during discovery, then pre-create all merge fields in the target Mailchimp audience. Selection fields with a fixed set of options map to merge field options lists in Mailchimp.

solve 360 pipelines and stages (Deal pipeline assignments, Opportunity stages) have no direct Mailchimp equivalent because Mailchimp does not have a deal or opportunity object. We export the full pipeline structure during discovery. If the customer wants to preserve stage information for reporting or segmentation, we map pipeline stages to Mailchimp tags (e.g., PIPELINE_STAGE_PROSPECT, PIPELINE_STAGE_NEGOTIATION) applied to the subscriber record. Alternatively, stages can be documented as merge field values if the customer prefers a flat field over tags.

solve 360 file attachments on contacts, companies, tasks, and support requests are downloaded from the platform and bundled by parent record. Mailchimp's media library stores files for use in campaigns, but does not link them to specific subscriber records. We extract attachments from solve 360, bundle them into a folder structure matching the original record hierarchy, and deliver them as a downloadable archive alongside the migration report. Re-association with subscriber profiles in Mailchimp requires manual upload and linking within campaigns or templates.

solve 360 Tasks (status, priority, due date, assignee, time tracking) have no Mailchimp equivalent. Mailchimp's data model is subscriber-centric and does not include a task or to-do object. We export the task list as a structured CSV with record ID, title, status, assignee, due date, and parent record reference, then deliver it to the customer. Rebuild options include Mailchimp Customer Journeys for automated milestone triggers, a separate task management tool (Asana, ClickUp, Trello), or a manual prioritization exercise.

solve 360 Follow-ups (time-stamped activity records tied to contacts or companies) have no Mailchimp equivalent. Mailchimp tracks campaign-level engagement metrics (opens, clicks, unsubscribes) but does not store per-contact activity logs. We export follow-up records as a CSV with contact reference, follow-up date, description, and assignee. The customer uses this as a reference to recreate any relevant follow-up sequences in Mailchimp Customer Journeys or to inform a separate sales process tool.

solve 360 Support Requests (issue tracking tied to contacts or companies) have no Mailchimp equivalent. Mailchimp does not have a case, ticket, or issue tracking object. We export the support request history as a structured CSV including request ID, contact reference, company reference, status, description, and conversation thread summary. The customer should select a dedicated helpdesk platform (Zendesk, HubSpot Service Hub, Freshdesk) to receive this data separately if ongoing support tracking is required.

solve 360 Time Records (duration, date, billing flag, parent task or engagement reference) have no Mailchimp equivalent and are not migratable. Mailchimp's data model does not include a time tracking object. We export time records as a CSV reference file for the customer's billing, project management, or HR team to ingest into a dedicated time tracking tool.

solve 360 Workflow definitions (automated task sequences, intelligent scheduling, assignee notifications) encode logic specific to solve 360's automation engine and cannot be directly replayed in Mailchimp. We export the full workflow configuration as structured JSON metadata. Mailchimp's automation equivalent is Customer Journeys, which uses event-triggered branching rather than rule-based task assignment. We deliver a written workflow inventory with each automation's trigger, conditions, actions, and a recommended Customer Journey mapping, and the customer's team rebuilds them post-migration.