--- name: navan-migration-deep-dive-ef5ec9a27d56 description: >- Migrate travel or expense data flows to Navan with staged cutover and financial and traveler reconciliation. Use when replacing a TMC, expense platform, card feed, or custom integration. Trigger with "migrate to Navan", "Navan cutover", or "replace travel platform". allowed-tools: Read,Glob,Grep,Write,Edit argument-hint: " " version: 1.9.0 license: MIT author: Jeremy Longshore tags: [saas, navan, migration] model: inherit effort: high compatibility: "Designed for Claude Code; live or external Navan actions require network access and explicit approval" --- # 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. ## Instructions 1. Inventory legacy workflows, data, owners, obligations, integrations, and open items. 2. Capture Navan tenant contracts and map concepts with loss and ambiguity labels. 3. Define historical migration, open-item transition, and future-state interfaces separately. 4. Rehearse with synthetic and approved bounded data. 5. Dual-run or shadow-process a controlled period and reconcile travelers, bookings, expenses, cards, and totals. 6. Cut over with freeze, communication, rollback, legacy retention, and decommission gates. ## Tool Discipline Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion. ## Approval Boundaries Historical data movement, traveler communication, policy conversion, card or payment change, production cutover, and legacy deletion require authorized owners. ## Error Handling - Do not manufacture missing legacy meaning. - Keep unresolved open items visible through cutover. - No legacy deletion before legal, finance, privacy, and rollback gates close. ## Output Return the concept map, data disposition, dual-run evidence, open-item register, cutover plan, rollback, and decommission record. Identify assumptions, owners, expirations, and evidence gaps explicitly. ## Examples - Move booking reporting while preserving legacy trip lineage. - Transition expense reconciliation without duplicating reimbursements. ## Validation Reconcile representative historical, open, cancelled, corrected, refunded, personal, and multi-currency cases. Record expected and observed results, including fail-closed behavior. ## Resources - [Current first-party evidence map](references/official-docs.md) — recheck dated sources and the selected tenant's in-account contract before relying on mutable endpoints, fields, entitlements, limits, or delivery behavior. - Record tenant observations as environment-specific evidence, never universal Navan guarantees. --- Source attribution: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/navan-pack/skills/navan-migration-deep-dive/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2025 Jeremy Longshore Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/navan-pack/skills/navan-migration-deep-dive/SKILL.md Attribution basis: Source repository record Fields of work: Operations, Product Management, Project & Program Management, Sales Roles: Business Development, Customer Success Manager, Operations Manager, Product Manager, Project Manager Specialties: API, Design, Word Documents, Frontend, Playwright, Testing Tools: Navan, Sap Concur Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 3d58012821a39df6fc591f5de7f15ae970e3e85920b76b4bf5aae77d7bce57bb