# Switch TMS one job at a time.

> Run one job in Roadmark beside McLeod, TMW, TruckMate or your own TMS while orders still land there. Move over company by company, lane by lane, or never.

URL: https://roadmark.ai/switching
Language: en

Run one job in Roadmark beside McLeod, TMW, TruckMate or your own system, usually quoting or tracking. Orders still land in your current TMS, so dispatch doesn't change. Then move over company by company when you choose, or never.

## Start beside the TMS you run. Nothing is typed twice.

Roadmark sends each booked order to your current TMS with the stops, rate and references on it, and reads dispatch, status, stops and POD back. Your dispatchers keep working where they work today.

- Roadmark → McLeod, TMW, TruckMate or your own: Order with stops, rate and references
- McLeod, TMW, TruckMate or your own → Roadmark: Dispatch, status, stops and POD

1. **Connect:** Your inbox, your current TMS and your ELD. We do the setup with you.
2. **Run one job in Roadmark:** Usually quoting or tracking. Orders still land in your TMS, so dispatch doesn't change.
3. **Move over when you choose:** One company, division or lane at a time, or never. Your old system stays readable for history.

## What moves to Roadmark, and what keeps running where it is.

While Roadmark runs one job, everything else carries on in the systems you already have. You choose what moves next, and when.

**Moves to Roadmark, one job at a time**

- Quotes from the inbox
- Tracking and ETAs
- Customer and carrier portals
- Invoices on POD

**Stays in McLeod, TMW, TruckMate or your own**

- Dispatch, as today
- Driver settlements, as today
- Every job you haven't moved yet
- Your history, readable after you move

**Stays connected either way**

- Your ELD: Samsara, Motive, Geotab or Omnitracs
- Your books in QuickBooks, Sage, Xero or NetSuite, synced both ways
- EDI with your customers
- Load boards like DAT and Truckstop

## Move your group over, one job at a time.

Start with quoting beside your current TMS. Move planning and invoicing when each company is ready, while keeping the books in QuickBooks. When another company joins the group, begin with the workflow that fits its operation.

| Job | Month 1: Quoting beside McLeod | Month 4: The fleet plans here | Month 12: Off TMW and McLeod | Keel joins: Its quoting moves first |
| --- | --- | --- | --- | --- |
| Ashgrove Logistics, Quoting and CRM | On Roadmark | On Roadmark | On Roadmark | On Roadmark |
| Ashgrove Logistics, Tracking | by phone and email | On Roadmark | On Roadmark | On Roadmark |
| Ashgrove Logistics, Planning and dispatch | in McLeod | in McLeod | On Roadmark | On Roadmark |
| Ashgrove Logistics, Billing and settlements | in QuickBooks | in QuickBooks | On Roadmark | On Roadmark |
| Ashgrove Logistics, Analytics | in spreadsheets | in spreadsheets | On Roadmark | On Roadmark |
| Ashgrove Freight, Quoting and CRM | in TMW | in TMW | On Roadmark | On Roadmark |
| Ashgrove Freight, Tracking | in TMW | On Roadmark | On Roadmark | On Roadmark |
| Ashgrove Freight, Planning and dispatch | in TMW | On Roadmark | On Roadmark | On Roadmark |
| Ashgrove Freight, Billing and settlements | in TMW | in TMW | On Roadmark | On Roadmark |
| Ashgrove Freight, Analytics | in spreadsheets | in spreadsheets | On Roadmark | On Roadmark |
| Keel Transport, Quoting and CRM | Not in the group yet | Not in the group yet | Not in the group yet | On Roadmark |
| Keel Transport, Tracking | Not in the group yet | Not in the group yet | Not in the group yet | in McLeod |
| Keel Transport, Planning and dispatch | Not in the group yet | Not in the group yet | Not in the group yet | in McLeod |
| Keel Transport, Billing and settlements | Not in the group yet | Not in the group yet | Not in the group yet | in McLeod |
| Keel Transport, Analytics | Not in the group yet | Not in the group yet | Not in the group yet | in spreadsheets |
| Jobs still run in another system | McLeod, TMW, QuickBooks | McLeod, TMW, QuickBooks | Nothing | McLeod |

Divisions that bill under their parent move with it. Choose the migration order that fits your group.

## What we import, and where your history stays.

We import from your current system or a spreadsheet, and map the fields with you before anything goes live.

- **Customers and carriers:** From your current TMS, a spreadsheet, or both.
- **Lanes and rates:** The ones you quote and haul today, from the same sources.
- **Fields mapped with you:** We go through how your fields map to Roadmark's together, before anything goes live.
- **History stays readable:** Your old system stays readable for history after a job or a company moves off it.

An example plan, not a promise for yours: importing takes a day or two, connections are done within a week, and running beside the old TMS on live loads takes two to four weeks. You test each connection with a real load before turning it on for everything.

## Every company moves on its own schedule.

Several companies on different systems is fine. Each one connects on its own, and a company can run on Roadmark or on its own TMS. Roadmark reads the ones that stay where they are.

- **A company you buy joins on the TMS it already runs.** Keel Transport joined the Ashgrove group on Mar 3, 2026 and is still on McLeod. Roadmark reads its loads, and group reports include it from that date only.
- **Its quoting moved to Roadmark first;** dispatch stays on McLeod until Keel is ready.
- **Sister companies haul for each other at internal rates,** even while one of them still dispatches from McLeod.

## What switching this way still asks of you.

Starting beside your TMS takes away the big-bang cutover. It doesn't take away the work, so here's what to plan for.

- **Time for connections:** Your inbox, TMS and ELD. We do the setup with you, but a couple may need your IT team.
- **Two systems for a while:** Until a company moves off McLeod or TMW, it keeps that system. Roadmark bills only the jobs you've switched on; the rest cost nothing here.
- **A session or two of training:** People start on the job they already do: quoting, dispatch or billing. Drafts are there to check, not a new workflow to learn.
- **No setup fee to run beside your TMS:** Any job that runs beside your current TMS has no setup fee. Moving a company fully off its old TMS is a one-time fee of one month of that company's price, waived on annual plans.

## Before you plan a switch.

### Do we have to leave McLeod or TMW?

No. Most companies start by running one job in Roadmark beside McLeod, TMW, TruckMate or another system, and move the rest over on their own schedule: a company, division or lane at a time, or never.

### What if we never move dispatch?

That's fine. Booked orders still land in your TMS with the stops, rate and references on them, dispatch and driver settlements run there as they do today, and Roadmark reads dispatch, status, stops and POD back for tracking and invoices.

### How long does implementation take?

Running one job beside your current TMS is the quicker start, and most of the work is connecting your ELD, email and accounting. Moving Roadmark in as your TMS is a longer, company-by-company rollout that you control.

### How do you migrate our data?

We import customers, carriers, lanes and rates from your current system or a spreadsheet, and map the fields with you before anything goes live. Your old system stays readable for history.

### How much training does our team need?

Most people start on the job they already do (quoting, dispatch or billing) and pick it up in a session or two. Drafts are there to check, not a new workflow to learn from scratch.

### Which systems can Roadmark run beside?

McLeod, TMW.Suite, TruckMate, Aljex, Turvo or your own. Booked orders go out to them through their APIs, and status comes back, with stops, POD and costs where the TMS provides them. Roadmark connects to any TMS with an API: if yours isn't in the integrations directory, tell us what you run and we set up the connection with you.

### Our companies run different systems. Can they move separately?

Yes. Each company connects on its own, and each can run on Roadmark or stay on its own TMS. A company you buy joins on the system it already runs, and moves over when it's ready.

### How is a partial switch priced?

Roadmark starts from $499 USD/month with unlimited users. Start with one workflow beside your current TMS and confirm the setup and price with our team.

### If we stop, can we get our data out?

Yes. Roadmark is month to month with 30 days' notice (or annual, prepaid, with 2 months free). When you leave, you get a full export of your loads, quotes, invoices and documents in open formats.

## Related pages

- [McLeod integration for LoadMaster and PowerBroker](https://roadmark.ai/integrations/mcleod): Run quoting or tracking in Roadmark beside McLeod LoadMaster or PowerBroker. Booked orders go to McLeod; dispatch, status, stops and POD come back.
- [Trimble TMW integration: run Roadmark beside TMW](https://roadmark.ai/integrations/trimble): Run quoting or tracking in Roadmark while dispatch stays in TMW. Booked orders go to TMW; dispatch, status, stops, POD and costs come back.
- [Trimble TruckMate integration through the TruckMate API](https://roadmark.ai/integrations/truckmate): Run quoting or tracking in Roadmark beside TruckMate. Orders go to TruckMate through its REST API; trips, status, stops, POD and costs come back.
- [Roadmark vs McLeod: a side-by-side TMS comparison](https://roadmark.ai/compare/mcleod): Roadmark and McLeod's LoadMaster and PowerBroker, row by row: how routine work gets done, AI features, companies, pricing and deployment.
- [Roadmark vs Trimble TMW: a side-by-side TMS comparison](https://roadmark.ai/compare/trimble-tmw): Roadmark and Trimble's TMW.Suite, TruckMate and Innovative, row by row: AI features, modes, companies, deployment and pricing.
- [McLeod alternatives for carriers and brokers](https://roadmark.ai/alternatives/mcleod-alternatives): Compare alternatives to McLeod for carriers and brokers, including Roadmark: workflows, AI controls, integrations and clear starting pricing.

Companies, people and shipment figures in product examples are fictional. They illustrate workflows and are not customer testimonials or measured results.