Webfleet alternative: options, LINK hardware, exit

Short version. Webfleet is Bridgestone’s fleet platform, and a strong one: its own LINK trackers, driver terminals, factory-telematics connections and a documented API. Leaving costs you in two places: a contract that renews for a year unless you give three months’ notice, and LINK devices on Webfleet SIMs licensed only for its platform, which you should plan on replacing. For another full-service vendor, look at Geotab or Samsara; to build it yourself, Traccar. For self-hosted telemetry and customer reports on open-protocol trackers, Routly.

Webfleet used to be TomTom Telematics and was renamed after Bridgestone bought it. Every claim about Webfleet below links to its own pages, terms or API reference, checked on the date at the top.

What Webfleet does well

• A complete hardware range. The LINK family covers self-installed plug-in units (LINK 140, LINK 245), fixed installs for cars, vans and trucks (LINK 640, LINK 740), an asset tracker (LINK 340) and a trailer device (LINK 350).
• Driver-facing hardware. The LINK 245 and 740 connect to the PRO X, PRO M and PRO i terminals and to the Webfleet Work App, and the API handles job dispatch and routes sent to the vehicle.
• No box at all for some vehicles. OEM.connect activates factory-fitted telematics from the VIN.
• Tachograph data. Partners can read customers’ tachograph data stored in Webfleet through TachoShare.connect.
• An ecosystem. WEBFLEET.connect is a documented API with a partner programme, and maintenance tools like Fleetio integrate with it.

If your operation runs on PRO terminals and dispatched jobs, that is a whole workflow, not a feature.

What Webfleet costs

Webfleet does not publish a price list. Its UK van-tracking page advertises tracking from £7.95 a month. The footnote on the same page describes a £7.35 per vehicle per month offer on a tariff purchase agreement, with hardware and installation not included. Treat that as the floor of a quote, not the quote.

The terms matter more than the tariff. Under the UK general terms (version dated 1 April 2026):

• The contract runs for the Minimum Contract Period on your order form. It then renews automatically for a year at a time unless either side gives written notice at least three months before the renewal date (clause 3.1).
• Shrinking the fleet mid-term is rationed. You need at least a year on the service. Above ten vehicles you can terminate up to 10% of the fleet a year, capped at 50 vehicles. At ten or fewer, it is one vehicle a year.
• Selling a vehicle doesn’t end its subscription. The service for that vehicle stops, but you keep paying until the term ends (Service Terms, clause 2.8).

Leaving Verizon Connect covers the renewal-window trap; it applies here word for word.

Can LINK devices be re-pointed to another platform?

We could not find anything from Webfleet saying they can. Here is what the published terms do say:

• The SIM is Webfleet’s. The SIMs Webfleet supplies stay its property. You are licensed to use them only to send data between your fleet and the Webfleet platform (Service Terms, clauses 5.1–5.2).
• So is the device’s intellectual property. Webfleet keeps the IP rights in the Products, and the general terms bar reverse-engineering or modifying them (clause 6.1).
• Rented devices go back. Rented hardware has to be returned when the contract ends, in substantially the condition it arrived (rental terms, clause 1.2).

Nothing in Webfleet’s developer documentation describes sending a LINK’s data to a third-party server. Plan a hardware replacement; if you own the devices and hope otherwise, get Webfleet’s answer in writing, for your model.

Two exceptions. Vehicles on OEM.connect have no Webfleet box, so ask which other platforms that manufacturer’s data feeds. And if you move to Geotab, its GO devices can feed software other than MyGeotab, so the next migration won’t have this problem.

Getting your data out of Webfleet

WEBFLEET.connect is the route, and its reference guide (version 1.75.0) is specific about the limits:

• Getting access. Customers request an API key through Webfleet support.
• Tracks are slow to pull. showTracks returns one vehicle’s positions for at most two days per request, at 10 requests a minute.
• Trips are slower. showTripReportExtern is limited to 1 request a minute.
• The API is thinner than the device. A LINK normally reports six positions a minute, but WEBFLEET.connect delivers one a minute as standard. More takes the HD Tracking add-on, charged per device.

Do the arithmetic first. A year of tracks for 200 vehicles is about 36,600 showTracks calls. At 10 a minute that is 61 hours of continuous calls, so start in the first week, not the last.

Check what is still there to pull. Webfleet’s data processing agreement lists retention by data type. Trip start and end records and trip fuel figures are kept for two full years plus the current year. Driving events, trouble codes and road-facing video are kept for 90 days, or 60 in France. Then list what no export will find for you: geofences, driver records, maintenance schedules, and the scheduled reports somebody depends on.

Does the EU Data Act help?

Possibly. The Data Act has applied since 12 September 2025, and it has two relevant parts.

Switching between data processing services. Article 25 requires a notice period of no more than two months, then a transitional period of at most 30 days to move your data. Under Article 29, switching charges are capped at cost until 12 January 2027 and banned after that. What the Act does not do is cancel a fixed term: it expressly allows proportionate early-termination penalties. Whether a telematics subscription counts as a “data processing service” is a question for your lawyer; we found no statement from Webfleet either way.

Access to connected-product data. Articles 4 and 5 give the user of a connected product the right to the data it generates, and to have it shared with a third party. A vehicle is plainly a connected product. Whether the tracker in it is one is less settled.

Leaving Samsara shows what this looks like when a vendor writes it into its contract.

The alternatives side by side

Traccar is the DIY answer. It is Apache-2.0, decodes more than 200 device protocols, and gives you a map and basic reports, but you build the rest.

Routly sits on top of a gateway. It decodes no trackers itself. Positions come in from Flespi, from Traccar, or from any gateway that POSTs JSON, and Routly turns them into trips, fuel events, driver scores and scheduled reports. You run it on your own servers, and the history lives in your own Postgres. The community is small, which matters when you are the one hosting.

When to stay with Webfleet

• Your drivers work from PRO terminals and dispatched jobs, and that workflow is the business.
• You depend on tachograph data in Webfleet and the reporting built around it.
• Much of the fleet is on OEM.connect with no hardware to manage.
• You want one vendor accountable for devices, SIMs, software and support, and the subscription is a fair price for that.

When to choose Routly

• You are replacing hardware anyway and want open-protocol trackers that will outlive any one platform.
• You want the data in your own database, not behind a two-days-per-request API.
• You are a provider with customers to separate, and need isolated organisations and per-customer report branding.
• The features that decide it are fuel drain detection, driver scoring and scheduled reports.

Routly has no tachograph download, no driver terminals, no job dispatch and no video. If those are the reasons you bought Webfleet, it is the wrong replacement.

How to leave Webfleet, in order

1. Find the order form. Note the Minimum Contract Period and the renewal date, and set a reminder at renewal minus three months, with an owner.
2. Request an API key and start the export. Pull tracks, trips, drivers and areas while you still have access, using the arithmetic above.
3. List the hardware. Mark each unit as owned or rented. Rented units go back; owned units need a written answer about reuse.
4. Pilot the replacement on five vehicles. Run both systems side by side and compare distance, engine hours and a few trips you can check by hand. Leaving Geotab explains why the numbers won’t match exactly.
5. Rebuild configuration and reports, then cut over. Send the non-renewal notice on the date from step one, wherever the project stands, and return rented units at the end.

Frequently asked

What is the best Webfleet alternative?

It depends on what you used Webfleet for. For another full-service vendor, Geotab or Samsara. For a self-hosted platform on your own trackers, Traccar if you only need a map, or Routly if you need trips, fuel, scoring and customer reports. The comparison hub has the rest.

Can I use Webfleet LINK devices with another platform?

Not as far as anything Webfleet publishes says. The supplied SIM is Webfleet’s property and licensed only for its platform, and rented units have to be returned. Ask in writing if you own the hardware.

How do I cancel a Webfleet contract?

In the UK, by written notice at least three months before the end of the Minimum Contract Period or the current renewal year. Otherwise it renews for another year.

Is Routly cheaper than Webfleet?

Self-hosted for your own fleet, Routly costs nothing to license under the AGPL, but you pay for servers, trackers and the time to run them. The cost worksheet does the comparison honestly. The public demo needs no account.