Skip to main content
Operations · DSO & GROUPS

Dental Practice Acquisition IT Integration: 90 Days After Closing

The deal has closed. On Monday the acquired office opens under your name, while the server, the domain, the phone account and every vendor login still sit in the seller's, and the team has never met your IT provider. Diligence told you what you bought, not what to do first.

This guide is the second half of the acquisition. The first half, what to check before you sign, is in our dental practice acquisition IT due diligence checklist, which also holds the Day 1 to Day 30 handover worksheet. This page starts where that worksheet ends: the workstreams, the decisions, the cut-over weekend, who does what, and the tests that let you call the office integrated. It is written for the person running the integration at a group of any size, from a second office to a thirtieth.

In this guide
  1. What does IT integration of an acquired dental practice involve?
  2. Migrate, keep or bridge: which practice-software path fits the acquired office?
  3. The week-by-week integration checklist
  4. How do you take over identity, email and the domain without losing messages?
  5. How do you move the phone numbers and the fax line?
  6. What should the network and firewall standard look like at the acquired office?
  7. What is the minimum security baseline before the office joins shared systems?
  8. How do you take over vendor contracts, licences and business associate agreements?
  9. How do you get the acquired staff signed in and supported?
  10. What does the cut-over weekend plan look like?
  11. Who does what: the RACI for an acquired office
  12. How do you know the acquired office is integrated?
  13. What does the integration cost, and where do the lines sit?
  14. The IT side: how a provider runs the 90 days
  15. What to ask your IT provider before the acquired office joins the group
  16. How Legend Networking works with groups that acquire offices
  17. Frequently asked questions
  18. The bottom line

What does IT integration of an acquired dental practice involve?

IT integration means moving every system the acquired office runs on, from the server to the fax line, from the seller's control to yours, and then from "as found" to your group's standard, without stopping patient care. It is nine workstreams with their own owners and tests, not one project called "the IT changeover".

Use the table as the index to the rest of this page. Each workstream has a usual window, a "done" test and a section below. Most groups run three or four of them in the same week, so the RACI near the end matters as much as the order.

WorkstreamDone whenUsual windowSection
1. Access and backupsYour administrators can sign in to every system; a restore has been witnessedWeek 1Week-by-week checklist
2. Practice-software pathMigrate, keep or bridge is written down with a date and an ownerDecision by week 2; execution laterMigrate, keep or bridge
3. Identity, email and domainEvery person has a named account with multi-factor sign-in; mail flows under your controlWeeks 2 to 4Identity, email and the domain
4. Phones and numbersNumbers ported or scheduled, fax handled, call flow documentedWeeks 3 to 8Phone numbers and the fax line
5. Network and firewallThe office matches the group template and has a site documentWeeks 4 to 7Network and firewall standard
6. Security baselineEndpoint detection, backup, patching and access controls report to your consoleWeeks 2 to 8Security baseline
7. Vendors, licences and agreementsEvery vendor is in the register with a status; nothing renews unseenWeeks 1 to 9Vendor contracts and agreements
8. Staff onboardingEach person signs in as themselves and knows where help requests goWeeks 2 to 5Onboarding the acquired team
9. Acceptance and handoverThe acceptance sheet passes; exceptions have owners and datesWeeks 12 to 13How you know it is integrated

Two things are deliberately not on the list. The pre-close checks (who owns the data, whether the backups restore, what the incumbent IT contract says) belong to due diligence, and if they were skipped they become week-one work. And the practice-software conversion itself is scheduled by this plan but run by its own runbook, our dental PMS migration cutover plan, because a conversion weekend has different risks from an infrastructure weekend.

Migrate, keep or bridge: which practice-software path fits the acquired office?

Decide the practice-software path in writing by the end of week two, but do not execute a conversion before day 30. Three paths exist: migrate the office onto the group's system, keep its current system with your controls around it, or bridge, keeping it for a defined period while reporting and preparation run in parallel. The table decides between them.

CriterionMigrate now (schedule a conversion inside the 90 days)Keep (for at least a year, reviewed)Bridge (keep for a defined period, then convert)
Same vendor and version as the groupNot needed; a database merge or move may be enoughFitsFits
Different vendor from the group standardFits when the group has converted before and staff capacity existsFits for a single office with stable staffFits for most groups: convert after the office is stable
Imaging bridge and sensorsMust be tested against the target software before a date is setNo changeTest during the bridge period, not on the weekend
Data export rights confirmed with the vendorRequired before any dateConfirm anyway; you will need it laterRequired before the bridge period ends
Clinical and front-desk staff turnover in the first 90 daysHigh turnover argues against a conversion nowFitsFits
Contract end date on the current softwareA near end date can force the pace; read the termsA long remaining term argues for keepAlign the conversion date with the term end
Group reporting needsMet after conversionMet by exports or a reporting toolMet by exports during the bridge
Best forGroups on one platform with a tested conversion playbookA second or third office whose software works and whose team is settledGroups with mixed systems that want one platform within a year

A bridge is not a technology; it is a decision with a date. The office keeps its software, your IT provider puts the group's backup, security and access controls around it, the billing team gets the reports it needs from exports, and the conversion is scheduled for a quiet month after the staff know you. Open Dental, for example, publishes a conversions service that includes "Data Conversions: Convert a database used by other software to an Open Dental Database" and "Database Merges: Combine multiple databases into a single database," and says that "Fees vary depending on the software you are converting from, conversion service, and other factors" (read 18 November 2026). Dentrix and Eaglesoft offices should ask Henry Schein One or Patterson in writing what converts, what is exported and on what timeline; their public pages do not state it in a form an integration lead can plan from.

Whatever the path, two things never move on closing day: the practice-management database and the imaging store. A conversion forced into the first week leaves ledgers, accounts receivable or image links behind and gives the new team no way to tell a conversion problem from a handover problem. If you are standardizing the whole group, the order of layers is in our guide to DSO technology strategy; the wider move itself is in the dental software migration checklist.

The week-by-week integration checklist

The checklist runs 13 weeks. Weeks one to four are about control and identity, five to eight about phones, network and security, nine to thirteen about vendors, the software decision and acceptance. Every row has evidence to file, because the next acquisition, your insurer and a future buyer will ask for it.

WeekWorkEvidence to fileExit test
1Receive and test every administrator credential; create your own admin accounts; rotate the seller's; list every remote-access tool and remove the ones nobody can account for; install the group's monitoring agent; watch the practice database and some images come back from backup; confirm a backup copy exists off the premises; give staff a single help route for week oneCredential inventory with change dates; remote-tool removal list; dated restore record; agent countYou can sign in as administrator everywhere; a restore has worked in front of a witness
2Write the practice-software decision (migrate, keep or bridge) with a date; inventory hardware with operating-system versions and ages; collect the vendor list, the phone bill, the internet contract and the registrar login; start named accounts in your directoryDecision memo; hardware inventory; vendor register draftThe decision is signed; every workstation and server is on the inventory
3Take control of the domain registrar and DNS; decide new mailboxes or a tenant migration; open the phone port: request the customer service record, confirm the account holder, prepare the letter of authorization; collect business associate agreements in forceRegistrar and DNS change log; port request date; agreements on fileYou control DNS; the port request is accepted or its blocker is named
4Move mail routing to your tenant with forwarding from the old addresses; turn on multi-factor sign-in for every account; swap shared logins for personal ones wherever the software supports it; delete accounts belonging to former staffMail-flow test (send and receive); account list with multi-factor statusEvery current employee signs in as themselves; no former employee can
5Train the team on the new sign-in, the ticket path and the group's security habits; publish the one-page "what changed on Monday" sheet; deploy endpoint detection to every machine; set patch windowsTraining attendance; endpoint console showing every deviceEvery device reports to the console
6Plan the network cut-over weekend: firewall, switches, Wi-Fi, address plan, static addresses for imaging devices; order equipment; book the window around the appointment bookSite design; equipment order; written change windowThe design is approved and the window is agreed with the office manager
7Network cut-over weekend (section below); write the site document; label the closetWeekend runbook with results; site documentMonday smoke tests pass in every room
8Port the phone numbers or confirm the firm port date; set call flow, voicemail and fax handling; test inbound and outbound on every line; cancel nothing until the port is confirmedPort confirmation; call-flow document; test logThe main number rings on the new system and the old carrier confirms the port
9Work the vendor register: assignment or new agreement for each vendor kept; termination notices for duplicates; licence transfers for practice and imaging software; confirm payer and clearinghouse portal ownersRegister with a status per vendor; copies of noticesNo vendor renews unseen; every portal has a named owner
10Replace or rebuild workstations and servers marked "replace in 90 days"; retire anything on an unsupported operating system or put a dated plan on it; second test restore from the group backupReplacement log; restore recordThe office appears in the group backup and security reports with no unsupported device unaccounted for
11If the path is migrate, run the test conversion and set the go-live date with the cutover runbook; if keep or bridge, set the review date and the reporting methodTest conversion report or review memoA conversion date exists, or a written reason why not
12Run the acceptance sheet (below); open the exception register for anything that failed with an owner and a dateCompleted acceptance sheet; exception registerEvery row is pass or has an exception entry
13Handover meeting: what changed, what did not, what is scheduled; add the office to the monthly group report; file the evidence folderHandover memo; first monthly report with the office on itThe office is in the monthly report and nobody is waiting on an unnamed task

The order can compress. An office that already runs your practice software, with supported hardware and a cooperative seller, can finish in eight weeks. An office with an out-of-support server, a shared password on every workstation and a seller who kept the registrar login will take longer, and the order still holds. Hidden lines that appear during weeks nine and ten (per-location software fees, a second internet circuit, a forgotten phone line) are reconciled line by line in hidden IT costs in dental groups.

How do you take over identity, email and the domain without losing messages?

Take the registrar and DNS first, then decide between new mailboxes with forwarding and a tenant-to-tenant migration, then move mail routing in a planned window with a send-and-receive test. Every person gets a named account with multi-factor sign-in before the office joins shared systems, and shared logins are replaced where the software allows.

The registrar and DNS. The domain controls the office's email and website. Confirm whose name the registrar account is in, move it to your entity's account, and record every DNS record before you change any. If the seller keeps the domain for any reason, the purchase documents should say so and your attorney should have read that clause; the integration lead's job is to know it before week three.

New mailboxes or a tenant migration. For a one- or two-doctor office with a handful of mailboxes, creating new mailboxes in the group's tenant and forwarding the old addresses for a defined period is simpler and leaves less to go wrong. For a larger office with shared mailboxes, calendars and years of mail that staff rely on, a tenant-to-tenant migration moves the content. Microsoft's own planning guidance says to "Determine whether users keep their existing UPN or receive a new one" and to "Plan for any domain transfers between tenants," and notes the sequencing rule that "Teams content depends on Exchange mailboxes: Migrate mailboxes before or alongside Teams" (Microsoft Learn, read 18 November 2026). Either way, the test is the same: a message sent to the old address and to the new one both arrive, and a message sent from the office arrives with the right name on it. Licence tiers and tenant setup are compared in Microsoft 365 for dental offices.

Named accounts. The HIPAA Security Rule's technical safeguards include a required implementation specification to "Assign a unique name and/or number for identifying and tracking user identity" (45 CFR 164.312(a)(2)(i)). That is a description of the safeguard, not a reading of the rule for your transaction. In practice it means the "Front Desk" login the office has used for a decade is replaced by one account per person, in your directory, so that access can be granted, logged and removed by name.

Multi-factor sign-in. CISA describes multifactor authentication as "a layered approach to securing your online accounts and the data they contain." Turn it on for email, the remote-access tool, the practice software where it is offered, and every payer and vendor portal. Portals are where an acquired office's shared "billing" login usually survives longest; the fix is in our post on payer portal logins and MFA for dental groups.

What to leave alone for now. Do not rename the practice's public email addresses, change the website or move the domain's nameservers in the same week as the phone port or the network weekend. One identity change per week is enough for a front desk that is also learning a new owner.

How do you move the phone numbers and the fax line?

Treat the phone numbers as an asset with its own workstream: confirm who holds the carrier account, get a current bill and the account PIN, submit a signed letter of authorization, set call forwarding for the port window, test every line, and cancel the old service only after the new carrier confirms the port. Never cancel first.

A lost main number is the integration failure patients notice. The sequence that avoids it:

    1. Find the account holder. The carrier will only port a number on the instruction of the account holder of record. If that is the seller or the seller's entity, the letter of authorization needs their signature, and the purchase documents should already say the numbers transfer with the practice.
    1. Pull the customer service record. Ask the current carrier for the record that lists every number, line and feature on the account. Offices find forgotten lines here: an alarm line, an old fax, a credit-card terminal line.
    1. Match the details exactly. A mismatched address, a missing suite number or a wrong account number is enough to get a port request rejected, and the new carrier submits exactly what you give it.
    1. Know the timing. For the simplest case, FCC rules require that carriers "must complete a simple wireline-to-wireline or simple intermodal port request within one business day unless a longer period is requested by the new provider or by the customer" (47 CFR 52.35(a)). A business account with several numbers, a fax line and features is usually not a simple port, and the carriers set a longer window; ask the new carrier for the firm date in writing and plan week eight around it.
    1. Forward during the window. Set the old carrier to forward to a number you control while the port is pending, so a port that completes at midnight does not strand a morning of calls.
    1. Decide the fax before the port. Many offices still receive referrals and insurance documents by fax. Move it to a fax service or keep a line for it, but decide before the port date, not after the line goes quiet. Our guide to replacing old copper phone lines in a dental office covers the options.
    1. Test every line, both directions. Inbound to the main number, outbound caller ID shows the practice name, voicemail, after-hours routing, the fax, and any line the clinical team uses.
    1. Cancel last. Only after the new carrier confirms the port and the test log is complete. Cancelling the old account before the port completes can release the numbers.

If the acquired office is joining the group's phone platform, the call-flow design (hours, menu, overflow to another office) belongs in the week-six plan, and the platform choice itself is in our guide to dental phone systems.

What should the network and firewall standard look like at the acquired office?

The acquired office should match the group's site template: one firewall model and rule set, separated networks for clinical systems, business devices, imaging equipment and guests, one Wi-Fi design, fixed addresses for imaging devices and printers, protected power in the closet, and a site document. It joins the group's shared systems only after it matches.

ElementGroup standardWhy it is in the standardAcceptance test
FirewallOne model and one rule set across offices; remote access only through the group's methodA different firewall at every office means a different exposure at every officeRule set exported and compared with the template; no inbound rule nobody can explain
Network separationClinical workstations and servers, business devices, imaging equipment and guest Wi-Fi on separate networksA guest phone should never reach the imaging serverA device on guest Wi-Fi cannot reach the practice server or any imaging device
Wi-FiOne design: a staff network and a guest network, no shared password written on the wallShared Wi-Fi passwords are never changed when people leaveStaff devices authenticate as users or as enrolled devices; the guest network is isolated
AddressingFixed addresses for servers, imaging devices, printers and the phone system; a written address planImaging bridges and printers break when addresses changeThe address plan matches what is on the network
InternetBusiness circuit with a known contract end; a second path (cellular or a second carrier) where phones and cloud software depend on itA single circuit is a single point of failure for a cloud officeFailover tested: the circuit is unplugged and the phones still work
ClosetRack or wall cabinet, protected power with runtime known, labels on every cable and portAn unlabelled closet with no battery backup turns a short power cut into a lost morningPhoto of the labelled closet in the site document; UPS runtime recorded
Site documentDiagram, address plan, equipment list with serials, carrier and vendor contacts, change logThe next technician should not need the last oneDocument exists and matches the room

Two rules make the standard safe to apply. First, the office joins group systems last: linking it to shared email, a central database or a site-to-site connection before its security matches the baseline extends its weaknesses to every location. Second, the network weekend is a planned window agreed with the office manager, not a Tuesday afternoon surprise. The design details, from cabling to closet, are in our guide to dental office network setup, and the group-wide view is in the DSO IT support services guide.

What is the minimum security baseline before the office joins shared systems?

The minimum is the set of controls your group already runs at every office, applied here before the first shared connection: endpoint detection on every machine, multi-factor sign-in on every account, a tested group backup with an off-site copy, supported operating systems or a dated plan, inventoried remote access, and a risk analysis updated for the new ownership.

ControlWhat it means at the acquired officeEvidence
Endpoint detection and responseThe group's agent on every workstation and server, replacing whatever antivirus the seller usedConsole shows every inventoried device; the difference is explained in EDR vs antivirus for dental offices
Named accounts with multi-factor sign-inEmail, remote access, practice software where offered, portalsAccount list with status; no shared login left on a clinical system without a written exception
BackupThe office on the group backup with an off-site copy; a second witnessed restore in week tenTwo dated restore records; see dental data backup
Patching and operating systemsEvery device on a supported version with updates applied in a set window. For reference, Microsoft's lifecycle pages (read 18 November 2026) give October 14, 2025 as Windows 10's end of support, January 12, 2027 as the end of extended support for Windows Server 2016, and January 9, 2029 for Windows Server 2019Inventory shows the version per device; anything unsupported has a replacement date
Remote accessEvery remote tool listed; the seller's and former vendors' tools removed; the group's method onlyRemoval list; see dental office remote access security
Local administrator rightsRemoved from day-to-day accountsPolicy report
Activity reviewLogs from the firewall, server and practice software reviewed on a scheduleReview log
Risk analysisUpdated for the office under its new ownership, with the findings feeding the exception registerDated risk analysis document

The risk-analysis and activity-review rows correspond to Security Rule specifications marked "Required" in the regulation text, quoted here as safeguards and not as advice: covered entities must "Conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information" (45 CFR 164.308(a)(1)(ii)(A)) and "Implement procedures to regularly review records of information system activity, such as audit logs, access reports, and security incident tracking reports" (45 CFR 164.308(a)(1)(ii)(D)). The documentation produced along the way is retained "for 6 years from the date of its creation or the date when it last was in effect, whichever is later" (45 CFR 164.316(b)(2)(i)), which is one reason the evidence column exists in every table on this page.

Unsupported machines are the common sticking point. An acquired office running Windows 10 workstations is not unusual in 2026, and the choice is replace, upgrade where the hardware allows, or isolate with a date; our guide to Windows 10 end of life for dental practices sets out the options.

How do you take over vendor contracts, licences and business associate agreements?

Build one vendor register in week two and work it to zero by week nine: every vendor that touches the office, what it touches, whose name the agreement is in, whether it can be assigned or must be re-signed, the renewal and cancel-by dates, whether a current business associate agreement exists, and who owns the portal login.

Register columnWhat to recordWhy
Vendor and what it doesPractice software, imaging, clearinghouse, phones, internet, backup, remote access, patient communication, payment processing, website, IT providerThe seller's list is never complete; the customer service record and the bank statements fill the gaps
Patient dataDoes the vendor create, receive, maintain or transmit patient informationDecides whether a business associate agreement is needed
Agreement holderThe seller's entity, the seller personally, or the practiceDecides whether assignment is possible
Assignment or re-signWhat the agreement says about a change of ownershipSome agreements survive a sale; some end; some auto-renew
Renewal and cancel-by datesBoth dates, in the group calendarNothing should renew unseen in month two
Business associate agreementIn force in whose name; datedA seller's agreement may not cover the new owner
Portal login ownerA named person at the group, with multi-factor sign-inShared portal logins outlive the people who used them
DecisionKeep, replace, terminate, with a dateThe register is finished when every row has one

Business associate agreements deserve a row of their own in the plan because the acquired office's agreements were made by a different covered entity. Which vendors need one, what the agreement must contain and what happens to your data when you leave a vendor are in our guide to business associate agreements for dental practices; the integration task is to know, by week nine, which agreements are in force in the right name.

The incumbent IT agreement is the register row with the most consequences. Read its term, auto-renewal and change-of-ownership language in week one if diligence did not. If it ends, the acquired office needs a support model: the group's own provider, a co-managed arrangement, or a new contract. How a shared model splits the work between an in-house IT person and an outside firm is set out in co-managed IT for dental groups. The comparison of best dental IT companies is written for that decision, and what a monthly plan should and should not include is in our guide to managed IT services for dental practices. If you are changing providers at the office, the handover steps are in how to switch dental IT providers without downtime.

How do you get the acquired staff signed in and supported?

Onboard the team in week five, after accounts exist and before the network weekend: one named account per person, a role-to-system list that says who reaches what, a single way to ask for help, a one-page "what changed on Monday" sheet, and a same-day process for removing access when someone leaves.

The acquired team has lost an owner and gained a corporate one. The IT changes land on top of that, so they should be few, explained and scheduled. What works:

    • One sheet, one page. How to sign in, how multi-factor prompts work, where to click for help, what has not changed. Hand it out in a huddle, not by email to addresses that are about to move.
    • Leavers the same day. Acquisitions bring departures. The Security Rule's administrative safeguards include an addressable specification to "Implement procedures for terminating access to electronic protected health information when the employment of, or other arrangement with, a workforce member ends" (45 CFR 164.308(a)(3)(ii)(C)); the register of named accounts is what makes that possible on the day.
    • Shared logins replaced with a reason. Where a clinical system cannot support one account per person, record the exception, who approved it and when it will be reviewed, instead of leaving the shared login undocumented.
    • Security habits as the group does them. How to recognise a fake IT call, how to report a suspicious email, why nobody installs a remote-access tool for a vendor without a ticket.

Training is also the moment to collect what the team knows that no document holds: which sensor is temperamental, which printer the hygienists share, which vendor calls on Fridays. That goes into the site document in week seven.

What does the cut-over weekend plan look like?

The infrastructure cut-over weekend replaces the firewall, switches and Wi-Fi, enrols workstations into the group's management and moves the office onto the group's monitoring, with Monday morning smoke tests in every room. It is separate from a practice-software conversion weekend, which has its own runbook, and the two are never run together.

WhenWorkOwnerGo or roll back
ThursdayFreeze changes; confirm equipment on site; confirm the backup from Wednesday night restored; print the address plan and the smoke-test sheet; tell staff the Monday startIntegration leadNo restore record means no weekend
Friday after the last patientFull backup of server and imaging store; export the old firewall configuration; photograph the closet as foundIT providerBackup verified before any cable moves
Friday eveningReplace the firewall and switches; apply the template; move devices to their networks; apply fixed addresses to imaging devices, printers and the phone systemIT providerEach device reachable from the right network before the next is moved
Saturday morningEnrol workstations in the group's management; join them to the group directory if that is the standard; confirm endpoint detection and monitoring report every deviceIT providerEvery inventoried device reports to the console
Saturday afternoonImaging test in every operatory: open a chart, acquire a test image on each sensor and the pano, confirm it attaches to the right record; printers, scanners, card readers, intraoral camerasIT provider with clinical leadAny operatory that fails is fixed or the old equipment is reconnected for that room
SundayPhones (if the port date is this weekend): inbound, outbound, voicemail, fax; remote access by the group's method; write the site document; walk the rooms with the office managerIT provider with office managerA failed phone test triggers forwarding to another office, not a Monday surprise
Sunday eveningGo or roll back decision against the sheet; a roll back means the old firewall configuration restored and the old addresses reapplied, which is why both were exported on FridayIntegration leadDecision recorded with time and names
Monday, before the first patientTechnician on site or on a call an hour before opening; smoke tests re-run in every room; the office manager has one number for the dayIT providerOpen items logged as exceptions with owners

Three habits keep the weekend short. Export before you replace, so rolling back is a file and not a rebuild. Test in the order patients will use the systems on Monday: the schedule, then the chart, then the sensor, then the claim. And give one person the decision; the rest of the room reports to them.

Who does what: the RACI for an acquired office

Give every workstream one accountable person and write it down in week one. The usual roles are the integration lead at the group, the office manager at the acquired practice, the group's IT provider, the seller and the seller's IT provider for a defined handover period, the practice-software and imaging vendors, and the attorney for the agreements.

R is responsible for doing the work, A is accountable for the result (one person per row), C is consulted, I is informed.

WorkstreamIntegration leadOffice managerIT providerSeller and seller's ITSoftware and imaging vendorsAttorney
Access and backupsAIRC (handover)II
Practice-software pathACCICC
Identity, email and domainAIRC (registrar)IC (domain clause)
Phone numbers and faxAR (details and tests)R (platform)C (letter of authorization)IC
Network and firewallIC (window)A and RIC (device addresses)I
Security baselineAIRIII
Vendors, licences and agreementsAR (collects documents)CCR (transfers)C (assignment)
Staff onboardingCARIII
Acceptance and handoverACRIII

The row most groups get wrong is the phone port, where the office manager usually holds the bills and the account knowledge, the IT provider holds the new platform, and the seller holds the signature. One accountable person and three responsible ones is normal there; what is not normal is nobody noticing that the letter of authorization has not been signed.

How do you know the acquired office is integrated?

The office counts as integrated once each acceptance-sheet row passes or is logged as an exception with a named owner and a revisit date, and the office shows up in the group's monthly report next to the others. The sheet is twelve tests run in week twelve, in front of the office manager, with the results filed as evidence.

#TestPass means
1Administrator accessThe group can sign in to server, firewall, practice software, imaging, email tenant, registrar and phone platform; the seller and former vendors cannot
2RestoreTwo witnessed restores on record from the group backup, the latest inside 30 days
3IdentityEvery current employee has a named account with multi-factor sign-in; no former employee has any
4Shared loginsNone on a clinical system without a written exception
5EmailMail sent to the old and new addresses arrives; outbound carries the right name
6PhonesMain number and fax tested inbound and outbound on the new platform; old account closed after confirmation
7NetworkFirewall and Wi-Fi match the template; a guest device cannot reach clinical systems; site document matches the room
8Endpoint and monitoringEvery inventoried device reports to the console; no unsupported operating system without a dated plan
9ImagingEvery sensor, the pano and any CBCT acquire and attach correctly from each operatory
10VendorsEvery register row has a decision; every kept vendor has an agreement in the right name; no renewal inside 90 days is unseen
11Practice-software pathMigrate, keep or bridge is written with a date; if migrate, the test conversion has run
12ReportingThe office appears in the monthly group IT report with ticket counts, backup results and open exceptions

The exception register is the companion. Every failed row becomes a line with the finding, the owner, the review date and the reason it was accepted for now. A group with three acquisitions a year ends up with a register that tells it which part of the playbook needs work.

What does the integration cost, and where do the lines sit?

Model the cost as one-time lines for the office, per-office recurring lines that change, and per-user lines that scale with headcount, and attach each to the workstream that creates it. Dollar figures depend on the office's condition and your group's standard, so get every line quoted in writing before closing where diligence allows.

LineTypeCreated byNote
Firewall, switches, Wi-Fi to the templateOne-timeNetwork workstreamOften the largest single line; quote it from the diligence inventory
Workstations and server replacement or rebuildOne-timeSecurity baselineDriven by unsupported operating systems and age
Cut-over weekend labourOne-timeNetwork workstreamTwo days of engineering plus Monday on site
Data conversion and image conversionOne-timePractice-software path (migrate or bridge)Vendors publish or quote these separately; images are often a separate fee from the database
Phone platform licences and port feesOne-time plus per-userPhones workstreamPort fees are usually small; the platform is per user
Email tenant licencesPer-userIdentity workstreamChanges with the licence tier you standardize on
Endpoint detection, backup, monitoringPer-device or per-officeSecurity baselineShould match what the group pays elsewhere
Duplicate subscriptions and lines cancelledSavingVendor registerThe register usually finds some
Ongoing supportPer-office or per-userVendor register (incumbent agreement decision)The model, not the number, is decided in week nine

The point of the model is comparison, not precision: the difference between an office that lands close to the group's standard cost and one that does not is the case for fixing the standard before the next acquisition.

The IT side: how a provider runs the 90 days

Behind the checklist, your IT provider should be running the integration as a project with a named engineer, a weekly status against the 13-week plan, and a change calendar agreed with the office manager. Six things to expect from them:

    • An inventory you can read in week two: every device, operating system, age, role and replacement decision, from the monitoring agent rather than from a walk-through.
    • Monitoring from day one, so the first week's problems are seen in the console before they are reported by the front desk.
    • Documentation as a deliverable: the site document, the address plan, the credential inventory and the vendor register are written artefacts with dates, not knowledge in one engineer's head.
    • Change windows, never changes on a clinical day without the office manager's agreement.
    • Tests with witnesses: the restore, the imaging test, the phone test and the acceptance sheet are run with someone from the practice present.
    • A monthly report that includes the new office from week thirteen: tickets, backup results, patching status, open exceptions.

Legend runs 24/7 monitoring at the offices it supports, with in-house engineers; no outsourced first-level triage, which matters most in week one, when the acquired team is calling a number they have never used about systems they did not choose.

What to ask your IT provider before the acquired office joins the group

About the plan

  • Which of the nine workstreams will you own, and who at your company is accountable for each?
  • What is your 13-week plan for this office, and which weeks need a change window on the appointment book?
  • How will you report progress against it, and to whom?

About control and recovery

  • When will you have tested every administrator credential, and what will you do about the ones that do not work?
  • When is the first witnessed restore, and when is the second?
  • Which remote-access tools did you find, and which have you removed?

About the standard

  • What does our site template require at this office that it does not have today, and what does each gap cost?
  • Which devices are on an unsupported operating system, and what is the date on each one?
  • What test proves a guest device cannot reach clinical systems here?

About the software path

  • What is your recommendation on migrate, keep or bridge for this office, and why?
  • If we convert, which weekend, what is the rollback, and who runs the imaging tests?

About the acquired team

  • How will the team ask for help in week one, and how will you tell them?
  • How quickly is a leaver's access removed, and who confirms it?

How Legend Networking works with groups that acquire offices

Legend Networking, based in Dallas, has served over 3,500 practices since 2004: 22+ years in dental IT. The guide is written by Ian Lynch, who has 22 years in dental IT; he oversees the NOC, onsite dispatch and client technology roadmaps. On Google, Legend's rating stands at 4.8 across 173 reviews.

The week-seven imaging tests and the migrate, keep or bridge decision depend on the systems in the building; on the practice-software side Legend supports the IT environment for Dentrix, Eaglesoft, Open Dental and Archy, and on imaging for DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging. Onsite dispatch by appointment across served dental markets; remote-first nationwide. Our DSO IT support work covers the standard an acquired office is brought to and the reporting that shows it stayed there, and our national dental IT support page describes what a practice on a Legend plan receives.

For what the second-location version of this work looks like, see the network, Wi-Fi, backup and software integration work at a practice's second location. If you are taking over a single office rather than adding to a group, our Fort Myers guide to taking over a second-generation dental office walks the same ground for one practice in one city, and the city-by-city pages are under dental IT by city.

Questions

Frequently asked questions

What is the difference between IT due diligence and IT integration in a dental practice acquisition?

Due diligence happens before you sign: it checks who owns the data, whether backups restore, what the IT contract says and what the hardware will cost to fix, so the findings can change the price or the terms. Integration happens after closing: it moves control to you and brings the office to your standard. Diligence findings become the first rows of the integration plan.

Which systems should change in the first week after closing, and which should wait?

In the first week, change only what secures control: administrator passwords, your own admin accounts, removal of unknown remote-access tools, the monitoring agent and a witnessed backup restore. Leave the practice software, the imaging bridge, the phone numbers, email addresses and workstations alone. Those move in later weeks, one at a time, each behind a test.

Can the acquired office keep its own practice management software for now?

Yes, and for most acquisitions it should, at least for the first 30 days. The decision between migrating, keeping or bridging is written down by the end of week two with a date and an owner, but a conversion is executed later, after the staff know the group and the backups, identity and network are under control. Forcing a conversion into week one mixes handover problems with conversion problems.

What does "bridging" an acquired office's software mean?

Bridging means keeping the acquired office's current practice software for a defined period while the group puts its backup, security and access controls around it, gets reporting through exports, confirms data-export rights with the vendor and prepares the conversion. The bridge ends on a date, usually aligned to the software contract term or a quiet month, when the conversion runs with its own runbook.

Who has to authorize moving the acquired office's phone numbers to the group's phone system?

The account holder of record with the current carrier, which is often the seller or the seller's entity. The new carrier needs a signed letter of authorization from that holder, a recent bill and the account PIN, with the address and account number matching the carrier's record exactly. Confirm the holder in week three so the signature is in hand before the port date.

Should the acquired team get new email addresses on closing day?

No. Email moves in week four, after accounts exist in your directory and the registrar and DNS are under your control. A small office usually gets new mailboxes with forwarding from the old addresses for a set period; a larger office with shared mailboxes and calendars may need a tenant migration. The test is that mail to both addresses arrives.

When should an acquired office connect to the group's shared network and systems?

Last. Connect the office to shared email, a central database or a site-to-site link only after it matches the group's security baseline: endpoint detection on every device, named accounts with multi-factor sign-in, a tested backup, no unknown remote access and a firewall on the template. Connecting first extends the office's weaknesses to every other location in the group.

What happens to the seller's IT contract after the practice is sold?

It depends on its term, auto-renewal and change-of-ownership language, which should have been read in diligence and must be read in week one if not. Some agreements end at the sale, some survive it, some renew unless notice is given. The register records the decision: keep for a handover period, move to the group's provider, or end it on a date.

How do you prove an acquired office is fully integrated?

Run the twelve-row acceptance sheet in week twelve with the office manager present: administrator access, two restores, named accounts, no undocumented shared logins, email, phones, network, endpoint and monitoring, imaging in every operatory, the vendor register, the software decision and the monthly report. Anything that fails goes on the exception register with a named owner and a date to revisit it.

What goes wrong most often in the first 90 days after a dental acquisition?

Four things: a phone number that stops ringing because the old account was cancelled before the port completed; a conversion forced into the first weeks that leaves ledgers or images behind; a vendor or software agreement that renews in the seller's name because nobody held the register; and an office connected to shared systems before its security matched the group's baseline.

The bottom line

If an acquisition is closing in the next quarter, or one closed last month and the checklist above has gaps, ask Legend for a Free Dental IT Assessment of the acquired office: a review of its computers, software, network security, backups and performance, with written findings and prioritized recommendations that slot straight into the 13-week plan. Start with our DSO IT support team, or read how dental IT support from Legend works for a single practice first.

Ian Lynch
About the author

Ian Lynch

Owner & Operator, Legend Networking

22 years in dental IT. Oversees the NOC, onsite dispatch and client technology roadmaps for practices nationwide.

  • Operations center

    Dallas, Texas

    Serving dental practices nationwide since 2004

  • NOC hours

    24/7 monitoring

    Helpdesk staffed 24/7 at 1-800-794-1588

  • Engineers

    In-house only

    No outsourced first-level dental IT triage

  • Onsite dispatch

    By appointment

    Technicians deployed across served dental markets

About Legend Networking
Your next step

Ask for an acquisition IT assessment before the next office joins

Tell us what you are running and we will review it with you.

Or call 1-800-794-1588