Migrate from GBuilder to Mailchimp

Merge field 255-character hard limit breaks long-text GBuilder fields

Mailchimp enforces a 255-character ceiling on all merge field values. GBuilder custom fields storing long-text notes, JSON metadata, description fields, or multi-line addresses exceed this limit frequently. FlitStack truncates at 255 characters and flags each affected record, but the truncation is irreversible within the Mailchimp import. Your team should identify which GBuilder long-text fields are business-critical before migration and decide whether to split them into multiple merge fields (for example, note_line_1 and note_line_2) or carry them as tags instead. Failing to pre-screen this creates data loss that is not apparent until after the audience is loaded.

Mailchimp cleans bounced contacts permanently — migration reactivates them if not handled

Mailchimp marks a member as 'cleaned' when an email hard bounces or the address is repeatedly unreachable. Cleaned members in Mailchimp are permanently suppressed and cannot be re-activated through normal imports — they require manual removal from the cleaned list by Mailchimp support or a manual API call per address. FlitStack exports GBuilder's cleaned-contact list separately and imports it as a suppression set rather than as members, so cleaned contacts do not re-enter Mailchimp as active subscribers. If your team has already manually re-permissioned some cleaned addresses in GBuilder, those contacts must be handled as a special re-engagement batch outside the standard migration flow.

GBuilder tag taxonomy flattens into Mailchimp's single tag namespace

GBuilder supports hierarchical or compound tags that encode multiple dimensions (for example, Source-Webinar-Q3 or Priority-High-Enterprise). Mailchimp stores a flat list of tags per member with no native hierarchy or key-value structure. FlitStack splits compound tags by delimiter into individual Mailchimp tags, but the original dimensional relationship is lost — a tag named 'Source-Webinar-Q3' becomes three separate tags: 'Source', 'Webinar', 'Q3'. If your GBuilder segmentation logic depends on compound tag patterns, those patterns must be rebuilt in Mailchimp's segment builder using tag combinations and merge field filters. The exported JSON of GBuilder tag definitions is the reconstruction reference for your Mailchimp admin.

Mailchimp audiences require a single email domain strategy at send time

Mailchimp's sending reputation is tied to your authenticated domain. If GBuilder contacts span multiple sending domains or include a high proportion of role-based addresses (info@, admin@, hello@), your Mailchimp sending reputation at go-live may be affected. FlitStack includes a pre-migration email quality audit that flags role-based addresses, known bad domains, and high-risk patterns before the audience is loaded. Cleaning the list before import is strongly recommended — Mailchimp's cleaned and bounce rates post-migration directly impact inbox placement across your entire audience.

GBuilder unsubscribed list requires explicit Mailchimp suppression import after main load

Mailchimp does not allow unsubscribed members to be imported as 'subscribed' through the standard bulk import endpoint — the unsubscribe status must be set through a separate suppression import operation using Mailchimp's Members API with status = unsubscribed, or by importing to a suppression list. FlitStack sequences the migration in three phases: active members first, then unsubscribed members via the suppression API, then cleaned members via the cleaned-list import. If this sequencing is not followed, unsubscribed contacts in GBuilder may appear as new subscribed members in Mailchimp, triggering compliance violations and reputation damage.