Straight into the service manual page
WrenchQuarry
More

3G fleet trackers: 2 upgrade or switch options

WrenchQuarry Editorial Team · Published · 11 min read · How these guides are written

For fleet trackers on 3G, compare upgrading to 4G LTE with your current provider against switching providers.

Key takeaways

  • Confirm each device's network type with your provider.
  • Get written quotes covering hardware, installation, and downtime.
  • Check contract exit terms and data exports.
  • Test representative vehicles before scheduling the fleet.

Neither path is always right. The better choice depends on how many vehicles are affected, how well your current system serves your team, and what your contracts allow.

This guide explains how to check your situation, what each path involves, which mistakes to avoid, and how to choose. It is written for fleet owners and dispatchers who need their trackers to keep working through the change.

Why the network change matters

A GPS tracker is only useful if it can reach a network. When the cellular network it relies on goes away, the tracker goes quiet and its data stops arriving. The map they check every morning could go blank.

The impact falls on different people in different ways. Dispatchers lose live position when they need to reroute a crew or answer a customer call. Owners lose the reports they use for billing, payroll, and questions like "where is my technician?" Drivers may notice too, especially if the tracker also runs a driver app or a timesheet feature.

Fleet tracking is no longer a niche tool. Samsara reports that "over 75% of fleet managers rely on fleet tracking software or vehicle telematics to help support day-to-day operations in at least some of their vehicles, according to data from Government Fleet's annual benchmarking survey." If your operation runs on that data, a silent tracker is an operations problem, not a small hardware issue.

Vehicle technology also keeps moving. A device installed a few years ago may already sit behind the technology your provider wants to support, so treat the 3G change as a reason to review the whole setup, not just one box.

Step one: find out what you actually have

Start with an inventory, because you cannot plan a fix for devices you cannot name. Do not guess from a vehicle's age or from what you remember buying. Samsara's advice is direct: "Confirm with your telematics provider which of your installed devices are 3G or 4G LTE." Ask for a device-by-device list, then check it against your own records.

A useful list includes the fields below.

FieldWhy it matters
Vehicle or asset name and IDLinks each device to a truck, van, or car your team recognizes
Device model and serial numberShows which upgrade or replacement applies
Network type, 3G or 4G LTEIdentifies devices that need a network change
Provider and contract end dateHelps you check timing and exit terms
Owned, leased, or rentedHelps you check who pays for replacement hardware
Status: active, sold, in storage, or spareStops you paying for devices that do nothing

Sort the list by how much each vehicle matters. Vehicles on your highest-value routes, vehicles carrying expensive equipment, and vehicles serving contracts with strict arrival windows should come first. Dispatchers are the best source for this ranking, because they know which trucks they send out most often and which ones they cannot do without.

Check what you can export, too. Ask whether you can download trip history, alerts, and reports in a format your team can open. This matters whichever path you take. If the answer is unclear, get it in writing before you commit. Your history is part of your business records, and you should not lose it because a contract ended.

Option one: upgrade the trackers you have

Ask your provider what upgrade is available for each device on your list, and get the answer in writing.

The biggest advantage is continuity. Your team already knows the system, so training is minimal. For many operations, that matters more than any list of new features. A platform change forces everyone to relearn a daily routine, often at the busiest possible time.

The main cost is the upgrade itself. Samsara frames the decision this way: "Evaluate your options closely, and determine if the time and costs involved in migrating to 4G hardware with your current provider will yield the best outcome for your business." Count three things: the hardware, the installation labor, and the time each vehicle spends off the road. A cheap device can still be an expensive choice if every install keeps a truck parked for a long stretch. Put a rough value on lost work so you can compare it fairly with the other path.

Contracts can change the math. The same page notes that "Many 4G providers like Samsara, have attractive offers for companies upgrading their 3G telematics technology and can offer contract buy-outs for those who are eligible." Treat that as a lead, not a promise. Ask exactly what qualifies your fleet, whether the offer comes from your current provider or only from a new one, and whether it covers every vehicle or only some.

When you upgrade, install in priority order. Start with your most important vehicles and schedule work around peak job times. Keep a simple record of which vehicles are finished, then match that record against your inventory list and the live system. That check catches any unit that did not come back online.

When upgrading makes sense

Upgrading makes the most sense when most of your fleet already sits with one provider, your software works well for your team, and the upgrade quote is clear and reasonable. It makes less sense if your provider cannot describe a clear 4G path for your devices, or if the current software causes problems that a new device will not fix.

Option two: switch providers and rebuild

The second path treats the 3G change as a natural break point. Samsara makes the case: "The 3G sunset could be an opportunity to switch providers and improve your entire fleet tracking technology." Instead of asking how to keep the old setup alive, ask what you would choose today if you were starting over.

A switch means choosing a provider, selecting hardware, installing devices, and moving vehicle records and settings. It also means a stretch when some vehicles run on the old system and others on the new one. Plan for that overlap. Keep the old account active until every vehicle reports correctly on the new system, and confirm your data has been exported before you close it.

What to compare

When you compare providers, look past the device price. Useful questions include:

  • How accurate and how quick is location reporting where your vehicles work?
  • Can dispatchers set up geofences, alerts, and route views the way your team works?
  • Is the driver app simple enough for crews to use without a long training session?
  • What reports does the system produce, and can they feed billing or payroll?
  • Does it connect to the other tools you already use?
  • What support hours do they offer, and how do they handle outages?
  • What happens to your data if you leave later?

Get written quotes from at least two providers, and ask each one to explain how its hardware connects to the network. Because the 3G problem is about network access, you want a plain answer on the cellular technology each device uses and on what happens when that technology changes again. Use these fleet tracking vendor checks to organize your comparison.

Vendor pages can sound alike. One provider's marketing promises that you can "Get unparalleled visibility into your vehicles’ location, usage, and health" (Motive). That is a fair starting point, but it is not a specification. Ask for the exact fields you will see, how often location updates, and what the usage and health data means for your daily work.

Watch for lock-in. A provider may offer a low hardware price but make it hard to export your data or remove devices from its platform. Read the exit terms before you sign. A good deal on day one can become a poor one if leaving later costs more than staying.

The switch path asks more of you. The payoff is that you can fix other weak points at the same time, such as aging software, weak reports, or thin support. If your current system works well apart from the network, the upgrade path may be enough.

Common mistakes to avoid

Several mistakes come up again and again when fleets handle a network change. The first is waiting. A tracker that works today can stop working when the network change reaches it, and a rushed install is much harder to manage than a planned one. Start the inventory now, even if you have not chosen a path.

The second is choosing on price alone. A low device price can hide high install costs, long downtime, or a contract that charges for every extra feature. Compare the full cost of each path, including the time your staff spend managing the project.

The third is forgetting vehicles that are off the road. Spare units, sold vehicles, and trucks in storage can still appear in your records and on your invoices. Include them in the inventory so you can close out what you no longer need.

The fourth is skipping a test. Installing a new system across the whole fleet at once leaves no room to catch problems early. A small test group gives you a safer way to learn what works.

The fifth is ignoring drivers and customers. Crews need to know when a device will change and what to do if a tracker goes dark. Customers who rely on arrival updates need notice if your process changes. A short message in advance prevents many complaints later.

Test before you commit

Before you commit a whole fleet to either path, run a pilot. Choose one or two vehicles that represent your typical work: one on long routes and one on short local jobs. Install the new device or system in those vehicles first, then watch them for at least several working days.

During the pilot, check a few things. Does location update often enough for dispatch to use it? Do alerts such as speeding, idling, or geofence entries fire when they should? Does the driver app work in areas with weak signal? Do the reports match what you see on the map? Write down each problem, and ask the provider to fix it before the rest of the fleet moves over.

A pilot also gives you real numbers. You will learn how long an install takes, how many minutes a vehicle is out of service, and how often a device needs attention. Those figures beat any estimate built from a sales sheet. Use them to update your cost comparison before you choose.

Keep the pilot honest. If a vehicle behaves badly, do not quietly leave it out of the test. That unit shows exactly the kind of problem you need to find before a full rollout.

Illustrative example: installation and downtime

Suppose an illustrative pilot involves a short installation, but the vehicle is unavailable for 40 minutes, including moving it and checking its reports. Schedule around the 40 minutes, rather than treating the installation as the whole interruption. Compare both paths using the same measure of time off the road.

Talk to your drivers and customers

Tracking changes reach beyond the office. Drivers may need to log in to a new app, follow a new check-in routine, or carry a different device. Explain the change in plain words, say when it will happen, and name who to call if something goes wrong. Ask drivers what worked and what did not during the pilot, since they will use the system more than anyone.

Give drivers a fallback for any period when a tracker is offline. A simple routine, such as a check-in call at the start and end of each job, keeps dispatch informed without depending on the device. Make sure everyone knows the routine before the old system goes dark.

Customers may notice, too. If they receive arrival estimates, technician updates, or live tracking links, tell them ahead of time if those features will change for a while. A short note explaining what is changing and when is usually enough. It is far better than a customer finding a broken link on the day of a visit. A customer arrival update plan can help you assign who sends each update.

How to choose

Use a few plain questions to decide between the two paths. These illustrative comparisons are prompts for checking your own quotes and constraints.

QuestionLeans toward upgradeLeans toward switch
How many vehicles are affected?Illustrative: only a few units run on 3GIllustrative: most of the fleet runs on 3G
How well does your software serve the team?Illustrative: it works well every dayIllustrative: the team works around it with spreadsheets or notes
What do your contracts allow?Illustrative: a clear buy-out or upgrade offerIllustrative: early-exit fees are low and data moves easily
How much downtime can you accept?Illustrative: small, staged installs fit your scheduleIllustrative: you can absorb an overlap period
What is your timeline?Illustrative: a tight deadline with a clear quoteIllustrative: enough time for a pilot and a careful cutover

Downtime deserves a closer look. Upgrades and switches both take vehicles off routine work for a while. Write down how many vehicles you can have out at once without hurting service, and plan installs around that limit. Work backward from the date you need tracking to be reliable, and leave room in the schedule for problems.

A simple next step today

Ask your current provider for the device-by-device network list today, then check it against your vehicle records. Keep the plan in one shared document so dispatch, the office, and the provider all work from the same list. When a vehicle is finished, update the list that same day. A clear record prevents one of the most common problems in fleet projects: a truck everyone assumes is tracked, but is not.

Common questions

Can I keep my current provider?

You can consider staying if your provider offers a suitable 4G LTE upgrade for your devices. Confirm the hardware, installation work, and contract terms in writing.

Is switching always the better choice?

Switching makes sense when its benefits justify the disruption for your fleet. Software problems, reporting needs, support, exit terms, and pilot results all belong in that decision.

Sources

More field guides