Migrating from NueMD to Medi

Short answer

NueMD is being retired on December 31, 2026. AdvancedMD, which acquired NueMD in 2018, has confirmed the platform and its support end on that date, and customers are being directed to migrate to AdvancedMD or leave. For billing companies and independent practices that do not want to move to AdvancedMD's pricing model, the window to plan and run a migration is now. NueMD's data handoff is workable for patient demographics and historical charge records, but payer enrollment, open-claim working state, and ERA routing do not move automatically to any new system. The pattern that protects revenue is a forward-only cutover with a 60 to 90 day legacy A/R closeout running in NueMD before the lights go out. See the NueMD page on AdvancedMD and the NueMD migration page for the official notices.

Why NueMD users are migrating now

NueMD has been an AdvancedMD property since 2018, when the acquisition closed. For several years NueMD kept operating as its own platform, serving small and mid-size practices across internal medicine, pain management, urgent care, and other specialties. It ran its own clearinghouse and gave billing companies a lower-cost alternative to larger RCM suites.

That arrangement is ending. AdvancedMD has announced it will retire NueMD software and support on December 31, 2026. After that date, logins stop working, the NueMD clearinghouse stops routing claims, and ERAs stop arriving. Phone support has already wound down, with users redirected to in-app ticketing and limited live chat. The message to NueMD customers is direct: move to AdvancedMD or move somewhere else.

The forced timeline matters more for a billing company than for a single practice. A billing company managing eight to twenty practices has to coordinate enrollment work, parallel runs, and staff training across every client account before a hard deadline. For any billing company still on NueMD, the planning clock is running.

What comes across and what does not

Not everything NueMD holds will transfer cleanly. Here is an honest map.

The category that bites hardest in a forced sunset is payer enrollment. NueMD runs its own clearinghouse, and when NueMD shuts down the clearinghouse goes with it. Every payer enrollment held through that clearinghouse ends on December 31, 2026. Re-enrollment at Stedi, Medi's clearinghouse, is a separate process for every payer, and the timelines are set by the payers, not by either software vendor.

How to protect legacy A/R

The single most important rule in a NueMD migration: do not try to move open A/R into the new system before it is collected. The open claims, the aged follow-up work, and the denial threads that have run for weeks all carry context inside NueMD that does not survive export. Re-creating that work in a new system on a cutover timeline compresses too much risk into too short a window.

The approach that works is forward-only. New charges go into Medi starting on cutover day. Claims with a date of service before cutover stay in NueMD for 60 to 90 days of legacy A/R closeout. ERAs for pre-cutover claims keep posting in NueMD during that window. Billing staff work down the legacy A/R in NueMD and enter new work in Medi at the same time, and the two systems run in parallel until the legacy bucket is closed.

Because NueMD shuts down entirely on December 31, 2026, the closeout window cannot run past that date. Any claims still open when NueMD closes need to be collected before the deadline, transferred to Medi as active claims with documented working state, or written off if collection probability does not justify the effort. Plan the cutover so the 60 to 90 day closeout ends well before December 31, not on it. A practical target is to complete cutover by October 1, 2026, which leaves about 90 days of legacy A/R closeout inside a working NueMD account before the hard stop. Billing companies with large books or complex payer mixes should target an earlier cutover.

Day-zero cutover checklist

• Export patient demographics, insurance coverages, provider NPIs, and taxonomy codes from NueMD before cutover day
• Verify that the Medi import accepted every patient and provider record, and spot-check at least twenty records for accuracy
• Confirm payer enrollment at Stedi is active for the top three payers by claim volume before the first production claim
• Confirm 837 claim submission with one test claim that passes scrub and reaches the clearinghouse
• Confirm 835 ERA enrollment with one test remittance for at least one payer
• Post all pending ERAs in NueMD before setting the account to read-only for new charges
• Document every open claim in NueMD with its working state, follow-up notes, payer contact history, and next-action date
• Document each in-flight appeal with payer reference number, submission date, appeal level, documents submitted, and next-action deadline
• Set NueMD to read-only for new claim creation for the practice that has cut over
• Confirm new charges for that practice enter Medi only, with a clear date-of-service boundary every biller understands
• Notify the practice that NueMD is read-only for new billing and that legacy claims will be worked there for 60 to 90 days
• Record the cutover date and date-of-service boundary in writing, shared with both the NueMD-side and Medi-side teams

How long do you have?

The hard deadline is December 31, 2026. After that date NueMD logins stop and the clearinghouse goes offline. Every billing company still on NueMD needs to be off it before then, with the legacy A/R closeout finished and verified, not just cut over to a new system. Working backward:

• A 90-day legacy A/R closeout ends December 31 if cutover happens October 1
• Payer enrollment at Stedi takes several weeks per payer at minimum, so enrollment work should start by August for an October cutover
• A billing company with ten clients rolling through August and September needs to start the first migration in early July

For a billing company managing five or more practices, June or July 2026 is the last reasonable start date for orderly migrations. Waiting until September compresses enrollment, parallel-run reconciliation, and staff training into too narrow a window. Contact the Medi team to get enrollment work started, because enrollment timelines are set by payers and cannot be shortened by paying more.

How Medi runs the migration

Medi's migration approach puts operating continuity first. The founder handles migrations directly, and migration pricing is published and per-practice, so a billing company knows the number before the project starts. The shape of every Medi migration is the same regardless of source platform:

• Forward-only cutover, with new charges entering Medi on and after the cutover date
• Legacy A/R closeout, with pre-cutover claims worked down in the source system over 60 to 90 days
• Enrollment carry-over, with Stedi re-enrollment for each payer starting on contract day one
• Practice-by-practice rollout, with the simplest practice first and each cutover informing the next

Migration is free with a 12-month commitment. On a month-to-month plan, migration is a one-time $100 per client practice, capped at $3,000 for the whole book. Data export is always free in standard formats. There is no early-termination fee. The annual commitment is the only lock-in; your data never is.

Medi is a billing-company-first platform. Platform pricing is $20 per client practice per month, with published volume discounts (1 to 25 practices at $20, 26 to 50 at $15, 51 and above at $10 each, marginal). There is no per-provider fee and no annual contract required. EDI usage is separate and unchanged: $0.25 per claim line submitted (dropping to $0.20 at volume), $0.25 per paid ERA line ($0.20 at volume), $0 for denied ERA lines after the first, $0.20 per eligibility check, $0.20 per claim status inquiry, and $1.00 for COB, insurance discovery, and attachment transactions. 277CA acknowledgments and PDF documents are included at no additional cost. The per-practice model means the platform fee scales with the book Medi actually serves, rather than charging a flat rate regardless of size. Medi routes all EDI through Stedi, covering 837 claim submission, 835 ERA, 270/271 eligibility, 276/277 claim status, and 277CA acknowledgments. Coming from NueMD, the clearinghouse change is the biggest operational shift: NueMD's internal clearinghouse and Stedi have different payer connection sets and scrub behavior, so the first two weeks of production include a normal calibration period. Plan for it rather than treating it as a sign something went wrong. The billing company software evaluation guide covers what to verify when evaluating platforms under deadline pressure.

Frequently asked questions

When is NueMD shutting down?

AdvancedMD has confirmed NueMD will be retired on December 31, 2026, with software access and support ending on that date. After December 31, NueMD logins stop working and the clearinghouse no longer routes claims or delivers ERAs. Phone support wound down earlier in 2026, leaving in-app ticketing and limited live chat until the sunset. The official notice is on the NueMD page.

Can I export my NueMD data?

Patient demographics, insurance records, and charge history are accessible through NueMD's reporting tools and can be exported for migration. Historical claim records export for reference. What does not export in usable form is the working state of revenue cycle operations: follow-up notes on open claims, denial investigation threads, in-flight appeal documentation, and per-payer scrub configurations. Request and verify your export before the account closes, since post-shutdown retrieval from a retired platform is not something AdvancedMD has published clear commitments on.

Do I have to move to AdvancedMD?

No. AdvancedMD is the migration path the parent company is promoting, but nothing requires NueMD customers to move there. You can move to any RCM platform that fits your operation. For a billing company that bills for multiple practices, the key question is whether the replacement is built around the billing company as the primary user or around individual practices with a multi-client layer added on top.

What happens to my open claims when NueMD shuts down?

If claims are still open when NueMD closes on December 31, 2026, the platform context for working them disappears with the shutdown. The notes, denial history, payer contact record, and follow-up thread will not be recoverable from a retired system. The protection is to finish the legacy A/R closeout before the deadline and document every open claim's working state in writing before cutover. Claims still open at the deadline have to be re-entered manually in the new system with whatever documentation was preserved, or written off.

Do I need to re-enroll with every payer when I leave NueMD?

Yes. NueMD operates its own clearinghouse, and payer enrollments established through it are tied to NueMD's submitter IDs. Moving to a platform with a different clearinghouse means those enrollment agreements do not carry over. Every payer enrollment for 837 claim submission and 835 ERA receipt has to be re-established at the new clearinghouse. Medi routes through Stedi. Medicare and state Medicaid take the longest; commercial payers vary. Start enrollment the day the contract is signed.

Is the NueMD situation like the Tebra migration?

The mechanics are the same, but the timeline pressure is different. Tebra is not being sunset on a hard date; NueMD is. That makes the NueMD migration more time-bound and less negotiable. The Tebra migration guide covers the forward-only approach, legacy A/R closeout, and payer enrollment in detail, and those sections apply here. The NueMD-specific risk is the deadline: there is no option to extend the closeout past December 31, 2026, or to keep a read-only NueMD account open for historical access after that date.