Navan Platform Migration Reconciliation

Overview

Migrate travel or expense data flows to Navan with staged cutover and financial and traveler reconciliation. This workflow produces an auditable decision or artifact before any live action.

Prerequisites

• Access to the selected tenant's current Navan Help Center and contracted integration documentation.
• A named business owner and data owner for the travel or expense workflow.
• A non-production evidence set with secrets and traveler data removed.

Current Contract

Migration must reconcile legacy and Navan concepts rather than forcing field-for-field equivalence. Booking lifecycle, traveler profile, policy, card, expense, receipt, currency, approval, and accounting meanings require explicit mapping.

Authentication

Use separate migration identities and time-bound access. Avoid copying legacy secrets, personal data, or administrator privileges into steady-state integration accounts.