navan-migration-deep-dive

# Navan Migration Deep Dive ## Overview End-to-end migration playbook for moving from SAP Concur or legacy travel management systems to Navan. Navan uses REST APIs with OAuth 2.0 — there is no SDK, no automated migration tool, and no sandbox for testing. ## Prerequisites - Admin access to both source system (SAP Concur, legacy TMC) and Navan - Navan OAuth credentials from Admin > Travel admin > Settings > Integrations - Data export from source system (expense reports, itineraries, user directory) - SSO identity provider (Okta, Azure AD, Google Workspace) for user provisioning - Executive sponsor and travel program manager identified ## Instructions ### Phase 1 — Discovery and Planning (Weeks 1-2) **Inventory current state:** | Data Category | SAP Concur Source | Navan Target | Migration Method | |---------------|-------------------|--------------|-----------------| | User profiles | Concur user export (CSV) | SCIM provisioning or `/get_users` API | IdP-driven | | Travel policies | Concur policy rules | Navan admin console | Manual recreation | | Expense categories | Concur expense types | Navan expense categories | Mapping table | | Historical bookings | Concur trip export | Archive only (not imported) | Export + cold storage | | Historical expenses | Concur expense reports | Archive only (not imported) | Export + cold storage | | Approval workflows | Concur approval chains | Navan approval policies | Manual recreation | | Corporate card feeds | Concur card integratio...