SAP Concur Migration Assessment — Know Before You Commit

A concur migration assessment is a structured discovery and sizing exercise that produces five deliverables: (1) a complete inventory of the source Concur tenant — every Custom Field, Audit Service rule, Workflow definition, Cognos report, Policy Configuration, corporate-card program and integration touchpoint; (2) a data-volume sizing — expense reports per fiscal year, receipt-image total size (typically multi-TB), corporate-card transaction count; (3) a complexity scoring across six dimensions (Custom Field count, audit-rule complexity, workflow depth, report library size, integration footprint, multi-tenant scope); (4) a target-state design for Oracle Fusion Expenses — DFF mapping, audit-rule retire/replace decisions, AMX workflow design, OTBI report rebuild plan; (5) a sized project plan with timeline, budget and risk register. Output goes directly into the migration project charter.

Most concur to oracle fusion migration projects that slip do so because the team underestimated one or more of: multi-TB receipt-image volume (impacts extract timeline by weeks), Audit Service rule complexity (impacts target-state design by months), corporate-card feed cutover coordination (impacts cutover schedule by 2–4 weeks per provider), or Cognos report library size (impacts OTBI rebuild scope by months). A 2–4 week concur migration assessment surfaces all four before the project starts — converting unknowns into knowns and letting the project plan be priced and timelined with confidence. Customers who skip the assessment typically take 1.5–2x longer to complete the migration.

2–4 weeks for a typical mid-large Concur tenant. Week 1: discovery automation runs against the Concur tenant via REST API v3/v4 — Custom Fields catalog, Audit Service rules, Workflow definitions, Cognos report metadata, integration touchpoint inventory. Week 2: data-volume sizing — full historical expense report counts, multi-TB receipt-image volume estimation, corporate-card transaction history. Week 3: complexity scoring and target-state design workshops with finance, T&E ops, compliance and integration leads. Week 4: project plan, budget, timeline and risk register prepared and presented. Larger or multi-tenant scenarios (M&A consolidations across 5+ legacy Concur tenants) typically run 4–6 weeks.

Six dimensions, each scored 1–5: (1) Custom Field count — fewer than 10 is low complexity, more than 50 is high; (2) Audit Service rule complexity — straightforward per-diem limits are low, sophisticated multi-condition policy logic is high; (3) Workflow depth — single-approver flows are low, multi-level delegated-authority chains are high; (4) Cognos report library size — fewer than 20 reports is low, more than 100 is high; (5) Integration footprint — HR feed only is low, HR + GL + AP + corporate-cards + travel + custom integrations is high; (6) Multi-tenant scope — single tenant is low, M&A consolidation across multiple tenants is high. Aggregate score drives timeline (low: 6–8 weeks, medium: 8–12 weeks, high: 12–16 weeks).

The integration mapping inventories every active integration into and out of the Concur tenant: HR feed (typically Workday, SuccessFactors, BambooHR, Oracle HCM or Sage People — providing the worker master to Concur); GL posting (typically SAP, Oracle EBS, Oracle Fusion, NetSuite, QuickBooks or Sage Intacct — receiving the journal entries from Concur); corporate-card feeds (Amex GBT, Visa Commercial, Mastercard SmartData, plus regional issuers); travel partners (Egencia, BCD, CWT, plus regional GDS connections); custom integrations (cost-center synchronisation, project-master sync, exception reporting). Each integration is mapped to its target-state equivalent in the Fusion architecture, with cutover sequencing and dependency analysis.

Yes. Data quality analysis runs across every domain: duplicate expense reports (same submitter, same date, same amount — often submission errors), orphan corporate-card transactions (no matching expense entry — often unused charges to refund), missing receipts (Audit Service rules historically flagged but submitter overrode — needs IRS Pub 463 review), unsubmitted reports older than 90 days (likely abandoned, candidates for cleanup before migration), expense entries with mismatched currencies (often FX-conversion errors), and approver-chain breaks (expense reports with terminated approvers — needs reassignment before migration). The data quality report flags cleanup candidates to address before extract — keeps the target Fusion data clean.

The assessment samples the Receipts API for image-size distribution, multiplies by total expense entry count, and produces a sized estimate (typically multi-TB; we have seen single tenants exceeding 40 TB across a decade of retention). The estimate drives three decisions: (1) extract timeline — multi-TB archives at the typical 200K–800K images per hour per worker pod throughput translate to 8–24 hours of streaming time; (2) target architecture — whether to load receipt images into Fusion's UCM attachment store or route to long-term cloud archive (cost trade-off); (3) compliance retention — which receipts retain in hot tier (current FY + prior FY), warm tier (2–4 yr back), cold tier (5+ yr back) per IRS Pub 463 and EU/UK VAT rules.

A standard concur migration assessment is typically delivered as a fixed-price engagement priced between $25K–$60K depending on scope — single-tenant single-module is lower, multi-tenant multi-module M&A consolidations are higher. Most customers find the assessment pays back in 5–10x value via avoided project overrun: a $40K assessment that surfaces a 6-week receipt-image extract window the team hadn't planned for saves $300K–$500K in delayed go-live cost. The assessment deliverables (inventory, sizing, complexity scoring, target-state design, project plan) are usable artifacts regardless of whether the customer chooses Syntra ETL or a different vendor for the migration execution.