Four hours spent reopening old expense claims because an exported “receipt” column contains dead links: that is the migration cost a cheaper subscription can hide.
For a startup planning to migrate expense data between tools, three criteria decide the route: whether historical transactions must remain searchable in the new app, whether receipt files can travel with stable identifiers, and whether approvals must remain visible. Compare a full historical import with a linked archive—not just one subscription price against another.
1. Three years of expenses, but only current spending needs a new home
A five-person startup has 4,800 historical expenses. Its finance lead wants a simpler capture workflow, not another review of already-closed periods.
Pick a linked archive: export historical rows into a spreadsheet, preserve receipt files separately, and connect them using the old transaction IDs. Start new spending in the new workflow from an agreed date. This avoids importing closed expenses as unpaid claims or accidentally including them in reimbursement runs.
Pick a full historical import if staff regularly search old claims inside the expense app, or finance needs past approvals alongside current records. A destination that demonstrably imports those relationships wins on retrieval convenience and workflow continuity. A folder and sheet cannot reproduce an approval audit trail by themselves.
Scan2Sheet fits the first route for new capture: it extracts receipt data into your own Google Sheet and links cloud-stored receipt images from each row. That does not establish compatibility with another tool’s historical export. Keep migration and new receipt capture as separate jobs.
2. The trial export has rows, but no usable receipt package
Before committing to either route—or signing the next subscription—export a small batch from the old tool and test what the destination accepts.
CSV or XLSX usually carries dates, merchants, amounts, and categories cleanly. It does not necessarily carry documents, approval history, comments, or reimbursement status. Even a populated receipt-link column may only point to an authenticated page in the old app.
Ask for three things:
- Transaction export: original IDs, currency codes, signed amounts, dates, and statuses, with a field dictionary if available.
- Document export: actual image or PDF files, not thumbnails or links that expire.
- Attachment mapping: a manifest connecting transaction IDs to filenames, including multiple files per expense.
A ZIP containing image001.jpg through image900.jpg is not a usable migration unless you can identify which expense owns each file. Merchant and date are weak substitutes: two employees can buy lunch at the same café on the same day.
Choose full import only after a pilot preserves these connections. Otherwise, build the archive mapping while the old interface can still resolve ambiguous files. Ask the destination vendor which fields it drops rather than assuming “CSV supported” means history preserved.
3. The imported total agrees, but the evidence is wrong
Use a deliberately awkward pilot: a refund, a foreign-currency purchase, and a long receipt with several pages. For example, these three source rows use the same currency:
| Source ID | Date | Merchant | Signed amount | Receipt files |
|---|---|---|---|---|
| EX-2041 | 2025-09-08 | Northline Office | 118.40 | 3 |
| EX-2042 | 2025-09-09 | Cedar Café | 61.60 | 1 |
| EX-2043 | 2025-09-10 | Northline Office refund | -18.40 | 1 |
The control total is 118.40 + 61.60 − 18.40 = 161.60. If the importer strips the refund’s minus sign, it becomes 198.40: an overstatement of 36.80, not 18.40.
After import, reconcile row counts and signed totals by month and currency; never add different currencies into one control total. Compare source IDs to find missing or duplicated rows.
Then check evidence separately. Confirm five files across these three rows, open them, and inspect every page of EX-2041. A matching total cannot reveal that page three disappeared or the refund image was attached to the purchase. Test links using the account your bookkeeper will actually use; owner-only permissions can hide a failed handover.
4. The renewal arrives before the archive is proven
Cancellation does not end the obligation to retain business records. The applicable period, acceptable formats, and access requirements depend on jurisdiction and record type; check the relevant tax authority and company-records regulator, with your accountant’s help.
Keep the old system readable until the full export reconciles, exceptions are resolved, and receipt retrieval works outside it. Confirm whether read-only access survives cancellation; do not assume it does. Preserve originals and a dated migration log alongside the archive.
Apply the same exit test to the replacement. Owning a spreadsheet is useful, but linked cloud images still need an independent retention plan.
Try Scan2Sheet for new receipts once your historical archive passes those checks.