FMCSA MOTUS: Migrating From URS, Common Issues and FAQs

FMCSA is replacing the Unified Registration System (URS) with a new online registration system called MOTUS. For a compliance team the practical question is not what MOTUS is named after — it is what you have to do, in what order, and what breaks if you get it wrong.

This covers both halves: what FMCSA announced and requires, and the problems carriers have actually run into since launch.

What the notice says

In a Federal Register notice published April 29, 2026, FMCSA announced MOTUS and explained how using it satisfies the statutory and regulatory requirements URS covered. FMCSA says MOTUS will "simplify the registration process, streamline identification, improve the user experience, and incorporate enhanced verification tools."

The rollout has two phases:

• Phase I, released December 8, 2025, let supporting companies create accounts. FMCSA defines supporting companies as blanket companies (Form BOC-3 process-agent filers), financial responsibility filers such as insurance and surety companies, and transportation service providers that file on behalf of carriers, brokers and freight forwarders.
• Phase II opens MOTUS to all regulated entities. This is the phase that reaches every carrier, broker and freight forwarder.

MOTUS satisfies the statutory mandate for a unified registration system, and FMCSA will sunset:

• URS, for new USDOT number and operating authority applications
• The registration components of the Motor Carrier Management Information System (MCMIS)
• The former Interstate Commerce Commission Licensing and Insurance system, which dates to 1994

Who this affects, and when

If your business registers with FMCSA in any capacity, MOTUS affects you — motor carriers, brokers, freight forwarders, and the supporting companies that gained access in Phase I.

New applicants and existing registrants are both in scope, but the timing differs. New USDOT number and operating authority applications are the functions FMCSA moved off URS first.

Expect a transitional period where some functions live in MOTUS and others still route through legacy tools. The safe working assumption is that anything new goes through MOTUS while established records may still be reachable through older interfaces until they are migrated.

What moves to MOTUS, and what does not

MOTUS covers registration: new USDOT numbers, operating authority applications, company records, and the identity and company verification that sits around them.

It is not a replacement for your safety data or your compliance obligations. SMS, inspection and crash records, the Clearinghouse, and your drug and alcohol program are all unaffected. Nothing about MOTUS changes what you have to do as a carrier — only where you go to register and maintain your registration.

Why a registration system change deserves attention

Registering in MOTUS is the foundation that the rest of your authority sits on. A registration system is not usually interesting. This one matters for three reasons:

It changes who can act on your behalf. Access moves toward verified user accounts and explicit company permissions rather than a shared PIN, which means the person who has historically filed your updates may not automatically have access.

It changes identity verification, introducing Login.gov into a workflow that did not previously require it.

And it creates a window in which a filing can be delayed by the system rather than by you — which matters if a renewal falls due during the transition.

Migration checklist

Now — identify who in your company will hold the MOTUS account. This should be someone permanent with authority to make filings, not whoever happens to be available. Get their Login.gov identity verification completed before you need it, because that step has been a common source of delay.

Now — check that your company record is accurate as FMCSA holds it. Claiming an existing company in MOTUS matches against FMCSA's records, so an outdated address or a mismatched legal name will block you. Fix discrepancies before you attempt the claim, not during.

Before any renewal falls due — confirm which system handles it and start early. Do not assume a transitional filing will complete on the timeline you are used to.

If you use a filer or service provider — confirm they have Phase I access and know how they will be granted permissions on your company record.

Keep a record of every attempt. See below.

Your URS-to-MOTUS migration checklist: what to do and by when

1. Create your MOTUS account in the correct entity role. Register as the right type: motor carrier, broker, freight forwarder, or supporting company. The role determines what you can file, so getting it right at account creation is important.
2. Verify that your exact legal name and USDOT number match your existing records. Name mismatches are the most common cause of failed identity verification. Confirm the legal name in MOTUS matches what is on file in MCMIS and on your operating authority before you rely on the account.
3. Confirm your BOC-3 process agent and insurance filers are linked. If your blanket company filed your BOC-3 or your insurer files your financial responsibility, confirm those supporting-company relationships are intact in the new system so a lapse does not appear during cutover.
4. Check which renewals or filings are due during the transition window. If a biennial update, an authority action, or a financial-responsibility filing falls during the migration, handle it deliberately and confirm the correct system before submitting.
5. Designate an internal owner. Assign one person responsibility for the MOTUS account, credentials, and filings. Shared, unowned logins are how registrations drift.
6. Document your migration. Record when you created the account, what you verified, and what you filed. A short migration log is useful if a filing is questioned later.
7. Know what to do if you hit a duplicate-account or name-mismatch error. Do not create a second account to work around a verification failure. Resolve the underlying record first, because duplicate entities create downstream problems that are harder to unwind than the original error.

Common issues since launch

No large technology rollout is perfect and MOTUS has been no exception. FMCSA has acknowledged several issues and has continued releasing updates as they are identified.

Difficulty claiming an existing company. Usually caused by outdated company records, or information that no longer matches what FMCSA holds on file.

Identity verification delays. Some users have had trouble completing Login.gov verification, or accessing MOTUS for the first time.

Insurance and operating authority workflow delays. Certain authority and insurance workflows ran slowly in the early stages. FMCSA has prioritized these.

If you hit any of these, do not submit multiple requests for the same issue — duplicates slow the queue. Instead:

• Save screenshots of any error messages
• Keep confirmation emails and support ticket numbers
• Note when you attempted the transaction
• Follow FMCSA's current guidance for technical support

That documentation matters. If a filing or update was late because of a system issue rather than because you were late, the record is what demonstrates it.

Transition failure modes

• Assuming your PIN still governs access. Access is moving to verified accounts and company permissions
• Letting one person's unverified Login.gov account block the whole company
• Attempting a company claim against stale FMCSA records and treating the rejection as a system fault
• Leaving a renewal to the last week during a transition
• Losing the audit trail when a filing is delayed by the system

Frequently asked questions

Do I have to switch to MOTUS right now? If you are making a new registration filing, yes — that is the function FMCSA moved first. Existing registrants should get accounts and verification in place ahead of their next filing rather than waiting for a deadline.

Do I still need my USDOT PIN? In some cases. FMCSA still maintains PIN-related resources and some legacy processes continue to rely on them. For most registration activity MOTUS is shifting access toward verified user accounts and company permissions rather than PINs alone.

What happens to my existing URS account? URS is being sunset for new USDOT number and operating authority applications, along with the MCMIS registration components and the legacy ICC Licensing and Insurance system. Your registration data persists; the interface you use to manage it changes.

Do I need to create a new registration if I already have a USDOT number? No. You claim your existing company in MOTUS rather than registering afresh. That claim matches against FMCSA's records, which is why accurate company data matters.

Will my USDOT number change? No. MOTUS changes the registration system, not your identifier.

Can multiple people access the same company? Yes. MOTUS is built around company permissions, so more than one verified user can be granted access — which is an improvement on a single shared PIN.

What if my company information is incorrect? Correct it before attempting a company claim. A mismatch between what you enter and what FMCSA holds is the most common cause of a failed claim.

What if a renewal is due during the transition? Start early and confirm which system handles it. Keep evidence of every attempt in case a system issue delays a filing you submitted on time.

Who in my company should create the MOTUS account? Someone permanent with authority to make filings, whose Login.gov identity verification is already complete. Not whoever is available on the day.

What if my legal name does not match across systems? Resolve the mismatch with FMCSA before attempting the claim. Name discrepancies are a frequent blocker.

Is SAFER still available? Yes. SAFER remains available as a public record lookup.

Sources

• Federal Register notice, 29 April 2026 — FMCSA announcement of MOTUS
• motus.dot.gov
• Login.gov