Migrate from STEL Order to Mailchimp

Mailchimp merge fields require type declarations before data lands

Mailchimp requires every custom merge field to be created with an explicit type (text, number, date, phone, address, or birthday) before any subscriber data is written to it. If STEL Order exposes job status, technician name, or service history as custom contact properties, those need to be pre-created as matching Mailchimp merge fields with the correct type. Text fields accept any string; number fields reject non-numeric values; date fields require ISO 8601 format. Failing to pre-create fields causes silent drops on those specific data points during the migration run. FlitStack AI audits STEL Order's custom property types and pre-creates matching Mailchimp merge fields before the migration batch commits.

STEL Order job and workflow automations have no Mailchimp counterpart

STEL Order automations fire on job lifecycle events — status transitions, technician assignments, invoice generation, and schedule changes. These are operational triggers that do not exist in Mailchimp's campaign-automation model, which is built around subscriber actions (opens, clicks, tag additions, sign-up form submissions). There is no translation layer between field-service event triggers and email marketing triggers. Any STEL Order automation logic must be audited and rebuilt in Mailchimp's automation builder using contact data that migrated successfully. FlitStack AI exports STEL Order workflow definitions as a reference document for your Mailchimp admin to use during the rebuild phase.

Company-to-contact relationship collapses to a single merge field

STEL Order maintains a proper many-to-one relationship between contacts and their parent customer/company record. Mailchimp has no native company object — the contact-company relationship does not exist at the schema level. We store the parent company name in a custom COMPANY merge field, but this is a denormalized string, not a foreign-key reference. Segmenting Mailchimp contacts by company requires matching on string values in the COMPANY field, which is case-sensitive and prone to mismatch if STEL Order uses inconsistent capitalization. You should review and standardize company name casing before migration runs.

Historical engagement data does not transfer — Mailchimp starts fresh

STEL Order does not track email engagement metrics (opens, clicks, unsubscribes) because its email functionality is transactional or bulk, not an analytics platform. Mailchimp's reporting suite — open rates, click rates, campaign-level revenue attribution — begins fresh after migration. Your historical engagement benchmarks from any previous email platform are not available in Mailchimp by default. We recommend exporting any available engagement history from STEL Order or your prior email platform before migration and storing it as a reference dataset separate from Mailchimp's native reports.

STEL Order's per-contact tags do not map natively to Mailchimp tags

STEL Order may allow per-contact labels or categories (e.g., VIP client, Commercial account, Residential customer). Mailchimp tags are applied to subscribers independently of merge fields and are case-sensitive. If STEL Order exposes contact-level categories, we create a TAG_SOURCE custom merge field carrying the original label so it is not lost. Actual Mailchimp tags must be applied manually or via a post-migration script because the tag creation API call is separate from the subscriber upsert call. We include a tag-application step in the post-migration validation checklist.