Migrate from MiniCRM to Mailchimp

MiniCRM Contact records map directly to Mailchimp subscribers within a target Audience. We map email address (primary key), first name, last name, phone, and address fields to their Mailchimp merge tag equivalents (FNAME, LNAME, PHONE, ADDRESS). All contacts import with subscriber status; we check the MiniCRM unsubscribe/export field and set Mailchimp Status accordingly to respect prior opt-outs.

MiniCRM Cards are the primary record container and hold custom field values (Pola dodatkowe). We detect every custom field defined on Cards during scoping, create corresponding merge tags in the Mailchimp Audience (text, number, date, or choice type), and map the stored values at import time. Choice fields require value normalization since MiniCRM choice labels may differ from Mailchimp dropdown options.

MiniCRM Company records map to a COMPANY merge tag on the Contact. We extract the company name from the related Card and write it to the merge tag at import. If the customer uses company-level segmentation in MiniCRM, we create Mailchimp Tags per unique company name instead, allowing audience segmentation by organization without a native company object.

MiniCRM Deals (Interesy) are pipeline records with stage, value, and close date. Mailchimp has no opportunity or deal object. We do not migrate deal records. During scoping we document every active MiniCRM deal with its stage and value so the customer's admin can decide whether to track these in a spreadsheet, a separate CRM, or a Mailchimp-integrated tool like a Zapier-connected spreadsheet. This is a manual rebuild scope item, not a data migration gap.

MiniCRM Tasks with assignees, due dates, descriptions, and recurrence patterns have no Mailchimp equivalent. Mailchimp does not include a task management or to-do object. We export task records as a CSV for the customer's reference and note that project management tools (Asana, Trello, ClickUp) are the appropriate replacement for task tracking post-migration.

MiniCRM free-text Notes attached to Cards migrate as note text in the Mailchimp contact profile. Mailchimp allows a single note field per contact. For Cards with multiple notes, we concatenate with timestamps and add a Mailchimp tag (e.g., historical-notes) to indicate multi-note origin. Note attachment files are flagged as a separate deliverable since file migration requires URL or storage reference handling.

MiniCRM tags applied to Cards for segmentation migrate as Mailchimp Tags on the corresponding subscriber. We deduplicate the tag taxonomy during scoping — MiniCRM's tag usage at the micro-SMB level is typically small, but we flag any overly broad or inconsistent tagging patterns that would create noisy segmentation in Mailchimp.

MiniCRM Users with email, name, and role map to Mailchimp team member accounts. We match by email address. Mailchimp's permission model (Admin, Manager, Author, Viewer) differs from MiniCRM's role structure; we assign the closest Mailchimp permission tier during migration and flag any MiniCRM role that has no direct Mailchimp equivalent for the customer's admin to adjust.

MiniCRM automation rules (when a Card enters status X, send email and assign task) do not export and have no Mailchimp equivalent as a transferable artifact. We document every active automation rule during discovery, capturing the trigger (status change, field fill, date), conditions, and actions. We deliver this as a written rebuild guide with recommended Mailchimp Flow equivalents. The customer's admin or a Mailchimp specialist rebuilds the automations post-migration.

MiniCRM custom fields on Cards (text, number, date, choice) require pre-creation of corresponding Mailchimp merge tags before import. We create the merge tags in the target Audience during the schema phase, matching field type to Mailchimp's allowed types (text, number, date, phone, address, dropdown). Choice fields require a value mapping table from MiniCRM labels to Mailchimp options. Polish-language field labels are translated with the customer's confirmation during scoping.