Mileage guide
Changing iPhone: a mileage-log transfer acceptance checklist
By FlatMile ·
At a glance
Keep the old iPhone until the new phone's mileage history passes a deliberate comparison. A successful setup screen, restored subscription or visible backup file does not prove that the expected journeys, vehicles and purposes are present.
This is a verification protocol for your transfer, not a claim that we performed a two-device migration test. Use FlatMile's current backup and restore instructions, then check the result against records you preserved before the move.
Write the acceptance record before transferring
On the old phone, note the period being preserved, the vehicles involved and the newest journey you expect to see. Record totals with their units and filters. If an export includes only a selected year, it cannot serve as the control for all historical journeys.
While you have export access, save a separate CSV and open it outside FlatMile. All app CSV and PDF exports require an active subscription or eligible trial. Confirm a recent successful iCloud Drive backup as a separate check. FlatMile's backup and restore is not live synchronization between two phones.
For general copy and storage preparation, start with the backup guide. This page begins where that preparation ends: deciding whether the transfer result is good enough to retire the old device.
A fictional acceptance sheet
Taylor records these controls before changing phones. The figures are invented and are not product test results:
| Control | Old-phone reference | New-phone check |
|---|---|---|
| Review period | January 1 through October 19 | Same period selected |
| Trip count | 208 | Compare with 208 |
| Business distance | 3,120.4 miles | Compare units and total |
| Personal distance | 1,479.6 miles | Compare units and total |
| Combined distance | 4,600.0 miles | Reconcile the two categories |
| Vehicles | Car A and Car B | Inspect entries for both |
| Latest journey | October 19, job T-81 | Open the actual record |
A matching total is helpful but insufficient. Taylor opens an early journey, a middle journey and the latest journey, comparing date, purpose, classification, distance and vehicle. A timezone or filter difference may explain a mismatch; first identify the cause rather than reimporting everything.
Restore history and access as separate checks
Follow the backup procedure in FlatMile support. If the backup is not fully available from iCloud, wait for the app's download or status process to finish and inspect any message. Do not interpret an incomplete package as an empty log and erase the old phone.
Purchase restoration concerns subscription access. After it succeeds, open the actual mileage history. If a CSV was used for recovery, remember that a readable log export and a full app backup are different formats with different contents; do not assume route maps or every setting were reconstructed.
Investigate differences while you have a reference
Write down the mismatched control, which device shows which value and the selected period or vehicle. Keep the source file unchanged. Avoid repeated imports as a troubleshooting experiment because they can make the history harder to compare.
Check a newly recorded journey on the new phone as well as the restored past. Historical completeness and current capture setup are separate acceptance questions. Once both are satisfactory, check the new phone's backup status and retain the dated archive before following Apple's normal process to retire the old device.