SAP Concur Migration Checklist — 60+ Items, Owner-Assigned

A complete concur migration checklist covers six work-streams: (1) tenant inventory — Custom Fields, Audit Rules, Workflow definitions, Cognos reports, Policy configurations, integrations to corporate cards and travel; (2) receipt-image archive — volume estimate, retention windows, storage path; (3) corporate-card feed re-cutover — Amex GBT, Visa, Mastercard cutoff dates and provider coordination; (4) in-flight expense handling — open reports, pending approvals, unsubmitted reports; (5) Fusion-side foundation — enterprise structures, ledgers, BUs, COA, expense templates, AMX approval rules; (6) compliance evidence — IRS Pub 463 7-year substantiation, SOX trace, EU/UK VAT recovery continuity. Syntra ETL's concur migration checklist runs to 60+ specific items grouped under those streams, with an owner column and a target-date column ready to drop into Smartsheet, Asana or a printable PDF.

Six months ahead for global, multi-entity programmes; three months ahead for single-entity, US-only Concur Expense migrations. The driver isn't the technical extract — that's 6–10 weeks for any scope. The driver is the corporate-card feed re-cutover (8–12 weeks lead time with Amex GBT, 4–6 with Visa/Mastercard), the Fusion Expense FSM setup (4–6 weeks if greenfield), the AMX approval workflow design and the VAT recovery filing window. Starting the concur migration checklist six months out lets the long-lead items (card feed cutover, vendor master cleansing, expense type rationalization) run in parallel with the Fusion build-out instead of becoming critical-path blockers in week 8 of a 12-week project.

Yes — receipt-image planning is one of the largest line items because the volume is so substantial. The concur migration checklist requires a receipt-image inventory in week 1: estimated total volume in TB (typically multi-TB, with some single tenants exceeding 40 TB across 10 years), file-type distribution (JPG/PNG/PDF), oldest receipt date (drives retention window calculation against IRS Pub 463's 7-year minimum), and target destination decision (Fusion attachments for current+prior FY, long-term archive for older). The checklist then sequences the image streaming through Concur's Receipts API in parallel passes — bulk pass for historical, delta passes during parallel-run, final pass during cutover weekend.

In-flight expense reports — submitted but not yet paid, pending approval, or returned for revision — are the single most common cutover risk. The concur migration checklist mandates a freeze on new expense submissions in Concur 48–72 hours before cutover, with a sweep of every in-flight report categorized: 'submitted, awaiting approval' migrate to Fusion with approval state and approver chain intact (via AMX); 'returned to user' get cancelled and re-filed in Fusion post-cutover; 'paid but not reimbursed' close on the Concur side with the reimbursement payment file routed to Fusion Payables. Each category gets a count, an owner and a target-cleared timestamp on the checklist.

Corporate-card feed cutover is on the concur migration checklist as a 4–6 week sub-project with its own gantt. Sequence: (1) confirm card-program inventory — issuer, BIN ranges, currencies, settlement entity; (2) request cutoff date from card provider (Amex GBT typically requires 8 weeks notice for a global program, Visa/Mastercard 4–6); (3) configure Fusion corporate-card setup — program, BIN ranges, MCC mapping, posting-account rules; (4) process last Concur card file, reconcile to provider statement; (5) cut feed to Fusion at provider level; (6) parallel reconciliation period (2–3 weeks) where late-posting transactions are caught manually. Each step is on the checklist with a provider-contact, an SLA and a roll-back trigger.

Audit Rules and Workflow definitions are treated as a separate work-stream on the concur migration checklist because they don't translate 1:1 to Fusion. Step 1: export the Concur Audit Service rule registry and Workflow definitions via the Admin APIs (output: machine-readable JSON, not screenshots). Step 2: classify every rule by business purpose — mileage limit, per-diem cap, alcohol policy, executive approval threshold, etc. Step 3: decide retire/replace per rule — typically 30–50% retire because Fusion's native policy engine subsumes them. Step 4: implement Fusion-native equivalents in Fusion Expense Audit Rules, AMX flows or BI Publisher exception reports. Step 5: parallel-test the new rules against historical Concur violation data to confirm coverage. The checklist tracks every rule's status from 'inventoried' through 'retired' or 'live in Fusion'.

The concur migration checklist's compliance work-stream covers four regimes. IRS Pub 463: 7-year retention of receipt images and expense substantiation, signed-and-timestamped read-access logs. SOX: auditable trace from GL journal line → Fusion Expense Distribution → Expense Entry → original receipt image, with hash signatures preserved across the migration. EU VAT Directive (and UK HMRC): 6-year retention of receipt images supporting VAT reclaim, gross/net/tax breakdowns preserved, vendor VAT registration carried over. FCPA / Anti-Bribery (ABAC): gifts, entertainment and government-official expense flags preserved with full approval-chain context. Each regime has a verification step on the checklist with the named owner (internal audit, tax ops, compliance officer) and the evidence document path.

Yes. Expense-only migrations drop the Travel work-stream (itinerary migration, online booking tool decommissioning, agency-fee reconciliation, unused-ticket tracking) and the Invoice work-stream (Concur Invoice → Fusion Payables, three-way match history, vendor master consolidation). What remains is the Expense work-stream — which is typically 70–80% of the checklist items anyway. Full-scope migrations also add the cross-module sequencing items: Travel itineraries need to land before related expense reports so the air/hotel/car segment context is available for matching; Concur Invoice needs to land before the related approval workflows are remapped to Fusion AMX. The Syntra ETL concur migration checklist comes in three variants — Expense-only, Expense + Invoice, and full scope — picked from at project kick-off.