Frequent flyer program migration that moves every mile and every level, with no member left behind
Every mile and every level moves, with no member left behind, and any wrong merge undone.
See one case, screen by screen ↓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 every 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
A frequent flyer program migration is not 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. Each member's points have to become miles at the rate the airline promised, their status has to land on a level that keeps their benefits, and upcoming award trips, co-brand cards, partner numbers and marketing consents all have to follow them. Today integrators write match rules, run a big-bang cutover, pause redemptions for days and leave the leftovers to the call center.
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.
Estimated split for one batch of a few hundred thousand accounts in a loyalty program merger, by hand and with the solution.
Eight agents match, check, convert and reconcile every account; people decide the hard pairs and sign each batch.
Corvane Airways bought Solenne Air. The 4,218,600 Solenne Club accounts move into Corvane Waypoint, with its 18.6M accounts, in nine batches before Solenne Club closes on Feb 1, 2027. Six batches have moved. Tonight is Batch 7: 286,450 Silver and Gold accounts. Here is the day, screen by screen, in the working solution.
Batch 7 moves tonight, 11:00 pm to 3:00 am CT, with redemptions paused for 4 hours. Her home screen shows 2,330,000 of 4,218,600 members moved so far, 3,812 pairs that need a person and 0 points not accounted for. Under it sits the night's work: 61,920 pairs found at 1:30 am, 1,212 scores lowered by the second look, 37 pairs held by fraud watch and 286,450 notices written by 6:10 am. She asks the agents what could go wrong tonight.
Move agent: “Batch 7 ties to the point. What is left is people's work on the 3,812 hard pairs.”
Maria Delgado holds Waypoint 4400 2318 (Blue, 18,640 miles) and Solenne Club SC 7781 0452 (Silver, 42,300 points). In the middle is her account after the move, field by field: 71,515 miles (18,640 + 42,300 × 1.25), Silver through Jan 31, 2028, 14,200 status points carried 1 : 1, her Nov 6 DEN–SFO trip re-pointed and her co-brand card ending 3390 earning into Waypoint from Oct 17. Every value opens the line it came from.
“One question: she uses two emails. I kept the Waypoint one for sign-in and the Solenne one as second. Is that right?”
The score is broken down for and against: the same Known Traveler Number ending 4471 (+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 she ever flew on both at once, the second-look agent answers from the flight records.
Second-look agent: “In 24 months the two accounts were never on the same flight on the same date… I tried to prove them two people and could not.”
Maria's notice is written for her, in English or Spanish: 42,300 Solenne points plus 18,640 Waypoint miles become 71,515 miles, Silver stays Silver through Jan 31, 2028, and her trip and card move with her. It goes by email only, because she turned texts 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.”
The agents were not sure 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 pattern carries a proposal and its risk. Tom has approved three; 2,606 pairs wait for Rachel's second signature.
In the family pattern, Robert Hale born Apr 2, 1958 and ROBERT HALE born Apr 2, 1986 share a name and a Boise address, 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. Rachel reads five samples chosen to cover the range of scores, sees the 3 pairs the agents pulled out to decide one by one, and signs as second.
“Tom Brennan approved this at 8:12 am · DIFFERENT-PEOPLE-FAMILY. Your second signature puts 385 pairs in tonight's batch.”
214 Solenne accounts in Batch 7 changed email or phone in the 14 days before the move. Fraud watch held 37 pairs and refused 9 link requests whose birth date did not match. Claire has 5 left: Victor Hensley's email changed to a free-mail address created that day, his phone was removed 4 minutes later, and a link request came from a new device at 1:12 am. Neil Ashby called and confirmed his own change, so the agents propose release.
Fraud watch holds only; Claire releases or confirms each pair.
9,738,412,652 Solenne points × 1.25 under rule R-1, rounded up to the whole mile per account, become 12,173,087,124 Waypoint 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. Greg signed the liability at 8:05 am.
“Every account carries its own line, so any member's balance can be traced.”
The sign-off lists what will run: 286,450 accounts, 57,108 merges and 224,530 new accounts, the reconciliation, the window and snapshot S-07, taken before the first account moves. 875 pairs still open at 10:00 pm stay as two working accounts and join Batch 8. Rachel signs with the reason BATCH-RECONCILED, and Daniel Kerr, President of Corvane Waypoint, co-signs.
“Snapshot S-07 first · rollback within 72 hours.”
Robert Hale Jr. of Spokane was merged into his father's account in Batch 6: same name, same street, different birth date. Keisha has him on the line. From snapshot S-06 the move agent has the undo ready: 41,250 miles and his Dec 3 trip go to a new account, 4400 9958, with Silver restored. His father's four redemptions since Sep 30 used only his own miles, so there is nothing to claw back. A personal letter and 5,000 miles of goodwill go with it.
Merges undone to date: 41 of 486,212 — 0.84 in 10,000.
The same batch, seen by five people at Corvane Waypoint — what the move looked like before, and what it looks like now.
Eight agents match, check, convert and reconcile every account; people decide the hard pairs and sign each batch.
Finds candidate pairs across both programs — birth date, phone, email, Known Traveler Number, the address written the standard way, name variants — scores each with its reasons, and groups the pairs it is unsure of into patterns with a proposal.
Re-checks every match another way — flights flown, seats on the same flight, co-travelers, booking devices — and argues “two people” first.
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.
Maps status levels, carries status points and status challenges, sums lifetime miles and applies the higher of the two levels.
Watches contact changes, link requests and redemption spikes before the move, and holds pairs whose email or phone changed within 14 days.
Writes each member's before-and-after notice in their language — 30 days before, the day of the move and 14 days after — on channels on file, under the carried consents.
Finds top-tier members the merged network will serve less well and proposes a gesture with its cost.
Runs a signed batch in its window: creates merged accounts, keeps the old numbers working as aliases, re-points trips, co-brand cards and partner numbers, and keeps a snapshot for undo.
Own the rules, sign every batch. The agents propose; a named person decides.
Every screen has the agents beside the work. The responsible agent leads with what it found; you ask back or instruct in plain words, and every answer cites the record it came from.
Did she ever fly on both at once?
No. In 24 months the two accounts were never on the same flight on the same date, and every seat was one passenger, DELGADO/MARIA. 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 Solenne 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?
Every Solenne member 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. Snapshot S-07 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.
13 screens from the working solution, on its sample data. Pick one to see it large.
The rate, the level map and the thresholds the agents work under are signed rules. A change is simulated on every member segment, replayed on a past batch and signed by the Head of Loyalty.
| Setting | Default | Choose from |
|---|---|---|
| Conversion (R-1) | 1 Solenne point = 1.25 Waypoint miles, rounded up per account | Any 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 wins | Valid to Jan 31, 2028; status points carried 1 : 1; lifetime miles summed |
| Merges after sign-off at or above | 0.95 | Any score · replayed on Batch 6 first, then signed |
| A person decides from | 0.70 | Any score · below it, pairs are kept apart; a second-look disagreement always goes to a person |
| Hold a pair if contact changed within | 14 days | Any number of days · a link request with a mismatched birth date is refused |
| Largest batch · redemption pause | 1,100,000 accounts · 4 hours at most | Window 11:00 pm – 3:00 am CT; pairs still open at 10:00 pm wait for the next batch |
| Whole-batch rollback window | 72 hours | Two signatures to roll back; a single merge can be undone at any time |
| Member notices | 30 days before · the day · 14 days after | English and Spanish; miles do not expire for 36 months after the move |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “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). Corvane Airways, Solenne Air, their programs and the people named on this page are fictional — characters and sample data in the working solution.
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 every account, while people decide the hard pairs and sign each batch, and any wrong merge can be undone.
To combine frequent flyer accounts, the matching agent finds pairs across both programs by birth date, phone, email, Known Traveler Number and address, and scores each with its reasons. A second-look agent re-checks every match 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.
Points conversion after a merger follows the rate your Head of Loyalty signs — 1 point to 1.25 miles in the working solution, rounded up per account — after a simulation shows no member segment worse off. For the status match after a merger, each member gets the higher of their two levels and never a lower one; status points carry over and lifetime miles are summed. Each member gets a personal before-and-after notice.
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 comes with 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 pulled out and decided on its own.
Yes. Loyalty account consolidation here is never one-way: every merge keeps a snapshot, so Member Services can undo one in one signed step with both ledgers restored, even while the member is on the call. A whole batch can be rolled back with two signatures for 72 hours after it moves.
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: the fraud operations manager releases or confirms each pair, and a held pair does not move until she does.
Yes. The agents propose, explain and prepare; they never 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 every decision is on an append-only audit trail kept seven years.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your conversion and level rules, both programs' records and the systems around them — and it goes live once every quality gate has passed. Setup includes a read-only dry run of the loyalty member data migration on 1% of the acquired program, so you see the pairs and patterns before anything moves.
Stolen miles stopped before the award is flown, and honest members never locked out.
1-min demoMissing Miles Claims ProcessingMissing miles credited in minutes, each one tied to the flown coupon and its record.
1-min demoLoyalty Partner Billing ReconciliationEvery partner statement tied out line by line, every missed mile billed or credited.
1-min demoWe'll run Frequent Flyer Program Migration on a 1% dry run of your own two programs.