Migrate from Lemon Tech to Mailchimp

Lemon Tech contact records export as structured rows with name, email, phone, address, and any linked entity references. We map each contact to a Mailchimp Audience member via email as the dedupe key. Standard contact fields map to Mailchimp merge fields (FNAME, LNAME, PHONE, ADDRESS). Any linked company or entity reference from Lemon Tech's relational model becomes a tag on the Mailchimp contact (e.g., tag: 'LinkedTo:Acme Corp') since Mailchimp has no entity lookup. Contact status or type in Lemon Tech (client, vendor, referral) maps to a segmented tag group for audience filtering.

Lemon Tech entities representing companies or organizations do not have a direct Mailchimp equivalent because Mailchimp has no Account or Company object. We decompose each Entity record into two parts: the entity name becomes a Mailchimp merge field (COMPANY) on the Contact record, and the entity-to-contact relationship becomes a tag (e.g., 'Entity:AcmeCorp'). For contacts with multiple linked entities, we create one tag per entity. If a contact has no email (entity-only record), we skip the contact import because Mailchimp requires an email address.

Lemon Tech Matters are case/project containers with no Mailchimp equivalent. We do not migrate Matters as records. For contacts that are Matter stakeholders, we extract the Matter name and create a tag (e.g., 'Matter:Smith-v-Jones') on the associated contacts to preserve the relationship at the contact level. The Matter status, dates, and billing data cannot be represented in Mailchimp and are flagged in the migration inventory as requiring a parallel CRM or project management tool if the customer needs to retain that data.

Lemon Tech Users map to the Mailchimp account users who will administer the platform post-migration, not to contact records. We do not migrate User records as contacts. During scoping, we identify which Lemon Tech users will be Mailchimp account administrators and the customer provisions those accounts directly in Mailchimp. The mapping is informational: we provide a list of Lemon Tech user emails and recommended Mailchimp permission roles (Admin, Manager, Author) based on their source role context.

Lemon Tech custom entities require decomposition because Mailchimp supports a maximum of 40 merge fields per Audience. We inventory all active custom entity types during discovery, identify the fields on each, and map them as follows: scalar values (text, number, date) become Mailchimp merge fields; multi-value or relational fields become tags. If a custom entity has more than 40 distinct fields across all types, we work with the customer to prioritize the 40 highest-value fields and document the remainder in the migration inventory for a potential custom integration or CRM replacement.

Lemon Tech file attachments associated with entities or matters have no Mailchimp equivalent. Mailchimp supports image embedding in campaigns and document links in email body, but not contact-level file attachments. We extract attachment filenames and parent record associations and list them in the migration inventory. If the customer needs to preserve attachment access, we recommend a document management system (SharePoint, Google Drive, Dropbox) with links stored as Mailchimp merge fields or tag metadata.

Lemon Tech time entries and billing records linked to Matters have no Mailchimp equivalent. Mailchimp has no invoicing, time tracking, or financial record object. We extract the billing record metadata (matter reference, billable amount, date, contact link) and list it in the migration inventory. If the customer needs to retain billing history, we recommend exporting to a spreadsheet or accounting system as a parallel workstream outside the Mailchimp migration scope.

Lemon Tech SQL Wrappers produce relational reporting tables that combine CRM data with custom SQL or third-party sources. These tables have no Mailchimp equivalent because Mailchimp's contact model is flat. We inventory all SQL Wrapper definitions during discovery, flag which wrappers reference live third-party data sources (these cannot be migrated as static records), and deliver a written map of wrapper outputs that the customer's admin can evaluate for re-implementation in a BI tool or a destination CRM if the migration extends beyond Mailchimp.