The entity migration: re-pointing every enrollment without a gap

What actually has to move, and why it isn't automatic

Nothing about forming a new entity automatically carries your enrollments over. Medicare, Medicaid, CAQH, and every commercial payer you're contracted with each hold a record anchored to your Social Security number and your individual NPI, and none of them watch your state's business-formation filing for changes — each one needs its own separate update, in its own system, on its own timeline.

The practical risk isn't the paperwork itself; it's the gap. Deactivate or abandon the old SSN-based enrollment before the new entity's enrollment is confirmed active, and you can end up unable to bill under either one for a stretch — which is why sequencing this migration matters as much as completing it.

Your individual NPI doesn't change either, which is easy to assume it should. The new entity typically needs its own organizational NPI, existing alongside your personal one rather than replacing it — one more record that has to be pointed at the right systems during this same migration, not swapped in for the number you've always had.

Before you touch enrollment: the entity and the EIN come first

Enrollment paperwork is the second half of this migration, not the first. The entity itself — most often a PLLC for a licensed solo clinician — has to exist as a formed, state-recognized business before any payer will enroll it, and the entity decision itself (PLLC vs. S-corp vs. staying a sole proprietor) is worth settling deliberately rather than backing into because a template said so.

Once the entity is formed, the IRS issues it its own Employer Identification Number, separate from your personal Social Security number, and that new EIN becomes the anchor every downstream enrollment update actually points to. Get the entity name and the EIN exactly right and finalized before starting a single payer update — correcting a typo in the entity name after enrollments are already in motion multiplies the work rather than fixing it once.

Medicare: enroll the entity, then reassign your billing rights to it

Medicare enrollment for the new entity is transacted in PECOS 1Ref 1Centers for Medicare & Medicaid Services (2026).Medicare PECOS.That the new entity's Medicare enrollment, and the reassignment of an individual's billing rights to it, is transacted in PECOS., the same system you used for your original individual enrollment, but it's a separate enrollment action: the entity gets enrolled as its own organizational supplier, and only after that's approved do you file the paperwork that reassigns your individual billing rights to it. Skipping straight to reassignment before the entity itself is enrolled is a common way this stalls.

CMS publishes the enrollment pathway with its own effective-date and retrospective-billing rules for exactly this kind of change 2Ref 2Centers for Medicare & Medicaid Services (2026).Provider and Supplier Enrollment.That CMS's enrollment pathway sets the effective-date and retrospective-billing rules that determine whether a gap exists during an entity migration., and those rules are what determine whether there's a real gap in what you can bill for — plan the entity's enrollment date and the reassignment date together, rather than assuming one flows immediately from the other.

CAQH: a new TIN usually means a new profile, not an edit

CAQH operates the provider data portal most commercial payers pull from during credentialing, and it organizes profiles around a provider-TIN combination rather than the individual alone 3Ref 3CAQH (2026).CAQH.That CAQH operates the provider data portal most commercial payers pull from, organizing profiles around a provider-TIN combination.. A new EIN attached to a new entity is, from CAQH's perspective, a new billing identity — which in practice usually means creating a new CAQH profile at the same sign-in point you used originally 4Ref 4CAQH (2026).CAQH Provider Data Portal Sign In.The sign-in point where a provider creates a new CAQH profile under a new TIN after an entity migration., not editing the old one to reflect a name change.

Moving your attestation, your malpractice documentation, and your work history into the new profile takes real time, and every payer that credentials off CAQH won't see the new entity until that profile is complete and re-attested — start this step early, not after Medicare's already moved.

Commercial payers: a notification, or a whole new contract?

How a commercial payer treats a TIN change varies payer to payer more than any other step in this migration — some accept a written notification and an updated W-9; others treat a new entity as a new contracting event entirely, requiring a fresh credentialing application before the new TIN can bill under your existing rates and terms. Ask each payer directly which path applies rather than assuming the smoothest one.

A TIN change can also trigger fresh primary-source verification under the credentialing framework most health plans follow 5Ref 5National Committee for Quality Assurance (2026).Credentialing — NCQA.That NCQA's primary-source-verification framework can be re-triggered by a TIN change even when the underlying license didn't change., even for a clinician who was fully credentialed under the old entity days earlier — the identity attached to the license changed, from the payer's system's perspective, even though the license itself didn't.

Medicaid: the state's own process, on the state's own timeline

Medicaid enrollment runs through your state's own agency rather than a shared federal system 6Ref 6Centers for Medicare & Medicaid Services (2026).Provider Enrollment.That Medicaid provider enrollment is state-administered on its own portal, separate from Medicare and CAQH, requiring its own entity-migration submission., so the entity migration has to happen there too, as its own separate submission, with its own required documents and its own processing time — nothing about updating Medicare or CAQH reaches your state Medicaid file automatically.

Build in extra lead time for this step specifically if Medicaid patients are a meaningful part of your caseload: state agencies vary widely in how quickly they process an entity or TIN change, and a gap here affects real patients waiting on authorizations, not just your own cash flow.

Confirm the effective date the state assigns the new enrollment before you stop billing under the old one, the same discipline that matters with Medicare — a Medicaid agency that processes the change slower than expected is not a reason to guess at continuity, it's a reason to call and confirm.

Sequencing the migration so nothing lapses

Treat this as an overlap, not a handoff: keep the old SSN-based enrollment active at every payer until its replacement is confirmed, not just submitted, and only deactivate the old one after you've actually been paid once under the new entity. Confirmation of submission and confirmation of approval are different things, and the gap between them is exactly where billing lapses happen.

Work through payers roughly in order of how much of your revenue each represents, since a delay with your highest-volume payer costs the most if something goes wrong. Update your EIN on everything — every payer file, every state Medicaid record, every business account tied to billing — as you go, rather than batching it for the end, so you're never holding two different identities across the systems that are supposed to agree with each other.