When a carrier moves states, the USDOT follows them — but the SOS doesn't

A common scenario

A trucking company is incorporated in Pennsylvania, operating for six years, with USDOT 1234567 and MC-987654. The owners move to Florida for cost-of-living reasons. They:

• Form a new Florida LLC.
• Update the MCS-150 with the new Florida principal address.
• Update their CDL addresses and vehicle registrations.
• Cancel the Pennsylvania LLC (or let it lapse).

The USDOT does not change. The MC does not change. The carrier is the same carrier, with the same federal record, just operating from a different state.

For a credit underwriter pulling this borrower, the FMCSA record shows a 6-year operating history under a single USDOT. The Florida SOS record shows an entity formed last year. The Pennsylvania SOS record shows an entity recently dissolved or lapsed.

If you only check one state, you get one piece of the picture. Specifically:

• FMCSA alone → 6-year history, looks great.
• Florida SOS alone → 1-year-old entity, looks like a new business.
• Pennsylvania SOS alone → dissolved entity, looks like a closed business.

All three are facts about the same operator. Combined, they tell you the carrier has 6 years of operating history and recently moved states. That’s a fine credit story. Each individually is incomplete or misleading.

Why the USDOT persists

USDOT numbers are issued by FMCSA, which is a federal agency. The number is tied to a specific operating entity (identified by its legal name and tax ID) and follows that entity across state-of-domicile changes. Selling the entity, dissolving the entity, or restructuring transfers the question of whether the new owner can also use the USDOT — that’s an FMCSA-determination question — but a simple change of principal address from one state to another does not require a new USDOT.

The MCS-150 update captures the address change. After the update, the SAFER record reflects the new principal address in the new state. The USDOT, MC, BASIC scores, crash history, MCS-150 filing history — all persist across the move.

This is by design. FMCSA’s safety regime is national. Carriers that hold safety records under one USDOT shouldn’t be able to abandon them by moving states.

Why the SOS entity often does not persist

State SOS registration is per-state. A carrier domiciled in Pennsylvania who moves operations to Florida may:

• Re-incorporate in Florida. The Pennsylvania entity gets dissolved or allowed to lapse. The Florida entity is brand new. Most common pattern.
• Convert the Pennsylvania entity to Florida. Some states permit “conversion” filings where an entity domiciles in a new state without dissolving. Less common because not all state pairs support the bidirectional conversion.
• Domesticate. Similar to conversion but a separate procedure under state law in the receiving state. Florida has a domestication procedure; many other states do.
• Foreign-qualify the Pennsylvania entity into Florida. Keep the Pennsylvania domestic entity and register it as a foreign entity in Florida. Common if the operator expects to maintain operations in both states.

The most common pattern by volume is the first one: re-incorporate fresh in the new state. This is cheap, clean, and clear of any historical PA-state liability. The downside is exactly what creates the verification pattern: the new Florida entity has no operating history of its own, even though the actual operating business has six years of history.

The verification workflow that catches it

The cross-state pattern is detectable if the verification workflow includes:

1. USDOT lookup. Pull FMCSA SAFER. Note the carrier name, MCS-150 date, and historical principal address.
2. State-of-current-domicile SOS lookup. Search the SOS in the state of the current principal address. Find the current entity.
3. State-of-prior-domicile SOS lookup. Search the SOS in the state of any historical principal address shown on the USDOT history. Find any prior entities.
4. Officer cross-reference. Confirm that the principals on the current entity are the same as the principals on the prior entity. This is the link that ties the two together.

When the officer names match across the prior and current entities and the USDOT spans both, the cross-state move is confirmed. The carrier’s actual operating history is the longer of the two — the USDOT span.

The thing that breaks this workflow

The workflow above breaks when there is no recent MCS-150 update reflecting the address change. If the carrier moved operationally but hasn’t updated the MCS-150, the FMCSA record still shows the prior-state address. The SOS in the current state doesn’t have a corresponding entity yet. The carrier is operating in a third state that no record reflects.

This is more common than it sounds. MCS-150 updates are not top-of-mind for operators in the middle of a move. The 24-month update cycle gives a lot of slack. A carrier can operate from a new state for a year before the next scheduled MCS-150 update without anything in the public record reflecting the move.

For an underwriter, the only signal is a mismatch between the credit application (which reports the current operating address) and the SAFER record (which still reports the prior). The mismatch is benign if explained by “we moved and haven’t updated yet” and concerning if not.

When it does indicate something worse

A cross-state move that doesn’t follow the normal pattern is a chameleon-carrier signal. Specifically:

• New USDOT issued in the new state recently.
• Old USDOT in the prior state recently revoked or marked out of service.
• Same principals across both.

That’s a carrier that closed an MC under safety pressure and reopened under a new MC in a new state. The cross-state SOS check catches this because the same principal name appears on both the closed and the new entity, the addresses are in different states, and the timing is suspicious.

See the chameleon-carrier post for the full pattern. The cross-state SOS check is one of the strongest single tests for it.

What this means for you

For trucking deals, verify across states, not just in the current state of operation. The USDOT is the persistent record; the SOS data is per-state. The combination tells the actual operating story; either one alone tells part of it. When the cross-state pattern is benign (move), the diligence is satisfied with the officer match. When the pattern is suspicious (closed-and-reopened MC), the chameleon flag fires.

A VerifySOS lookup on a trucking deal automatically cross-references the carrier’s principals against SOS records in the USDOT-historical states. The packet identifies prior-state entities under the same principals. Developers get the cross-state entity list and the migration-pattern classification via /api/v1/lookup.