SystemLoyalty & Customer Experience

Frequent Flyer Program Migration

Frequent flyer program migration that moves every mile and every level, with no member left behind

See one case, screen by screen ↓
Watch with transcript →

Built forLoyalty integration leadsProgram operations analystsMember services leadsLoyalty controllersFraud operations managers

The Problem Today

When two loyalty programs combine, integrators write match rules, pause redemptions for days and hand the leftovers to the call center.

5 days
members' miles were unavailable in one 2025 US merger published
19 days
of hand work to move one batch of member accounts our estimate

Records that never quite match

  • Emails
  • Nicknames
  • Addresses
  • Balances
  • Son merged into fatherSame name and street, a different birthday
  • Liability won't tie outPoints in and miles out, rebuilt by hand weeks later

The Solution

  1. Pairs found and scoredBirth date, phone, traveler number and name variants, with reasons
  2. “Two people” argued firstA second agent re-checks each match by flights flown and co-travelers
  3. Hard pairs as patternsUnsure pairs grouped by why they are hard, each pattern decided by a person
  4. Tied out, then signedLiability matches before and after; three people sign before it runs

Built-in controls

  • No level lowered, no consent widened
  • Accounts with last-minute contact changes held
  • Rules change only with a signature

What You Get

Members move at the signed rate with no level lowered, and the liability ties out before each batch runs.

  • Top-tier members at risk foundEach gets a proposed gesture, with its cost, to approve
  • A personal notice for eachEach member's before and after, in English or Spanish
  • Old numbers keep workingTrips, co-brand cards and partner numbers move too
In short

What is Frequent Flyer Program Migration?

Frequent flyer program migration is the work of moving members from one airline loyalty program into another after a merger: matching the same person across both programs, converting points to miles, carrying status, and moving trips, co-brand cards, partner numbers and consents. Frequent Flyer Program Migration does it with eight agents that match, check, convert and reconcile each account, while people decide the hard pairs and sign each batch, and any wrong merge can be undone.

How to choose AI for airlines: a buyer's guide to agentic AI solutions →

Updated

The problem

Where a frequent flyer program migration goes wrong after the cutover

A frequent flyer program migration is more than a balance transfer. When one airline buys another, millions of members hold an account in both programs under different emails, nicknames, married names and old addresses. Points have to become miles at the rate the airline promised, status has to land on a level that keeps its benefits, and award trips, co-brand cards, partner numbers and marketing consents have to follow the member. Today integrations run on match rules and one big-bang cutover: redemptions stop for days, and whatever the rules miss becomes a call-center problem.

The damage shows up after the move. A son's miles land in his father's account, and fixing it is a manual ledger rebuild. A member the match rules missed keeps two accounts, and the status earned in one is not recognized in the other. Points in and miles out do not tie, so the loyalty controller cannot close the quarter on the liability. And account thieves use the confusion: a contact change a few days before cutover is how a stranger claims a merged balance.

typical5daysa US program was unavailable to members during its 2025 move
typical7daysmembers' points were frozen in a 2018 US program merger
Where a batch's working days goestimated
By hand19 days
With the solution2.4 days
  • Matching members across the two programs3 → 0.2 d
  • Working the pairs the match rules are unsure of5 → 1 d
  • Converting balances and mapping status levels2 → 0.2 d
  • Tying points, miles and liability to the cent3 → 0.2 d
  • Writing and approving member notices2 → 0.3 d
  • Fixing wrong merges after members call4 → 0.5 d

Estimated split for one batch of a few hundred thousand accounts in a loyalty program merger, by hand and with the solution.

How it works

How frequent flyer accounts are matched, checked, converted and moved

What comes in
Two programs inBoth programs' members · records, ledgers, trips, cards, consents
Agents at work
Matching agentpairs and reasons
Then
Second-look agenttwo people first
Fraud watchholds recent changes
Then
Conversion and tier agentsto the point, no level lowered
Then
Notice agentbefore and after
Move agentsnapshot first
A person decides
Program teamdecides patterns, signs the batch
What comes out
One account per member
Every point reconciled
Any merge undone
One case, step by step

Batch seven of a frequent flyer migration, screen by screen

The airline bought another airline. The acquired program's 4,218,600 accounts move into the airline's own program, with its 18.6M accounts, in nine batches before the acquired program closes. Six batches have moved. Tonight is the seventh: 286,450 Silver and Gold accounts. Here is the day in the working solution.

A worked example on sample data. Names, IDs and figures on the screens and in this section come from the demo.

  1. 01The morning of the move

    Seven items need the manager; the agents did the rest overnight

    Loyalty integration manager

    The batch moves tonight, 11:00 pm to 3:00 am CT, with redemptions paused for 4 hours. So far 2,330,000 of 4,218,600 members have moved, 3,812 pairs need a person and 0 points are unaccounted for. Overnight: 61,920 pairs found at 1:30 am, 1,212 scores lowered by the second look, 37 pairs held by fraud watch, 286,450 notices written by 6:10 am. The manager asks what could go wrong tonight.

    Move agent: “The batch ties to the point. What is left is people’s work on the 3,812 hard pairs.”

  2. 02One member

    Two accounts side by side, and the one the member will have

    Matching agent

    One member holds a Blue account with 18,640 miles on the airline's side and a Silver account with 42,300 points on the acquired side. Between them sits the account after the move: 71,515 miles (18,640 + 42,300 × 1.25), Silver kept, 14,200 status points carried 1 : 1, an upcoming trip re-pointed and the co-brand card earning into it. Each value opens its source line.

    “One question: the member uses two emails. I kept the one on our side for sign-in and the other as second. Is that right?”

  3. 03Why 0.97

    The reasons for the score, and an agent that argues against it

    Matching agent and second-look agent

    In favor: the same Known Traveler Number (+0.31), the same date of birth (+0.22), the same mobile (+0.18), the same home once written the same way (+0.12). Against: two different emails (−0.03). Asked whether the member flew on both at once, the second-look agent checks the flight records.

    Second-look agent: “In 24 months the two accounts did not share a flight on any date… I tried to prove them two people and could not.”

  4. 04What the member will read

    A personal before-and-after notice, on the channel allowed

    Notice agent

    The notice is written for this member in English or Spanish: 42,300 points plus 18,640 miles become 71,515 miles, Silver stays Silver, and the trip and card move too. It goes by email only: texts were off on one account, and the stricter choice per channel is carried.

    “Your miles do not expire for 36 months. We will never ask for your password or your card number.”

  5. 05The hard pairs

    3,812 pairs as eight patterns instead of a grid of rows

    Program operations analyst

    The agents were unsure of 3,812 of the 61,920 pairs, so they grouped them by why they are hard: name variants and nicknames (1,606), married or changed surnames (612), shared email or phone (541), family at one address (388), one account matching two (297), names spelled two ways (214), status conflicts (117) and holds by fraud watch (37). Each carries a proposal and its risk. The analyst approved three; 2,606 pairs await a second signature.

  6. 06Second signature

    A father and son at one address stay apart

    Loyalty integration manager

    In the family pattern, two members share a name and a home address, were born in 1958 and 1986, and flew together side by side. The rule the agents propose for all 388: keep apart where date of birth or Known Traveler Number differ. The manager reads five samples across the range of scores, sees the 3 pairs pulled out to decide one by one, and signs as second.

    “The analyst approved this at 8:12 am as different people, same family. Your second signature puts 385 pairs in tonight’s batch.”

  7. 07Before the move

    Contact changes just before cutover are held

    Fraud operations manager

    214 accounts in the batch changed email or phone in the 14 days before the move. Fraud watch held 37 pairs and refused 9 link requests with a mismatched birth date. Five are left. On one, the email changed to a free-mail address created that day, the phone was removed 4 minutes later, and a link request came from a new device at 1:12 am. On another, the member called to confirm the change, so the agents propose release.

    Fraud watch holds only; the fraud operations manager releases or confirms each pair.

  8. 08Convert

    Each point accounted for, to the cent

    Conversion agent and loyalty controller

    9,738,412,652 points × 1.25 under the signed rate, rounded up to the whole mile per account, become 12,173,087,124 miles. Liability before, at 1.75¢ a point, is $170,422,221.41; after, at 1.40¢ a mile, the same, a $0.00 difference. The 71,309 rounding miles, $998.33, are booked as goodwill. The controller signed the liability at 8:05 am.

    “Each account carries its own line, so any member’s balance can be traced.”

  9. 09Signed

    Nothing moves until three people sign

    Integration manager and head of loyalty

    The sign-off lists what will run: 286,450 accounts, 57,108 merges, 224,530 new accounts, the reconciliation, the window and the snapshot taken before the first account moves. 875 pairs still open at 10:00 pm stay as two working accounts for the next batch. The integration manager signs with the reason batch reconciled, and the head of loyalty co-signs.

    “Snapshot first · rollback within 72 hours.”

  10. 10On the call

    A wrong merge, undone in one signed step

    Member services lead

    In the last batch a son was merged into his father's account: same name, same street, a different birth date. He is on the line. From that batch's snapshot the move agent has the undo ready: 41,250 miles and his upcoming trip go to a new account, with Silver restored. His father's four redemptions since used only his own miles, so nothing is clawed back. A personal letter and 5,000 miles of goodwill go with it.

    Merges undone to date: 41 of 486,212, or 0.84 in 10,000.

Who it’s for

Five roles in a frequent flyer program migration, before and after

The same batch from five seats: how the move ran by hand, and how it runs now.

Loyalty integration manager
Signs each batch
Before
Runs the migration plan from cutover runbooks and defect logs, and learns about a wrong merge when the member calls.
Now
Signs a batch only once each point is accounted for, with the hard pairs already decided as patterns.
Program operations analyst
Decides the hard pairs
Before
Works low-confidence pairs one row at a time from a match score, with no reason behind it.
Now
Sees why the agents think it is the same person, reads a pattern’s samples and decides hundreds of pairs in one signed step.
Member services lead
Handles calls about the move
Before
When a member reports landing in a parent’s account, opens a ticket and waits for a manual ledger rebuild.
Now
Undoes the merge on the call from its snapshot, with both ledgers restored, and approves the personal letter.
Head of loyalty
Signs the rules, co-signs batches
Before
Sets the conversion rate on an average and cannot see which member segments lose value.
Now
Signs the rules after a simulation shows no segment worse off, co-signs each batch and approves the retention gesture for top-tier members.
Loyalty controller
Signs the liability
Before
Rebuilds the loyalty liability by hand weeks after the load, when points in and miles out do not tie.
Now
Signs liability before equal to liability after, to the cent, for each batch before anything moves.
The agents

Matching, second-look and conversion agents for a frequent flyer migration

Eight agents match, check, convert and reconcile every account; people decide the hard pairs and sign each batch.

Matching agent

Finds candidate pairs across both programs by birth date, phone, email, Known Traveler Number, the address written the standard way and name variants, scores each with its reasons, and groups unsure pairs into patterns with a proposal.

  • Scores and explains; never merges
  • Reads both programs' member records read-only
Second-look agent

Re-checks each match by flights flown, seats on the same flight, co-travelers and booking devices, and argues “two people” first.

  • Can lower a score or keep a pair apart, with a reason
  • Cannot merge; a disagreement always goes to a person
Conversion agent

Converts points to miles under the signed rule, rounds per account and ties points in, miles out and liability before and after to the cent.

  • Uses only a signed rate
  • Never changes a balance outside a signed batch
Tier agent

Maps status levels, carries status points and status challenges, sums lifetime miles and applies the higher of the two levels.

  • Never lowers a level
  • Conflicts go to a person
Fraud watch

Watches contact changes, link requests and redemption spikes before the move, and holds pairs whose email or phone changed within 14 days.

  • Holds only; people release or confirm
  • Refuses a link request with a mismatched birth date
Notice agent

Writes each member's before-and-after notice in their language, 30 days before, on the day of the move and 14 days after, on channels on file and under the carried consents.

  • Approved templates only
  • Personal letters need Member Services
Retention agent

Finds top-tier members the merged network will serve less well and proposes a gesture with its cost.

  • Proposes only; the Head of Loyalty approves the budget
Move agent

Runs a signed batch in its window: creates merged accounts, keeps old numbers working as aliases, re-points trips, co-brand cards and partner numbers, and keeps a snapshot for undo.

  • Signed batches only, inside the window
  • Undo and rollback need people
Integration Manager and Head of Loyalty

Own the rules, sign every batch.

Ask in plain words

Questions put to the migration agents about a pair, a rate or a rollback

The agent responsible for each screen leads with what it found; people ask back or instruct in plain words, and each answer cites its record. These answers use the sample data.

Did this member ever fly on both at once?

No. In 24 months the two accounts did not share a flight on any date, and each seat was one passenger with the same name. One iPhone signs in to both accounts. I tried to prove them two people and could not.

Is anyone worse off after the move?

No segment loses value: at 1 : 1.25 a point worth 1.75¢ becomes 1.25 miles worth 1.40¢ each, so 1.75¢ in value either way, and no level goes down. The rounding adds 71,309 miles, $998.33.

What would 1 : 1 do?

Each member of the acquired program would lose 20% of the value of their points: a typical Gold balance of 52,210 points worth $913.68 would become miles worth $730.94.

Can we roll this back?

Yes. The batch snapshot is taken before the first account moves. For 72 hours the whole batch can be rolled back with two signatures; after that, any single merge can still be undone.

The screens

Merge frequent flyer accounts: pairs, patterns, the liability and the undo

From the working solution, on its sample data. Pick one to see it large.

TodayThe integration manager's day in a frequent flyer program migration: tonight's batch, members moved, hard pairs, points accounted for and the agents' night.
Two accounts, one memberMerge frequent flyer accounts side by side: both records, the merged account between them with points converted and status kept, and the agents.
Why the agents matched themThe match score for and against, each signal cited, and the second-look agent's check of flights, seats and devices.
The member's noticeA personal notice of the points conversion and status after the merger, in English or Spanish, on the channel the member allows.
Hard pairs as patternsDuplicate member accounts the agents were unsure of, in eight patterns with a proposal, risk, samples and who decided.
One pattern, its samplesFamily members at one address: why the agents grouped them, the rule they propose, five samples to read and the second signature.
Fraud during the mergeContact changes in the 14 days before cutover, pairs held by fraud watch, refused link requests, and release or confirm.
Loyalty liability reconciliationPoints in, miles out, rounding and the loyalty liability before and after, tied to the cent and signed by the controller.
Approve and sign the batchWhat the loyalty program cutover will run, the snapshot, rollback window, reason code and signer, then the co-signer.
Undo and rollbackA wrong merge undone in one signed step from its snapshot, both ledgers restored, and each batch snapshot with its rollback window.
Members at risk of leavingGold members the merged network will serve less well, with the proposed gesture and its cost for approval.
The rules people ownSigned conversion, level, threshold, fraud and consent rules, and the simulation showing no member segment worse off.
Audit trailEach agent action and each decision with its reason code and source, kept seven years, with the evidence pack export.
Governance

Signatures, snapshots and the audit trail behind each migration batch

Each value cites its sourceEach merged value and agent statement opens its source line in either program: the member record, the ledger, the flight history, the signed rule.
Three people sign each batchNothing moves until the Integration Manager signs and the Head of Loyalty co-signs, with the liability signed by the Loyalty Controller. No one signs twice.
Hard pairs go to a personPairs scored from 0.70 to 0.95, each second-look disagreement and each fraud hold go to a person, and each decision carries a reason code such as name variant or different people, same family.
No level lowered, no consent widenedStatus maps to the higher of the two levels and does not go down. Marketing consent carries the stricter choice per channel, and members are told only on channels on file.
Rules change only with a signatureThe agents work only under signed rules. A change to the rate, levels, thresholds, fraud holds or consent is simulated on each member segment first, then signed.
Undoable, and on the recordEach merge keeps a snapshot, so an undo restores both ledgers. The audit trail is append-only and kept seven years, with an evidence pack per member for a complaint or an auditor.
Configuration

Conversion rate, level map and match thresholds the loyalty team signs

The rate, the level map and the thresholds the agents work under are signed rules. A change is simulated on each member segment, replayed on a past batch and signed by the Head of Loyalty.

SettingDefaultChoose from
Conversion (R-1)1 acquired-program point = 1.25 miles, rounded up per accountAny rate can be tried in the simulation; the agents will not run a batch under a rate that devalues points
Status levels (R-2)Member → Blue · Silver → Silver · Gold → Gold · Sapphire → Platinum; the higher winsValid to a set date; status points carried 1 : 1; lifetime miles summed
Merges after sign-off at or above0.95Any score · replayed on the last batch first, then signed
A person decides from0.70Any score · below it, pairs are kept apart; a second-look disagreement always goes to a person
Hold a pair if contact changed within14 daysAny number of days · a link request with a mismatched birth date is refused
Largest batch · redemption pause1,100,000 accounts · 4 hours at mostWindow 11:00 pm – 3:00 am CT; pairs still open at 10:00 pm wait for the next batch
Whole-batch rollback window72 hoursTwo signatures to roll back; a single merge can be undone at any time
Member notices30 days before · the day · 14 days afterEnglish and Spanish; miles do not expire for 36 months after the move
Connections

Loyalty platforms, reservations, co-brand cards and the general ledger

Both loyalty platformsmembers, ledgers and levels; the acquired program read-only, yours written only in a signed batch
Reservationsupcoming trips and award bookings of both airlines, re-pointed in the window
Co-brand card partner filecard links sent out before the window and confirmed after it
Partner ID exchangehotel and car partner numbers that follow the member
Consent store and message servicemarketing and text consents of both programs; email and text on channels on file
General ledgerthe loyalty liability, read-only, tied before and after each batch
What it changes

Redemption pauses and undone merges in a frequent flyer program migration

Each figure carries its label: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
0
points unaccounted for and levels lowered in any batch
Big-bang loadtied out weeks later
With the agentsto the point, before sign-off
target
1in 10,000
or fewer merges undone, each in one signed step
under 1 in 10,000
both ledgers restored
target
4h
redemption pause per batch, against 5–7 days in past US mergers
Past mergers5–7 days
With the agents4 hours

“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate, the hand work on one sample batch split by step · “typical” = published figures (HawaiianMiles unavailable Sep 26–30, 2025, reported by KOMO; Virgin America Elevate frozen Feb 1–7, 2018, reported by One Mile at a Time; DOT conditions on the 2024 Alaska–Hawaiian merger, 1:1 conversion or better, no devaluation, status matched or raised). Names on the screens are sample data.

Questions

Frequent flyer program migration questions from loyalty and finance teams

What is frequent flyer program migration?

Frequent flyer program migration is the work of moving members from one airline loyalty program into another after a merger: matching the same person across both programs, converting points to miles, carrying status, and moving trips, co-brand cards, partner numbers and consents. Frequent Flyer Program Migration does it with eight agents that match, check, convert and reconcile each account, while people decide the hard pairs and sign each batch, and any wrong merge can be undone.

How do you merge frequent flyer accounts after an airline merger?

To combine frequent flyer accounts, the matching agent finds pairs by birth date, phone, email, Known Traveler Number and address, and scores each with reasons. A second-look agent re-checks each against flights, seats and devices. Pairs at 0.95 or above merge after the batch is signed; pairs from 0.70 to 0.95 go to a person as patterns with samples, and below 0.70 they are kept apart.

What happens to points and status when two loyalty programs merge?

Points conversion after a merger follows the rate the Head of Loyalty signs (1 point to 1.25 miles in the working solution, rounded up per account) once a simulation shows no segment worse off. For the status match after a merger, each member gets the higher of their two levels; status points carry over and lifetime miles are summed. Each member gets a personal before-and-after notice.

How do you avoid merging the wrong accounts, like a father and son?

Pairs the agents are unsure of are grouped into patterns such as family at one address, shared email or phone, and married or changed surnames. Each pattern has a proposed rule (for families, keep apart where date of birth or Known Traveler Number differ) and samples a person reads before deciding. Any pair can be decided on its own.

Can a wrong merge be undone?

Yes. Loyalty account consolidation here is not one-way: each merge keeps a snapshot, so Member Services can undo one in a signed step, both ledgers restored, with the member on the call. A whole batch can be rolled back with two signatures for 72 hours after it moves.

How do you stop fraud during a loyalty program merger?

Fraud watch holds any pair whose email or phone changed in the 14 days before the move, and refuses link requests whose birth date does not match. It only holds: a held pair does not move until the fraud operations manager releases or confirms it.

Who signs off before any balance or level changes?

The agents propose, explain and prepare; they do not change a rule, lower a level or move a balance outside a signed batch. The integration manager and the head of loyalty sign each batch, the loyalty controller signs the liability, and each decision is on an append-only audit trail kept seven years.

Can we see the matches on our own members before anything moves?

Yes. The Agentic Solution Engine builds and deploys it from your conversion and level rules, both programs’ records and the systems around them, and it goes live once each quality gate has passed. Setup includes a read-only dry run of the loyalty member data migration on 1% of the acquired program, so the pairs and patterns are visible first.

Dry-run your own two programs
before a single account moves.

We'll run Frequent Flyer Program Migration on a 1% dry run of your own two programs.