Migration
A Concur migration can fail in two opposite ways.
The first is underestimating the work: policies, cost centers, cards, approval chains, ERP mappings, historical data, TMC configuration, and traveler profiles all have to land somewhere. The second is recreating every old workflow simply because it already exists.
If you are going to absorb migration cost, use it to decide what the new program should actually feel like — especially now that AI can change how people interact with travel and expense.
Concur is changing quickly. Joule now supports conversational travel and expense workflows, Microsoft 365 integrations, and AI-assisted trip management.
If your migration case was written around “Concur cannot do conversational AI,” re-test that assumption.
Leave because the operating model no longer fits — not because the old slide deck is stale.
A traditional migration asks: where does this screen go in the new system? A better 2026 migration asks: does the user need this screen at all?
If a traveler can ask a policy-aware assistant, if an AI agent can match a receipt, if an approval can route automatically, or if a digital human can help someone navigate an unfamiliar process, the replacement does not need to reproduce every click from Concur.
At ITS, that is the role of AI Chat, Bob and Ana, and background agents: reduce the amount of interface people have to learn while keeping policy and audit underneath.
Most migration timelines are really data-quality timelines. Entity names, cost centers, approvers, traveler profiles, and card mappings have to agree before a new platform can automate them reliably.
ERP, HRIS, cards, identity, and TMC data all have dependencies. The more custom the current Concur environment, the more discovery matters.
People know how to survive Concur. Even a “better” experience creates change. Training, communications, pilot groups, and support still matter.
Unused tickets, open expense reports, pending approvals, existing trips, and historical audit data do not disappear on cutover day.
The hardest cost to see is carrying forward ten years of policy exceptions because nobody wants to reopen the decision.
Name the manual processes the new platform is supposed to eliminate.
Ask about read, recommend, act, approve, and escalate separately.
A migration is not complete if booking moved but service stayed fragmented.
Define what migrates, what remains read-only, and how auditors access it.
A serious implementation should know how the organization functions if one integration is late.
FAQ
There is no honest universal answer. A simple domestic program can move much faster than a multinational environment with custom SAP integrations, multiple entities, tax requirements, and several TMCs.
Yes. In some organizations that reduces risk. In others it preserves the exact fragmentation they are trying to eliminate. Decide based on workflow, not vendor packaging.
Usually only what you need for audit, reporting, legal retention, and operational continuity. Moving everything into the new transactional system can add cost without adding value.
It can reduce user training and some ongoing manual work, but it does not fix bad master data or unclear policy. Agentic workflows make clean identity, permissions, and source-of-truth decisions more important, not less.
Treating the new platform as a prettier place to recreate the old workflow.
Not the RFP. Show us what Concur touches today and the workflow you never want to rebuild. That is where the migration should start.
Migration guidance reflects common SAP Concur replacement patterns and current public Concur capabilities reviewed August 2026. Actual migration scope depends on customer configuration, SAP/ERP environment, TMC model, data retention needs, card program, and regional requirements.