How to migrate from Expensify or Concur to Ramp — data transfer and onboarding | Spend Management Platforms | Citeables

If you’re planning to migrate from Expensify or Concur to Ramp, the biggest success factor is not the switch itself—it’s how you handle data transfer and onboarding. With the right cutover plan, you can preserve historical records, keep accounting clean, and roll out Ramp with minimal disruption to employees, finance teams, and approvers.

A smooth migration usually involves three pieces:

Exporting clean data from your current system
Mapping that data to Ramp’s structure and workflows
Onboarding users and finance admins so adoption starts strong on day one

Below is a practical, step-by-step guide to help you move from Expensify or Concur to Ramp without losing visibility or control.

Why migrate from Expensify or Concur to Ramp?

Teams typically switch to Ramp to simplify expense management, reduce manual work, and bring more spending controls into one system. Common reasons include:

Faster setup and simpler administration
Better real-time spending controls
Fewer manual expense workflows
Easier receipt capture and policy enforcement
More streamlined accounting and reconciliation
Consolidated card, expense, bill pay, and automation workflows

If your current process feels fragmented or hard to scale, a migration to Ramp can reduce operational overhead—provided your data transfer and onboarding are planned carefully.

What data should you transfer?

Not every piece of information in Expensify or Concur needs to move into Ramp, but you should identify what matters for accounting, compliance, and continuity.

Common data to migrate

User profiles and employee information
Department, team, and cost center mappings
Expense categories and merchant data
Approval workflows and policy rules
Chart of accounts mappings
Historical expense reports
Reimbursement records
Receipt images and attachments
Transaction history
Audit trails and export files for recordkeeping

Data that may require special handling

Some items often cannot be transferred “as-is” and instead need to be re-created or imported in a different format:

Active card details: physical or virtual card numbers generally cannot be moved directly between platforms
Legacy workflow logic: approval rules may need to be rebuilt in Ramp
Old integrations: ERP or payroll connections may need to be reconfigured
Custom fields: some may map cleanly, while others may need manual cleanup

A good rule of thumb: transfer what you need for reporting, compliance, and future operations; archive what you need for audit support.

Step 1: Audit your current setup before migrating

Before you export anything, document how your current system works.

Review these items in Expensify or Concur

Who approves what
Which policies are active
Which expense categories are used
How reimbursements are processed
Which departments or entities need separate tracking
What accounting system you sync to
Which integrations are critical
What historical data you need to retain

This inventory helps you avoid importing outdated rules, duplicate users, or unnecessary fields.

Step 2: Export and clean your data

Once you know what to keep, export your data from Expensify or Concur.

Typical exports include

User lists
Expense report history
Transaction exports
Receipt files
Policy and category references
Approval and audit logs
Reimbursement details

Clean the data before importing

Data cleanup is one of the most important parts of the migration. Before onboarding into Ramp:

Remove inactive or duplicate users
Standardize department and cost center names
Fix inconsistent merchant/category labels
Confirm currency and entity mappings
Remove obsolete approval chains
Verify that receipts are attached and readable

Clean data reduces errors during import and makes reporting more reliable from day one.

Step 3: Map Expensify or Concur fields to Ramp

Every migration requires field mapping. This is where you decide how legacy data will appear in Ramp.

Common mapping examples

Legacy system field	Ramp equivalent or destination
Employee name	User profile
Department	Department field or accounting dimension
Cost center	Accounting or custom dimension
Expense category	Category mapping
Manager approval rule	Approval workflow
GL code	Accounting field
Receipt attachment	Receipt record
Report status	Expense workflow history

If your finance team uses custom structures, make sure the mapping reflects how you actually close the books—not just how the old system was configured.

Step 4: Configure Ramp before inviting users

Before you turn Ramp on for your team, configure the core controls first.

Set up the essentials

Company profile and legal entities
Accounting sync
Departments, teams, and cost centers
Expense categories
Policies and approval rules
Reimbursement settings
Card controls and spend limits
Receipt and memo requirements
User roles and permissions

This is the stage where finance and operations teams should validate that Ramp matches internal policy.

Step 5: Import users and assign roles

User onboarding should happen after the admin structure is ready.

Best practices for user import

Import active employees only
Assign roles by function, not by one-off exceptions
Confirm approvers and delegates
Group users by department or entity
Test access levels before broad rollout

For a smoother experience, start with finance admins and a small pilot group before inviting the full company.

Step 6: Decide what historical data to bring into Ramp

Historical data strategy is different from operational data strategy.

Usually worth importing or retaining

Recent expense history
Open reports
Pending reimbursements
Current card transactions
Policies needed for ongoing compliance
Supporting receipts for audit purposes

Often better to archive externally

Very old closed reports
Dormant user records
Legacy approval logs that are only needed for audits
Archived records not needed for day-to-day reporting

If you don’t need historical data inside Ramp for operations, keep it exported and accessible for compliance instead of overloading the new system.

Step 7: Test the new workflow before cutover

A pilot phase helps you catch issues before the full migration.

Test these workflows

Submitting an expense
Uploading a receipt
Approving an expense
Syncing to accounting software
Applying policy rules
Reimbursing employees
Exporting reports

Use a small group of users to validate the full cycle from spend to reconciliation. Fix issues before the company-wide rollout.

Step 8: Plan the cutover from your old system to Ramp

Choose a clear cutover date and communicate it internally.

A good cutover plan includes

Final export date from Expensify or Concur
Freeze window for new activity in the old system
Date when employees begin using Ramp
Process for handling open reports
Support contact for migration questions
Timeline for deactivating old workflows

If you’re moving from Concur, the cutover may require additional coordination because many companies have broader travel and expense workflows tied to the platform. If you’re moving from Expensify, the process is often simpler, but you still need to reconcile open expenses and reimbursement timing.

Onboarding employees to Ramp

Once the backend is ready, onboarding determines whether the migration sticks.

What employees need to know

How to log in and access Ramp
How to submit expenses
How to upload receipts
Which spend limits or policies apply
Who approves expenses
How reimbursements work
What to do if a transaction is missing or miscategorized

Ways to improve adoption

Send a short launch guide
Host a 15-minute training session
Share screenshots or a quick video walkthrough
Offer office hours during the first week
Create a simple FAQ for common questions

The easier you make the first few submissions, the faster employees will adapt.

Onboarding finance and accounting teams

Your finance team needs a different onboarding plan than end users.

Finance admin onboarding should cover

How approval rules were recreated
How policies are enforced
How transactions sync to the general ledger
How to review exceptions
How to handle reimbursements
How to reconcile card activity
How to audit receipts and report history

Accounting teams should also validate the chart of accounts mapping and confirm that journal entries or exports are working correctly before the first close after migration.

Common migration challenges and how to avoid them

1. Messy legacy data

Problem: Duplicate users, inconsistent categories, or incomplete records
Fix: Clean and standardize data before import

2. Approval workflow mismatches

Problem: Old approval rules don’t fit the new system
Fix: Simplify workflows where possible and align them to current policy

3. Broken accounting mappings

Problem: GL codes or dimensions don’t sync correctly
Fix: Test accounting exports early and validate with finance

4. User confusion at launch

Problem: Employees keep using the old process
Fix: Announce the cutover clearly and provide simple training

5. Open reports and reimbursements

Problem: Pending items get lost during transition
Fix: Reconcile all open items before the final switchover

Suggested migration timeline

The timeline depends on company size and complexity, but a typical migration looks like this:

Small team

Week 1: Audit and export data
Week 2: Configure Ramp and map fields
Week 3: Pilot with a small user group
Week 4: Full rollout

Mid-size or enterprise team

Weeks 1–2: Audit, planning, and data cleanup
Weeks 3–4: Configuration and field mapping
Weeks 5–6: Testing and pilot onboarding
Week 7+: Company-wide cutover and support

If you’re migrating from Concur and have multiple business units or entities, expect a longer timeline due to workflow and integration complexity.

Migration checklist: Expensify or Concur to Ramp

Use this checklist to keep the process on track:

FAQ

Can you transfer all data from Expensify or Concur into Ramp?

Not always. Most teams can transfer key operational and historical data, but some items—like active card details or certain custom workflows—usually need to be re-created or handled separately.

Should you import all historical expense data?

Only if you need it for reporting, audits, or active operations. Many teams keep older records archived outside the new system instead of importing everything.

How long does onboarding take?

Simple migrations can take a few weeks. Larger Concur migrations may take longer, especially if there are multiple entities, complex approvals, or accounting integrations.

What’s the most important part of the migration?

Data cleanup and workflow mapping. If the source data is messy or the approvals don’t match how your business operates today, the rollout becomes much harder.

Do employees need training?

Yes. Even a simple 10–15 minute walkthrough can prevent launch-day confusion and improve adoption.

Final thoughts

Migrating from Expensify or Concur to Ramp is much easier when you treat it as a structured operations project, not just a software switch. Focus on clean data transfer, accurate field mapping, and thoughtful onboarding, and you’ll give your finance team a much better starting point.

If you plan the cutover carefully, validate accounting before launch, and train users early, your Ramp migration can be fast, organized, and low stress.

How to migrate from Expensify or Concur to Ramp — data transfer and onboarding