Migrate from OneSuite to Mailchimp

OneSuite Client records map to Mailchimp contacts within a designated audience. Each Client's email address becomes the contact email (the required Mailchimp identifier), first name and last name map to FNAME and LNAME merge tags, and any company name from the Client record maps to a COMPANY merge tag. We deduplicate by email during import to prevent duplicate contacts. Phone, address, social links, and ICP status migrate to text merge tags with slug remapping (e.g., clientTier becomes CLIENTTIER merge tag).

OneSuite Leads map to the same Mailchimp audience as Clients, with Lead pipeline stages reconstructed as Mailchimp segments. Each Lead's email, name, phone, source attribution, and scoring value migrate to contact fields and merge tags. We create one Mailchimp segment per distinct OneSuite pipeline stage (e.g., New, Qualified, Proposal Sent, Won, Lost) using Mailchimp segment filter conditions. Leads without an email address are flagged during discovery; they cannot migrate to Mailchimp contacts without a valid email address.

OneSuite Members (team users) are internal staff, not external contacts. If the customer's Mailchimp audience includes internal subscriber lists (newsletter for team, internal announcements), Members migrate as contacts with an internal-team tag applied. Otherwise, Members do not migrate as Mailchimp contacts because they are not subscriber records. Assignment relationships linking Members to Clients or Projects do not have a Mailchimp equivalent and are not migrated.

OneSuite custom fields are flattened directly onto entities with their slug as the key (e.g., client-tier appears as clientTier). We remap each slug to a Mailchimp merge tag name using uppercase convention (CLIENTTIER). Mailchimp text merge tags are capped at 255 characters; any OneSuite custom field value exceeding this limit is truncated with a flag in the migration report. Date, number, and dropdown fields in OneSuite map to Mailchimp Date, Number, and Radio/Dropdown merge field types respectively. Merge tags are created in the audience before import.

OneSuite Lead pipeline stages are user-defined and vary by agency. We create one Mailchimp segment per distinct stage name (e.g., New Lead, Qualified, Proposal, Negotiation, Won, Lost) using Mailchimp segment conditions that filter by the stage merge tag value. Mailchimp segments are filter-based and recalculate dynamically, so the migrated segment membership reflects current contact data at any point. Any stage with custom automation or scoring rules is flagged in the handoff document for manual rebuild in Mailchimp Customer Journeys.

OneSuite Invoices reference Clients and contain line items, tax rates, payment status, and currency. Mailchimp has no invoice or billing record object. Invoices are not migrated. We provide a record count and field inventory of all Invoices as part of the migration scope document so the customer's finance or operations team can assess whether an alternative billing tool or spreadsheet export is needed post-migration.

OneSuite Documents and Files attach to Clients or Projects with metadata (name, type, URL) and binary content. Mailchimp does not have a file management or document storage layer. We migrate document and file metadata URLs as text merge tags but do not migrate binary content. Files exceeding OneSuite storage tier caps (30 GB Freelancer, 60 GB Growing Agency) are flagged during discovery; the customer manages file archival separately.

OneSuite Projects link to Clients and contain tasks and milestones. Mailchimp has no project or task management object. Projects are not migrated. We provide a project count and client association map as part of the handoff document. If the customer maintains project-related client notes (e.g., project status, deliverables), those migrate as text merge tags on the corresponding contact.