Migrate
Needed in daily work
- Examples
- Vehicle list, driver list, geofences, user roles
- Check
- Compare a sample on the new platform
Platform migration · Free Excel template
MDVR re-pointing checklist: moving devices off CMSV6
A plan for re-pointing an MDVR fleet from a CMSV6 server to another one. List the devices, decide what video and history to keep, map the reports, re-point the devices in waves and sign off.
Free: enter your name and email and we send you the file. Works in Excel, Microsoft 365, Google Sheets and LibreOffice Calc. No macros.
- 44 tasks in 8 phases
- Data-to-keep sheet
- Cut-over readiness verdict
- Every device, model and SIM listedDone
- Recordings to keep exported and countedDone
- Roll-back steps written downCheck
- Pilot group signed off
What's inside
Eight phases, from the first inventory to sign-off
One workbook with eight sheets: Start here, Checklist, Devices, Data to keep, Reports, Plan, Summary and Lists.
1. Inventory
Every vehicle, device model, device ID, SIM, channel count and storage type, and the server each device reports to today.
2. Data to keep
Which recordings and histories you must keep, for how long and why. Export them and count the files.
3. Users and roles
Who can view, edit and get video on the new platform. Leave old accounts behind.
4. Reports and alarms
What the team uses every week, and what matches it on the new platform. Mark each one Same, Partly or Missing.
5. Re-point devices
Back up the configuration, write the roll-back steps, change one test device and check it.
6. Pilot and parallel run
A few vehicles of each model, compared with trips you know. A written go or no-go.
7. Cut-over and training
Move the rest in waves. Train supervisors. Keep roll-back available until each wave is accepted.
8. Acceptance and close
Every active device reports, the archive is checked, and the old platform stops only after sign-off.
The decision that matters most
What happens to each piece of history?
The Data to keep sheet asks for one decision per item. Nothing is moved by default.
Archive only
Kept, but not used daily
- Examples
- Old recordings, issued reports, event history
- Check
- Count files against the export log
Drop
No reason to keep
- Examples
- Test vehicles, accounts of people who left
- Check
- Make sure no contract or incident needs it
What does a platform migration involve?
Moving a fleet is more than changing a server address. You also move people, reports, habits and history. The checklist keeps all of it in one plan, so nothing is found missing after the old platform is switched off.
The title names CMSV6 only as an example of the platform you may be leaving. The plan itself is neutral. It works for a move between any two platforms.
How to use the checklist
- Fill in Start here. Name the project, the lead, the current platform and the new one.
- List every device. Type the device ID as text, exactly as the device sends it.
- Decide on the data. One decision per item: migrate, archive only or drop.
- Map the reports. Ask supervisors what they open every week.
- Plan the waves. Dates, success criteria and the roll-back trigger for each stage.
- Work the Checklist and read the Summary. It shows open critical tasks, report gaps and how many devices have moved.
Why a pilot comes first
A pilot shows problems while only a few vehicles are affected. Pick a few vehicles of each model and each kind of use, and include one that works in weak coverage. Compare what the new platform shows with trips you already know.
Re-pointing a device
Re-pointing means changing the server address, port and protocol in the device so it reports to the new platform. The exact setting and method come from your device manual. Back up the configuration first and write down how to put the old values back.
Cut-over readiness = Not ready if a critical task in phases 1 to 6 is open
Check = no critical task open, but report gaps or undecided data remainReady for cut-over = all of the above are clearCritical flags are our suggestion. Change them to fit your project.
Limits
Ask before you assume
This file is a plan. It does not say that any device, recording or setting can be moved between platforms, and Tracom has not tested every combination. Ask your supplier in writing what can be transferred. Check retention and notice periods against the current official text and your own contracts.
Related Tracom solution
Moving MDVR fleets to Tracom devices
Tracom M1N is a mobile DVR (MDVR). Camera options such as DSM/ADAS are confirmed with the Tracom team. Tracom devices send data to the Safee platform. Bring this checklist and we go through what can be moved from your current setup.
- Tracom M1N MDVR. Camera options such as DSM/ADAS are confirmed with the Tracom team.
- SCMS portal. Manage devices and configuration files in one place.
- Advanced configuration files. Keep a known-good configuration for each model.
- Over-the-air updates. Update device software without a workshop visit.
Does the checklist work for any platform?
Yes. The tasks are general: inventory, data, users, reports, re-pointing, pilot and sign-off. Type your own platform names on Start here.
Can I move my old recordings to the new platform?
It depends on both platforms and on the file format. Often the practical answer is to archive them and keep access for as long as you need. Ask your supplier in writing.
How long should the pilot run?
There is no fixed number. Set it on the Plan sheet so it covers each model, each kind of route and a working week at least. Your own risk review decides.
Do I need to keep the old platform running?
Keep access for roll-back and for the archive until sign-off. Read the notice and access terms in your contract first.
Which tasks are marked critical?
Twelve before cut-over and two after, such as written roll-back steps and a go or no-go from operations. They are suggestions. Change the Yes or No in column E.
What is Tracom's role here?
Tracom makes the devices. This checklist is a neutral planning tool and makes no claim about compatibility with any platform or device.
Next step
Planning a move to Tracom devices?
Bring the checklist and your device list. We will tell you what we can confirm and what we still have to test.
Related tools and templates