Migrate from Estimate Rocket to Mailchimp

Estimate Rocket estimates and work orders have no native Mailchimp object—project history survives only as tagged notes

Mailchimp has no native equivalent to Estimate Rocket's project, estimate, work order, or invoice objects. When you migrate, project names, estimate totals, work order details, and invoice histories become formatted text notes attached to the subscriber profile. These are reference records, not operational data—if your team needs to see the full project history or regenerate an invoice in Mailchimp, that is not possible. FlitStack surfaces this limitation upfront and gives you the option to include or exclude project/estimate note exports based on whether you need the reference data in Mailchimp or prefer to archive it separately.

Mailchimp requires merge fields to be pre-created before bulk import—Estimate Rocket custom properties need schema setup

Mailchimp's merge field system requires you to create each custom field in your audience settings before data can populate it. Estimate Rocket custom client properties (e.g., 'Equipment Make', 'Contract Type', 'Preferred Service Day') do not auto-create Mailchimp merge fields during import. FlitStack generates a merge field creation checklist based on your Estimate Rocket custom property list, and your Mailchimp admin must pre-create these fields (with correct types: text, number, date, dropdown) before the migration import runs. Mismatched merge field types cause import failures that require re-export and re-import.

Clients without email addresses cannot migrate as Mailchimp subscribers and require a separate handling decision

Estimate Rocket stores clients with phone numbers and addresses who may not have an email address on file. Mailchimp requires a valid, deliverable email address to create a subscriber—clients without email cannot be imported as subscribers and will be flagged in the pre-migration data audit. Your team must decide whether to exclude these records, export them to a separate spreadsheet for manual outreach, or enrich them with email addresses before migration. FlitStack generates a 'no-email' client report during the planning phase so this decision is made before data moves.

Mailchimp contact-based pricing means migrated Estimate Rocket clients count toward your subscriber limit from day one

Mailchimp pricing is subscriber-based—you pay for the total number of contacts in your audience regardless of whether they are actively marketed to. If your Estimate Rocket client list includes inactive clients, past clients, or records that have never received an email, those records still count toward your Mailchimp subscriber tier. Teams migrating large historical client lists from Estimate Rocket may see an immediate pricing tier jump in Mailchimp. FlitStack's pre-migration audit includes a subscriber count estimate against Mailchimp's current pricing tiers so you can plan your budget accordingly.

Estimate Rocket follow-up campaigns and email templates require complete manual rebuild in Mailchimp's automation builder

Estimate Rocket's follow-up campaign feature sends emails based on project phase transitions and estimate status changes. Mailchimp's automation builder does not import these campaign definitions—they must be rebuilt from scratch using Mailchimp's trigger-based logic, time delays, and condition branches. Email templates created in Estimate Rocket use a token-based system with dynamic field insertion that does not map to Mailchimp's template format. FlitStack exports your Estimate Rocket email template content and token references as a rebuild document, but the actual template construction and automation logic is a manual project for your Mailchimp admin.