What happens when data fields change or merge?

You're tidying up your ESP's field list. You rename "purchase_date" to "last_order_date" and assume it's a five-minute task. Two days later, your abandoned cart flow stops firing and you can't figure out why. When you rename or merge a data field, any segment that references the old field name becomes orphaned. In most ESPs this fails silently, returning zero results or the wrong subscribers rather than throwing an error you'd actually notice.

Before changing any field, find out which segments reference it. Most platforms have a field usage view that lists dependencies. If yours doesn't, export your segment rules and search for the field name manually. Don't stop at segments: check your automations and flows too, since they often filter on the same field independently of your segment definitions. In Klaviyo, you'll need to check each flow's trigger and filter conditions separately from the segment list because they're stored independently.

The safe migration sequence is: create the new field first, backfill data for existing subscribers, update every segment rule and automation to point at the new field, verify your counts look right, and then retire the old field. If you're merging two fields into one, decide upfront which value wins when a subscriber has entries in both. Write that logic down before you run the backfill so you can explain it later if something looks off.

After any field migration, check your key data fields and spot-check a handful of subscriber records directly. A segment that normally holds 5,000 people suddenly showing 50 is the clearest signal that something's broken. Catching a broken reference the same day you made the change is far easier than tracing it back two weeks later when a campaign underperforms and you're not sure why.