Migrate from Less Paper Co. to Mailchimp

Less Paper Co. Customers map directly to Mailchimp Contacts. Each contact record must contain a valid email address to be imported; records missing emails are flagged during the pre‑migration audit and held aside, then exported in the work‑order CSV for manual entry later. Duplicate emails are identified and resolved according to your chosen deduplication rule before the final import commit.

Email is the primary key in Mailchimp — it is both the unique identifier and the address used for all campaign sends. FlitStack AI validates email format and flags malformed addresses before import. Duplicate emails within the audience are merged or flagged per your chosen deduplication rule.

Mailchimp reserves FNAME and LNAME as built-in merge fields. Less Paper Co. name fields map directly. If Less Paper Co. stores a single customer_name field, FlitStack splits it on the first space and assigns the remainder to LNAME, with a fallback to populate FNAME only if the split is ambiguous.

Mailchimp's PHONE merge field stores a single phone number string. If Less Paper Co. has both phone and mobile_phone, the primary phone number populates PHONE and the mobile number is preserved as a custom merge field (e.g., PHONE_MOBILE__c) pre-created in the Mailchimp audience before import.

Mailchimp's ADDRESS merge field is a compound field (addr1, addr2, city, state, zip, country). FlitStack maps Less Paper Co. address components to the correct sub-fields. If Less Paper Co. stores billing and service address separately, the service address is mapped to the primary ADDRESS field and the billing address is stored as a custom merge field.

Work order service type (e.g., HVAC repair, plumbing, cleaning) has no native Mailchimp equivalent. FlitStack maps this to a pre-created custom merge field (SERVICE_TYPE) and optionally creates Mailchimp tags per service category so segments can filter contacts by the type of service they received historically.

Work order status (e.g., scheduled, in-progress, completed, cancelled) is stored as a custom merge field (WO_STATUS) in Mailchimp. For contacts with multiple work orders, the most recent status is used. Historical statuses across all work orders are preserved in the exported work-order CSV for reference.

Less Paper Co. account status (active, inactive, prospect) maps to Mailchimp tags: Active customers receive the 'Active' tag; inactive or lapsed customers receive 'Inactive' and are also flagged in a CUSTOMER_STATUS__c merge field. Segments can then filter by these tags for re-engagement campaigns.

Mailchimp has no work-order entity. FlitStack exports all work order records to a structured CSV (work_order_id, customer_email, service_date, technician, parts_used, labor_hours, total_amount, signature_on_file) that is delivered alongside the Mailchimp import so your team has a complete audit trail for any reporting or follow-up logic that needs to be rebuilt manually.

Mailchimp tracks no inventory, parts, or purchase orders. These records are outside the scope of a Mailchimp migration. If your team needs to reference parts data for customer communications, FlitStack can export inventory records as a separate reference CSV.

Less Paper Co. employee and technician records have no Mailchimp equivalent. If technicians need to receive Mailchimp notifications or campaign copies, they can be imported as contacts separately with a 'Team Member' tag, but this is a separate audience decision and not part of the standard customer migration scope.

Payment records and invoice history from Less Paper Co. do not map to Mailchimp. FlitStack exports this data as a separate payments CSV (customer_email, invoice_number, amount, date, payment_status) for your accounting or CRM team to handle independently of the Mailchimp audience migration.