AI SummaryEnd-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. 1. Configure SCIM connector in your IdP (Okta, Azure AD) 2. Map IdP groups to Navan r
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "navan-migration-deep-dive" skill in my project. Please run this command in my terminal: # Install skill into your project (2 files) mkdir -p .claude/skills/navan-migration-deep-dive && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/navan-migration-deep-dive/SKILL.md "https://raw.githubusercontent.com/jeremylongshore/claude-code-plugins-plus-skills/main/plugins/saas-packs/navan-pack/skills/navan-migration-deep-dive/SKILL.md" && mkdir -p .claude/skills/navan-migration-deep-dive/references && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/navan-migration-deep-dive/references/one-pager.md "https://raw.githubusercontent.com/jeremylongshore/claude-code-plugins-plus-skills/main/plugins/saas-packs/navan-pack/skills/navan-migration-deep-dive/references/one-pager.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Use when planning or executing a migration from SAP Concur or legacy TMC to Navan — data migration, user provisioning, policy recreation, and cutover planning. Trigger with "navan migration deep dive" or "migrate to navan from concur".
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
Examples
Quick migration readiness assessment: `bash
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 integrations | Navan card program or integration | New setup | Key decision: historical data strategy. Navan does not support importing historical booking or expense data. Export source system data to a data warehouse or archive storage for reference. Future Navan data starts fresh from migration day.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster