How to Transfer Your SAP Concur Account When Switching TMCs

The reason most companies stay with a travel management company they've outgrown is a quiet fear: that leaving will break SAP Concur. Years of policy rules, approval chains, cost-center codes, and traveler profiles live inside that configuration, and the thought of rebuilding it from scratch is enough to make a Finance Director renew a contract they don't want to renew.

That fear is almost always misplaced. When you switch TMCs, you do not have to transfer SAP Concur by rebuilding it — in most cases the account itself stays exactly where it is. What changes is far smaller than the demo made it sound. This post explains what actually happens to your Concur configuration, history, and travelers when you change TMCs, and how the handover is done without a single traveler losing the ability to book.

In most cases, nothing happens to your SAP Concur account at all — it stays in place, and your new TMC is connected to it. Concur is the platform; the TMC is the travel agency that fulfills the bookings behind it. Switching one does not delete the other.

This is the single most important fact to understand before you change providers. Your company typically owns the Concur contract, or holds it through a partner who can reassign it. Your policy rules, approval workflows, cost-center structure, GDS connection, and travel history are attributes of that account, not of the TMC sitting behind it. The outgoing agency is unplugged and the new one is plugged in, usually without rebuilding anything the travelers see.

The first worry is configuration. Policy rules, approval hierarchies, cost centers, custom fields, and your negotiated-rate loads are stored in Concur's admin layer. When the account is transferred rather than rebuilt, those settings carry over intact, because they never belonged to the old TMC in the first place.

The second worry is history. Past itineraries, expense records, and reporting data stay attached to the Concur account, so your finance team keeps the audit trail it depends on. A TMC change does not wipe the ledger — it simply changes who books the next trip.

The third worry is travelers. Employee profiles, loyalty numbers, passport and known-traveler details, and saved preferences live in the Concur user records. Your people keep their logins and keep booking while the handover happens in the background. The disruption they notice is usually none at all.

A clean transfer follows a defined order, and the order is what keeps travelers booking the whole time. It starts with an audit: your new partner reviews the existing Concur configuration — policy rules, approval chains, cost-center mapping, custom fields, and negotiated-rate loads — so nothing is assumed and nothing is lost.

Next comes the agency reassignment. The TMC-of-record and the GDS fulfillment behind your Concur travel are repointed to the new agency, the ticketing queues are rebuilt on the new side, and the connection is tested with live itineraries before anyone relies on it. Only once bookings route correctly does the old agency connection get retired.

Throughout, traveler profiles and history are verified rather than recreated. The goal is a transfer where the configuration your company spent years tuning is confirmed working under new management, not an expensive rebuild dressed up as onboarding. Our how we work page walks through the sequence in full.

For a company that already runs Concur, the technical handover takes about a day — the agency connection is reassigned and tested while your existing configuration stays in place. A full new Concur build, for a company starting without one, takes three to four weeks from signed agreement to go-live.

The reason the transfer is so much faster than the build is that the hard work already exists. Your policy logic, approval chains, and traveler records are done; the transfer validates and repoints them rather than authoring them. Because travelers keep booking throughout, there is no freeze window and no day where your team can't book a trip. A dedicated account manager owns the timeline and the testing so the switch lands on a date you choose, not a date you dread.

Repointing a Concur connection is the easy part. The part that actually protects your program is having people who answer when a traveler or an approver hits a question during the change. A transfer that's handled by a ticket queue feels risky because no one owns it; a transfer handled by a named team feels routine because someone always picks up.

That is where a boutique TMC earns the switch. At Telios, five named agents handle your account and answer calls within three rings, email gets a first response within 30 minutes, and VIP travelers get a first response in nine minutes on average. One dedicated account manager owns the Concur handover end to end, so questions go to a person who knows your program — not a stranger reading your file for the first time. You can see how a managed corporate travel program is run day to day, and the case studies show the outcomes that follow.

Ask any prospective partner three direct questions. Are they an actual SAP Concur Travel Partner who can set up, transfer, and repair a Concur travel program — or do they only claim to work with it? Will your travelers keep booking during the handover, with no freeze window? And who, by name, owns the transfer if something needs fixing at 6pm on a Friday?

The answers separate a real transfer from a disruptive migration. Telios maintains a 93% Concur adoption rate across clients because the handover is done correctly and the service that follows keeps people inside the tool. And because there's no lock-in — no minimum spend and a 30-day cancellation — you're never trapped by the same fear that kept you from switching in the first place.

Your SAP Concur account is an asset you own, not a hostage held by your current TMC. Transferring it to a better partner is a one-day technical handover when it's done by people who do it for a living — and your travelers never stop booking. If you're ready to see exactly what your transfer would involve, Contact us for a straight review of your current Concur setup. No lock-in, no minimum spend.