Migration Checklist for Switching From Motus or Cardata
The Kliks migration checklist helps finance, HR, payroll, operations, IT, and reimbursement administrators plan a controlled move from Motus, Cardata, or another incumbent vehicle reimbursement provider. The checklist is designed for FAVR and CPM migrations where driver data, FAVR rates, workflow rules, reimbursement history, compliance evidence, integrations, and audit records need to be requested, transferred, mapped, tested, and approved before cutover.
What the checklist covers
- Internal project setup, stakeholder owners, timeline, and decision checkpoints.
- Vendor-ready data request language that can be handed to the incumbent provider.
- Driver roster, eligibility, manager, cost center, territory, and location exports.
- FAVR rates, fixed and variable components, program settings, effective dates, and historical rate changes.
- Approval workflows, exception rules, reminders, document status, insurance evidence, payroll exports, and audit history.
- Secure transfer methods, encryption expectations, file naming, field definitions, control totals, and escalation contacts.
- Sandbox setup, side-by-side comparison, UAT scripts, release planning, final data refresh, go-live, and post-launch hypercare.
Why it matters
A vehicle reimbursement migration should not be a blind cutover. Customers should be able to review their current program structure in a sandbox, compare the old system and new system feature by feature, validate rates and exports, test admin and driver workflows, and sign off before shutting down the incumbent platform.
Download access
The PDF download is available from this page after a corporate work email is submitted. Personal and disposable email domains are not accepted for the checklist request.