Migrate from Ploomes CRM to Mailchimp

Ploomes Contact records map directly to Mailchimp Audience Members. We extract first name, last name, email address, phone number, address fields, and any custom field values created via the Ploomes POST /Fields endpoint. CNPJ/CPF identification values stored in Ploomes custom fields are preserved in a Mailchimp custom merge field (type TEXT) because Mailchimp has no native Brazilian tax-ID field. Tags applied to the Ploomes Contact are recreated as Mailchimp Tags on the matching Audience Member. The Ploomes Contact-Company association is preserved by adding the Company name as a merge field (COMPANY) or as a tag on the contact record.

Ploomes Companies are distinct records not replicated as a separate Mailchimp object. Each Company record generates a CompanyName merge field value that we attach to the related Contact records as a COMPANY merge field. Teams that rely on account-based segmentation in Ploomes can use the Mailchimp COMPANY merge field to build segments by company name or recreate company groupings as Tags. We document the full Company record list separately so the customer can reference it for any account-based reporting or re-import if needed.

Ploomes Tags are a flat tagging system applied across Contacts, Deals, and Companies. Tags attached to Ploomes Contacts migrate to Mailchimp Tags on the corresponding Audience Members. Ploomes tags used for pipeline or deal categorization are preserved as tags on the contact record but the customer should note that Mailchimp has no deal context to interpret them against; we document which tags relate to pipeline stages so the customer can rename or suppress them post-import.

Ploomes custom fields created via POST /Fields migrate to Mailchimp merge fields. We map Ploomes field types to Mailchimp merge field types: text fields become TEXT, number fields become NUMBER, date fields become DATE, checkbox fields become ADDRESS or TEXT depending on structure. All custom field definitions are exported before contact migration begins, and the corresponding Mailchimp merge fields are created in the Audience before any contact records are upserted. Customers with more than 30 custom fields should be aware that Mailchimp's per-audience merge field limit is 40, and we flag this constraint during scoping.

Ploomes Owner records (sales reps assigned to Contacts and Deals) do not have a native Mailchimp equivalent. We extract the owner name and email and attach them as a merge field OWNER_NAME on the Contact record so teams can still segment or report by rep. Owner email is not stored as a contact field to avoid duplicating the contact email; the name field provides the reference. If the destination Mailchimp account is used by multiple Ploomes owners, we recommend using Mailchimp Tags to indicate owner assignment rather than merge fields.

Ploomes Deals with pipeline stages, deal values, owners, and stage histories have no equivalent in Mailchimp. Mailchimp is an email marketing platform and does not track opportunities, deal stages, or sales pipelines. We export the Deal record list (deal name, value, stage, owner, associated contact) as a CSV inventory delivered alongside the migration, and document it as a manual-rebuild scope for the customer's sales or RevOps team. Teams relying on deal tracking should not use Mailchimp as their primary CRM.

Ploomes Quotes with line items, totals, approval status, and custom properties are excluded from Mailchimp migration because Mailchimp has no quoting or proposal object. Quote version history is not accessible via the Ploomes public API in any case, so only the current quote state could theoretically transfer. We recommend exporting quote PDFs manually from Ploomes before the migration window and storing them in a shared drive. We deliver a quote inventory CSV listing all active and historical quotes as a handoff document.

Ploomes Workflows define automated rules, SLA triggers, checklists, and approval flows and are not accessible via the documented public REST API at api2.ploomes.com. We cannot export them programmatically. We perform a discovery-phase workflow audit where we document the trigger conditions, actions, and recipients for each active Ploomes Workflow and deliver a written Workflow Audit Checklist. The customer rebuilds automation logic in Mailchimp Customer Journeys or in a separate automation tool. This is standard scope for all Ploomes departures.