Motus USDOT Registration System | FMCSA Migration Guide 2026

Motus is FMCSA's new online registration system, announced in Federal Register notice FR-2026-08334 on April 29, 2026. The name derives from the Latin word for "movement" or "progress." Motus consolidates three legacy platforms: the Unified Registration System (URS) that was mandated by MAP-21 in 2012 and became the interface for USDOT and operating-authority applications, the registration components of the Motor Carrier Management Information System (MCMIS), and the legacy Interstate Commerce Commission Licensing and Insurance (L&I) system that dates to 1994. Motus is not a new regulatory requirement; it is an operational replacement for the front-end interfaces carriers, brokers, freight forwarders, and supporting companies use to interact with FMCSA registration. The system introduces Login.gov authentication with multi-factor verification, IDEMIA-based identity proofing, transaction-oriented workflows that replace the older form-based navigation, real-time data validation, and mobile-ready filing capability. Existing USDOT numbers, MC numbers, and registration records continue without modification — Motus is the new door, not a new record.

Motus rolled out in phases. Phase I launched December 8, 2025 for "supporting companies" — the BOC-3 process agents, insurance and surety companies, and transportation service providers that file on behalf of registered entities. If your fleet uses a process agent, your BOC-3 filings are already routing through their Motus interface. Phase II opened during the second quarter of 2026 to all regulated entities: motor carriers, brokers, freight forwarders, and owner-operators. The exact date URS will sunset for new applications has not yet been published in a Federal Register notice — FMCSA has said only that URS will be retired once Phase II is stable, which is expected in the third quarter of 2026 or later. In practice, most carriers will encounter Motus the next time they file for a new USDOT number, apply for operating authority, complete an MCS-150 biennial update, or update BOC-3 process-agent designations. Existing registrations remain valid throughout the transition — you don't need to refile anything currently on record. But your next filing event will route through Motus rather than URS, and the account setup and identity verification steps are prerequisites, not part of the filing itself.

Yes, in most cases. Motus authenticates users through Login.gov, which is the federal government's single sign-on service, and adds IDEMIA-based identity verification on top. If you already have a Login.gov account from another federal service, that account will work for Motus, but you'll still need to complete IDEMIA identity proofing specifically for Motus access. If you don't have a Login.gov account, you'll need to create one. The account must be tied to the Portal Company Official designated for your FMCSA registration — a named individual who owns account authority for the entity. FMCSA has indicated that account claiming in Motus uses the same email as the FMCSA Portal Login.gov email, so if the person on your Portal record is a former employee or the email has bounced, you should update it now rather than at the first Motus filing. Multi-factor authentication is required under federal cybersecurity policy. Enterprise fleets running multiple authorities across affiliated carriers should expect to validate credential access, authorization workflows, and inter-entity permissions early — the one-to-one mapping from URS to Motus is straightforward but the credential model may differ from what fleets are used to.

No. The MCS-150 biennial update requirement under 49 CFR §390.19 continues without modification. Every FMCSA-registered entity must file an MCS-150 update every 24 months based on the last two digits of its USDOT number, even when company information hasn't changed. What changes is the interface: instead of navigating the URS or FMCSA Portal MCS-150 workflow, filers will now complete the biennial update through the Motus transaction-oriented workflow. The underlying data collected is the same — principal place of business, mailing address, operational classification, cargo types, vehicle counts, driver counts — and the legal record of authority remains the FMCSA-held filing regardless of which front end submitted it. Two operational differences to plan for: first, Motus's real-time validation may flag data inconsistencies that URS silently accepted, so validate your current MCS-150 record proactively rather than discovering issues on deadline day. Second, the transaction-oriented workflow may not surface the MCS-150 form name explicitly — you may see "update carrier information" or a similar task label instead of an MCS-150 form reference. It's the same filing under the hood.

Both identifiers continue exactly as they are. Motus is a system replacement, not a renumbering. Your existing USDOT number remains your USDOT number in Motus, your MC number (if you have operating authority) remains your MC number, and all associated records — safety rating, CSA scores, inspection history, crash history, insurance filings — move with the identifier. The Federal Register notice was explicit that the initial Motus release does not include MC/FF docket number elimination, safety registration changes, or new registration substantive requirements. Some industry commentary has speculated about eventual consolidation of MC numbers into a USDOT-only identity model as part of longer-term FMCSA modernization, but no such change is currently effective or scheduled under Motus. The practical implication: brokers, shippers, insurers, and enforcement systems that rely on your USDOT and MC identifiers continue to see the same numbers. Your carrier profile, safety data, and operating history are preserved. What changes is who logs in, how identity is verified, and which interface holds the transaction — not who you are or what you're authorized to do on the road.