From navan-pack
Guides end-to-end migration from SAP Concur or legacy TMCs to Navan: data inventory, SCIM/CSV user provisioning, policy recreation, API verification, and cutover planning.
How this skill is triggered — by the user, by Claude, or both
Slash command
/navan-pack:navan-migration-deep-diveThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
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.
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.
Option A — SCIM provisioning (recommended):
Option B — CSV bulk upload:
Verify provisioned users via API:
TOKEN=$(curl -s -X POST "https://api.navan.com/ta-auth/oauth/token" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "grant_type=client_credentials&client_id=$NAVAN_CLIENT_ID&client_secret=$NAVAN_CLIENT_SECRET" \
| jq -r '.access_token')
# Count provisioned users
curl -s -H "Authorization: Bearer $TOKEN" \
"https://api.navan.com/v1/users" \
| jq '{total: (.data | length), sample: [.data[:3][] | {email, status}]}'
Recreate travel policies in Navan admin console. Key policy areas:
SAP Concur policy mapping pitfalls:
Run both systems simultaneously to validate the migration:
| Activity | Source System | Navan | Duration |
|---|---|---|---|
| New bookings | Disabled for pilot group | Active for pilot group | 2 weeks |
| Expense submission | Active (all users) | Active (pilot group) | 2 weeks |
| Approval workflows | Active | Tested with pilot | 2 weeks |
| Reporting | Primary | Validated against source | 2 weeks |
# Monitor booking volume in Navan during parallel run
curl -s -H "Authorization: Bearer $TOKEN" \
"https://api.navan.com/v1/bookings?page=0&size=50&createdFrom=$(date -d '7 days ago' +%Y-%m-%d)" \
| jq '{total_bookings: (.data | length)}'
Reconciliation checks:
Go/no-go checklist (all must pass):
Cutover steps:
| Issue | Impact | Resolution |
|---|---|---|
| SCIM provisioning fails | Users cannot access Navan | Fall back to CSV upload; check IdP connector logs |
| SSO login fails | Users locked out | Verify SAML metadata; test with Navan admin account |
| Policy mismatch | Out-of-policy bookings approved | Audit first 50 bookings; adjust policy rules |
API returns 403 on /get_users | Cannot verify provisioning | Confirm API integration enabled in Admin > Integrations |
| Data sync not running | No reporting data | Check Fivetran/Airbyte connector status and credentials |
Quick migration readiness assessment:
# Verify Navan API access and user count
echo "=== Migration Readiness Check ==="
TOKEN=$(curl -s -X POST "https://api.navan.com/ta-auth/oauth/token" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "grant_type=client_credentials&client_id=$NAVAN_CLIENT_ID&client_secret=$NAVAN_CLIENT_SECRET" \
| jq -r '.access_token')
echo "API Auth: $([ -n "$TOKEN" ] && echo 'OK' || echo 'FAILED')"
USERS=$(curl -s -H "Authorization: Bearer $TOKEN" \
"https://api.navan.com/v1/users" | jq '.data | length')
echo "Provisioned users: $USERS"
BOOKINGS=$(curl -s -H "Authorization: Bearer $TOKEN" \
"https://api.navan.com/v1/bookings?page=0&size=50" | jq '.data | length')
echo "Total bookings: $BOOKINGS"
navan-install-auth to set up OAuth credentials for the migrationnavan-prod-checklist before cutover to validate production readinessnavan-data-sync to configure Fivetran/Airbyte data pipelinesnpx claudepluginhub jeremylongshore/claude-code-plugins-plus-skills --plugin navan-packProvides production reference architecture for Navan API integrations: API gateway, OAuth token management with Redis cache, REST client, data sync pipelines, ERP connectors, monitoring stack.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.