Reusing the device is only one part of the move
A fleet sells a vehicle, returns a lease or replaces a van, and the tracker appears ready for the next assignment. The useful question is not just whether the unit powers on in the replacement vehicle. It is whether the new installation, vehicle identity, records and commercial arrangement have all been checked.
Treat the transfer as a small handover with an owner and a clear changeover time. The method below is a proposed review checklist, not a claim that every tracker can be reused or that SafarTrak automatically transfers vehicle records. Actual support depends on the device, firmware, vehicle and agreed configuration.
Keep the old vehicle’s history separate
Before anyone changes a vehicle name, ask the platform provider what reassignment does to previous journeys, odometer values and vehicle references. Establish how the original record will remain identifiable, what access is needed later and whether any agreed export or retention arrangement applies. Do not assume that renaming a record creates a clean history boundary.
Geotab’s current Automatic Vehicle Management documentation provides a concrete vendor example: its handling of a GO device moved between vehicles depends on whether AVM is enabled. The documented disabled case can leave previous trip history associated with the original record while vehicle details change. This illustrates why configuration matters; it does not describe SafarTrak behaviour.
Record the old vehicle reference, device reference, last verified report time and agreed handover time in your controlled fleet records. Keep full identifiers and operational history within your approved business systems, rather than a public support discussion.
Check fit again for the replacement vehicle
Give the installer or provider the new vehicle make, model, year and the exact device model. Confirm the connection, power arrangement, harness or adapter and any peripheral requirements against the relevant installation instructions. Arrange physical removal and refitting with the responsible installer; this article is not a wiring guide.
A device that physically connects is not proof that every previous reading remains available. Ask which location, ignition, diagnostic or sensor fields are supported on the new combination. If a field is unavailable, record it as unknown or unsupported instead of copying an old vehicle’s baseline. Confirm any recalibration or configuration work with the responsible provider before using the reading.
Agree the commercial change as well as the technical one
Ask whether the software subscription follows the device, the vehicle, the account or another agreed unit. Confirm when the old vehicle stops being billed, when the new one starts and whether removal, refitting, replacement accessories, configuration or connectivity changes are separately charged. These are questions for the proposal or agreement, not assumed SafarTrak fees.
Also confirm responsibility for the SIM or data service, account access and any equipment supplied by a leasing company or previous provider. Do not cancel a connection before the handover owner confirms the sequence. SafarTrak’s Pricing & Rollout page outlines the software, hardware, connectivity and service items to discuss; the actual proposal must state what applies to your fleet.
Verify the first records before accepting the handover
After the agreed changeover, compare the displayed vehicle identity and the device reference with the installation record. Check the time of the latest report and a known vehicle activity. For a short authorised test, compare available journey and event records with the actual sequence, allowing for the configured reporting interval.
Check distance and engine-hour sources separately where they are available. A replacement vehicle may have a different accumulated distance or runtime. Do not treat a counter reset, an inferred value or a gap in reporting as a new vehicle’s verified starting value. Ask the provider to explain discrepancies before accepting the report for maintenance or operational decisions.
Review both sides of the boundary: the old vehicle should remain distinguishable in the required history, and the new vehicle’s records should describe the new vehicle. Test applicable rules and recipient assignments without creating unnecessary alerts or assuming that old settings fit the new duty.
Close the transfer with evidence and an owner
Use the downloadable handover template linked below to record the agreed changeover, fit check, record-boundary check, supported fields, commercial questions and unresolved items. Keep it with the installation or asset record. The blank template contains no customer or vehicle data; populate it only in your approved workspace.
A useful acceptance note states what was checked, what remains unsupported and who will follow up. Proceed only when the readings required for the intended workflow are understood. If the new vehicle needs different hardware or the old account cannot be reassigned as expected, revise the plan rather than assuming a successful physical move completes the job.
For a SafarTrak discussion, bring the exact existing tracker model, replacement vehicle details and the readings your team needs. Start with a compatibility review and agree the installation, record-handling and commercial scope for that combination.
Sources and further reading
Manufacturer documentation illustrates vehicle-specific coverage. It does not establish compatibility for a SafarTrak deployment.
BRING IT TO YOUR FLEET
Start with your vehicles.
Ask the right questions.
Share your vehicle mix, existing devices and required signals with the SafarTrak team.
Discuss the tracker and replacement vehicleDiscuss your deployment
