Migrate from Texada Software to Mailchimp

Mailchimp bills based on total audience size including unsubscribed and cleaned contacts

Unlike Texada which charges per seat or by module, Mailchimp's pricing tier is determined by the total count of contacts in an audience — including unsubscribed and cleaned (bounced/complained) records. Migrating a large Texada customer base with many inactive contacts will increase your Mailchimp bill even if you never email those contacts. We recommend auditing Texada's inactive customer count before migration and either cleaning the list beforehand or planning a suppression-segment strategy in Mailchimp to avoid unnecessary billing. FlitStack surfaces the inactive-to-active ratio in the pre-migration audit report so you can make an informed decision before contacts land.

Email consent tracking requires explicit handling when migrating from Texada's implicit model

Texada's marketing_opt_in flag is a boolean property on the customer record, not a timestamped consent log with GDPR-style granularity. Mailchimp's compliance model requires a clear opt-in basis for each contact. Contacts flagged as active in Texada but with no explicit marketing consent cannot be imported as subscribed in Mailchimp without reconfirmation. We implement a double opt-in flow for these contacts: they import as pending status and receive a Mailchimp confirmation email before being counted as subscribed. This adds a step but protects your sender reputation and ensures GDPR/CCPA compliance. We flag all ambiguous consent records in the pre-migration report so your team can decide on a consent strategy before the migration runs.

Duplicate email addresses across Texada locations collapse to one Mailchimp contact

Texada supports multiple customer records that may share the same email address across different locations or divisions within the same company. Mailchimp enforces one contact record per email address within a single audience. If the same email appears in multiple Texada location records, those contacts will merge into a single Mailchimp contact during migration. We surface duplicate email occurrences in the pre-migration report and allow your team to choose a merge rule (keep most recent, keep by location, keep by active status) before migration commits. This prevents unintended data loss where multi-location customer records collapse to one.

Mailchimp's 40-merge-field limit may compress Texada custom properties

Texada SRM allows arbitrary custom properties on customer and company records. Mailchimp caps merge fields at 40 per audience. Teams with more than 40 custom Texada properties face a field-selection decision: we surface all custom properties in the pre-migration audit, prioritize the 40 most operationally relevant fields for merge-field creation, and bundle the remainder into a JSON-encoded TEXT merge field that Mailchimp can parse for reference. This is not ideal for segmentation but preserves all data. We recommend reviewing the custom property list with your marketing team before migration to choose which fields drive segmentation versus which are archival.

Domain authentication must be verified in Mailchimp before sending from migrated addresses

Mailchimp requires DKIM, SPF, and DMARC authentication records to be published for the domain your emails will send from. If your Texada account uses a domain for customer email addresses that differs from your intended Mailchimp sender domain, or if authentication records are not set up before migration, email deliverability will suffer. FlitStack includes DNS authentication guidance as part of the migration package, but DNS propagation (24–72 hours) is outside our control. We recommend setting up domain authentication in Mailchimp at least 72 hours before your first campaign send from the migrated audience.