Growing a Dental Group in Las Vegas: The IT Plan for Your Second to Tenth Office
Your Green Valley office is booked three weeks out. A lease for a second suite in Summerlin is on your desk, or a retiring North Las Vegas dentist has offered you the practice. In the same month, two dental support organizations have sent letters asking if you would consider partnering. You intend to stay independent, and you want the second office to run as well as the first.
Our page on dental IT support in Las Vegas covers the service; this guide is the IT plan for a growing dental group in Las Vegas, the part most owners leave until after the ribbon cutting. It goes deeper on one decision: how an independent owner adds offices across the valley without ending up with two practices that happen to share a name. The wider picture of heat, power, internet and opening a first office is in the Las Vegas dental IT guide. The reader is an independent owner with one, two or three locations who is about to add another, whether that office is built, leased as a second-generation suite or bought from a retiring dentist.
Before office two opens, decide what every office will share and what each office keeps. Share the practice-management version, where images are stored, one account per person, one backup design and one set of records. Keep local the internet line, the closet and the front-desk routines. Then plan for a storm that cuts power to every office at once.
- In 2025 no state had a larger share of DSO-affiliated dentists than Nevada, so an independent group competes with central systems and hires associates trained on them.
- Standardize what crosses between offices first: software version, image storage, accounts, backup design and records.
- Fold acquired offices in with an inventory first and planned steps after; most surprises sit in the seller's name.
- One utility serves the valley, so plan for an outage that hits every office at once, and keep the offsite backup outside the valley.
- Keep the records a partner or buyer would ask for; they also make today's IT easier.
In this guide
- What does Nevada's DSO-heavy market mean for an independent group?
- What should you standardize before office two opens?
- Should every office run the same software and imaging versions?
- How do you fold a retiring dentist's office into your group?
- What happens when one storm hits every office at once?
- How should staff who float between Summerlin and Henderson be set up?
- How should phones and the front desk work across several offices?
- Which vendors does a group rely on, and who owns each relationship?
- What IT records should a growing group keep ready for a partner or buyer?
- What does IT cost when a practice adds offices?
- Can a Dallas-based provider support offices across the valley?
- What to ask your IT provider before office two
- Key takeaways
- Sources
- Frequently asked questions
- The bottom line
What does Nevada's DSO-heavy market mean for an independent group?
In the ADA Health Policy Institute's 2025 data, group affiliation was more common among Nevada dentists than anywhere else in the US. For an independent owner, the competition across the street often runs central scheduling, shared imaging and one set of logins, and the associates you hire may have trained inside those systems. An independent group can match that discipline without a head office by deciding the shared pieces early.
The ADA Health Policy Institute's 2025 state file puts Nevada first in the country for DSO affiliation, and it also shows how dentists spread across practice sizes. The full Nevada table sits in the guide to dental IT in Las Vegas; this guide reads it for a group that wants to stay independent. HPI cautions that its method slightly undercounts affiliation, so treat the shares as minimums.
Read from an owner's desk in Henderson, Summerlin or the southwest valley, the file says three things.
The middle is thin. In 2025, fewer than one Nevada dentist in fifteen worked for an organization with two to nine locations. Most worked either in a single-location office or inside a platform with ten or more. A group of two to six offices is therefore an unusual shape here, with few peers to copy and no head-office IT to lean on.
Your next associate probably trained on group systems. HPI's 2025 file puts a majority of Nevada's newest dentists in DSO-affiliated practices, so the associate you hire for office two may be used to booking across locations, opening any patient's images from any operatory, and logging in once. If your group's systems feel older than what they left, that shows in the first week.
Big platforms set the patient's expectation. Patients who move between offices in a group expect their chart, images and balance to follow them. A platform delivers that from a central office. An independent group gets the same result from decisions made once and applied to every office.
None of this says independents should partner, or should not. That is a business and legal decision outside this guide. What the data supports is narrower: if you plan to stay independent in Nevada, your IT should behave like one practice in several places. For the national picture of how platforms run IT, Legend keeps a page on DSO IT support and a longer guide to DSO IT support services. The rest of this article is about the independent version.
Office size points the same way. Census business data show that most dental offices in the metro employ five or more people, so a "small" second office here can still mean eight or ten staff, each needing an account, a device and a role.
What should you standardize before office two opens?
Standardize the things patients and staff cross between offices: the practice-management software and its version, where images live, how people sign in, how backups are designed and tested, and what is written down about each office. Leave room for local differences in internet carrier, closet layout and front-desk habits. Decide each item once, write it down, and apply it everywhere.
A common mistake is to copy office one exactly, including its problems. Office one usually grew by accident: a server bought in year two, a firewall a cousin set up, a shared front-desk login nobody changed. Office two is the moment to write the standard you wish office one had, then bring office one up to it on a schedule.
The table below shows how the decisions change as a group grows. Each cell is a decision, not a product. Where a cell says "same", it means every office runs it the same way, documented in one place.
Table 1: Group readiness by size, what to decide at each step
| Area | 1 office | 2 offices | 3 to 5 offices | 6 to 10 offices |
|---|---|---|---|---|
| Practice-management software (PMS) and version | Whatever runs today, kept current | Same product and version in both; decide whether office two connects to office one's database or has its own | One shared database or one cloud tenant; version changes rolled out on a schedule | Written change calendar; one test office takes each update first |
| Imaging software and image storage | Images on the local server or PC | Decide where office two's images live and how a provider in office one opens them | One storage design for every office; same imaging product where possible | Storage sized for growth; retention rules written down |
| Identity (Microsoft 365 or Google, Windows sign-in) | One tenant, but shared logins are common | One tenant for the group; one named account per person; MFA on email | Role-based groups (front desk, clinical, billing, owner); naming standard | Joiner, mover and leaver steps run the same day for every office |
| Workstations | Mixed ages and builds | A standard operatory build and a standard front-desk build | Replacement cycle per device, tracked in one inventory | Spares held for each build; new rooms set up from the standard |
| Network and firewall | One firewall, often consumer-grade | Same firewall family in both; decide site-to-site link or cloud access | One configuration template; changes logged | Central view of every office's firewall and switches |
| Backups | One backup, rarely tested | Same design in both offices: local copy plus an offsite copy | Restore tests per office on a calendar, with results written down | Restore evidence kept for every office every quarter |
| Documentation | In someone's head | One sheet per office: internet circuit, closet, devices, admin accounts | Same template for every office; reviewed twice a year | Kept current by the IT provider and checked by the practice |
| Vendors | Owner calls whoever answers | One named owner per vendor relationship | Vendor register with account numbers and contacts per office | Register reviewed at each contract renewal |
| Reporting | Owner checks the schedule | Same reports run the same way in both offices | Group-level production and collections from one system | Reporting cut-off times agreed in Pacific time for every office |
Two decisions in that table carry most of the weight, so settle them first.
Database: shared or separate? A shared database (or one cloud tenant) lets any office see any patient, which matters when patients move between Green Valley and Summerlin. It also means one outage, one upgrade and one set of permissions for everyone. Separate databases keep offices independent, but every referral, transfer and group report becomes a manual step. Most growing groups move toward shared. Ask your software vendor how its product handles multiple locations, and ask your IT provider what the connection between offices needs.
Accounts: one person, one login. Shared front-desk logins are the most common habit that breaks when a second office opens. With one named account per person, you can see who did what, switch off a leaver everywhere at once, and give a floating hygienist the same access in both offices.
If you are opening office two from bare walls, the build-side decisions (cabling, closet, internet order) are covered in our piece on dental startup IT in Las Vegas. The ongoing side, who watches backups and patches each month, is in managed IT for dental practices in Las Vegas.
Should every office run the same software and imaging versions?
Yes, as a goal. When offices share patients or reports, mismatched versions cause charts that will not open across offices, images one office cannot read, and reports that do not add up. Reach the goal in stages. Test the target version on one operatory, then one office, then roll it out, instead of moving every office in one weekend.
Groups that grow by acquisition rarely start aligned. The office you buy in North Las Vegas may run a different practice-management product, an older imaging version, or sensors whose drivers have not been updated in years. Moving it onto your standard is worth doing. Doing it in the first week, with a new team and patients who already miss the old dentist, usually is not.
A staged path that works for most independent groups:
- Inventory first. List every operatory computer, its imaging software version, its sensor model and driver, and the practice-management version. No changes yet.
- Pick the target. Usually the version your largest office runs, once it is current.
- Test on one operatory. Install the target version on one room's computer in the office being moved. Take test images, open them from the chart, print a walkout, run a claim.
- Move the data with a tested restore. Convert or migrate the database and the image archive, then prove you can open old patients' images on the new system before the old one is switched off.
- Roll out by room, after hours. One room per evening if needed, so a problem never stops the whole schedule.
- Retire the old system on paper. Record where the old database and images now live, who can reach them, and for how long you keep them.
Our dental software migration checklist covers the conversion steps in detail. For what goes wrong between the practice software and the imaging program when versions drift, see the companion piece on dental software and imaging support in Las Vegas. Legend's published list of supported practice-management systems is Dentrix, Eaglesoft, Open Dental, Archy, and its imaging list is DEXIS, Vatech, Carestream, Planmeca/Romexis, Dolphin Imaging. Whichever products your group runs, the version decision belongs to the owner, with the vendor's compatibility notes in hand.
How do you fold a retiring dentist's office into your group?
Take stock before you change anything. In the first weeks, record what the acquired office runs, who holds its accounts and licences, where its records and images live, and what condition its cabling and closet are in. Then move it onto your group's standard in planned steps. Most surprises in an acquisition come from things in the seller's name.
Established offices come up for sale as owners retire. Many of the valley's established offices are multi-dentist practices with sizable teams, so the office you buy may arrive with a dozen logins and years of history in its systems. When one of those owners retires, a nearby group is a natural buyer, and the office arrives with years of history in its systems.
Before closing, the deal checklist matters most, and our guide to IT due diligence when acquiring a dental practice covers it. After closing, the job changes from "what are we buying" to "how do we bring it in". Use the list below for the acquired office, in this order.
Inheritance checklist for an acquired Las Vegas office
- [ ] Data export rights. Confirm in writing that the practice owns its patient database and images, and that the software vendor will transfer the licence or allow export to your system.
- [ ] Image archive format. Find out which imaging program created the archive, how large it is, and whether your imaging software can read it directly or needs a conversion.
- [ ] The old server. Note its age, what runs on it, when it was last backed up, and whether that backup has ever been restored. Do not switch it off until its data has moved and been checked.
- [ ] Licences and accounts in the seller's name. Practice software, imaging, Microsoft 365 or Google, the domain name, the website, the internet account, the phone account. List each, then transfer it.
- [ ] Administrator passwords. Firewall, server, Wi-Fi, email admin, imaging admin. Change them all once the transfer is complete, and record who holds the new ones.
- [ ] Cabling and closet. Look at the closet: labels, heat, whether the rack sits on the floor, whether the battery backup is still holding a charge. Older Paradise and east-valley buildings may have cabling nobody has traced in years.
- [ ] Phone numbers. Patients know the old number. Confirm the number can be moved to your carrier before you cancel anything.
- [ ] Devices by room. Sensor model, driver version, intraoral camera, printers, card terminals. Photograph the back of each computer before anything is unplugged.
- [ ] Staff accounts. Who is staying, who is leaving, and which shared logins exist that need replacing with named accounts.
Once that list is complete, apply the staged path from the previous section. The first month is for learning the office; the second and third months are for moving it onto the standard.
What happens when one storm hits every office at once?
Plan for it as a group-level event. The whole Las Vegas Valley is served by one electric utility, NV Energy, so offices in Summerlin, Henderson and North Las Vegas can lose power in the same afternoon. Decide in advance which systems keep running, where patients are redirected, who checks each office and who restarts the computers, in what order.
The valley has a dated example. On July 1, 2025, the first major monsoon surge of that year's season sent dust and wind across the valley. Fox Weather's tally passed 30,000 homes and businesses without power, with Henderson gusts topping 70 mph and the worst pole damage on the west and north sides. A group with one office near the Summerlin side and another in Henderson could have had both dark at once.
In many metros, two offices in different suburbs sit on different utilities or different parts of the grid, so they partly protect each other. Here, every office reports to the same utility. Spreading offices across the valley spreads some risk, because a storm does not cut every street, but it does not give you the separation a multi-utility metro can. Plan on the assumption that one office cannot always cover for another.
Some systems behave differently in an outage. If the practice software is hosted in the cloud, an office that loses power may still reach it from another office or from a laptop on a phone hotspot. If the practice software sits on a server in office one's closet, every office that depends on it goes down when office one does, even if their own lights are on. That single dependency is easy to miss when the server was bought for one office and the group grew around it.
The matrix below is a sheet to fill in for your own offices. Copy it, fill one row per office, and keep a printed copy at each front desk.
Table 2: One-valley outage matrix (fill in for each office)
| Office | Power status: where to check | Internet status: where to check | What keeps running if this office loses power | Where patients go | Who checks this office | Who calls whom | Who owns the restart order |
|---|---|---|---|---|---|---|---|
| Office 1 (e.g. Green Valley) | NV Energy outage map, by address | Carrier's status page or account app | e.g. cloud PMS from other offices; hosted phones forward | e.g. Office 2 for emergencies | Office manager | Manager → owner → IT provider | IT provider, with the manager on site |
| Office 2 (e.g. Summerlin) | NV Energy outage map | Carrier's status page | |||||
| Office 3 (e.g. North Las Vegas) | NV Energy outage map | Carrier's status page | |||||
| Shared systems (server, phones, PMS host) | Where the server lives | Vendor status page | Which offices depend on it | n/a | Named person | IT provider → vendors | IT provider |
NV Energy's outage map can be searched by address, and its outage page lists current events. Bookmark both on every front-desk computer and on the owner's phone. Your internet carrier will have its own status page or app; carriers differ by office, so record each one.
Three rules make the matrix work in practice:
- Name a person, not a role, for each cell. "Front desk" is nobody at 6:15 p.m. on a Tuesday.
- Write the restart order down. When power returns, the network gear and server come up before the workstations, and imaging computers after the server. Whoever owns your IT should write that order for each office and keep it in the office sheet. Our general guide to what to do when the dental office internet is down covers the patient-facing side.
- Test the redirect once a year. Call the main number from a mobile phone and check where it rings when office one is marked closed.
Backups belong in the same plan. Keep a local copy in each office for fast restores, and hold the offsite copy somewhere a Las Vegas storm cannot reach. Legend's page on backup and recovery for dental practices explains the approach.
How should staff who float between Summerlin and Henderson be set up?
Give each person one identity that works in every office, with access set by role rather than location. A hygienist who works Mondays in Summerlin and Thursdays in Henderson should use the same account in both and print to the nearest printer. When someone leaves, switch off that one account and they are out of every office the same day.
Every new office adds staff, and dental staff move between practices. A clean account setup turns hiring and leaving into routine steps instead of half-days of password resets.
Floating-staff setup checklist
- [ ] One named account per person in Microsoft 365 or Google, with multi-factor sign-in turned on.
- [ ] Practice-management access by role: front desk, clinical, billing, manager, owner. No shared "frontdesk1" logins.
- [ ] Imaging access that opens the same patient's images from any office the person works in.
- [ ] Printers, scanners and card terminals mapped per office, so the nearest device appears automatically when someone signs in there.
- [ ] Workstations that keep no patient files on the desktop; work saves to the shared storage.
- [ ] A joiner list: accounts, role, offices, devices, training date, signed policies.
- [ ] A leaver list run the same day: disable the account, remove from every office's systems, recover devices and badges, change any shared door or alarm codes.
- [ ] A mover list for promotions or office changes: adjust role, remove old access, add new.
Our guide to dental employee IT onboarding and offboarding has the full steps. The point for a group is that each list runs once and covers every office.
How should phones and the front desk work across several offices?
Settle four questions before office two opens: one main number or one per office, how calls move between offices when one desk is busy or closed, whether scheduling is done centrally or at each desk, and how long call recordings are kept. The first three are workflow choices. The last is a records question to settle with your compliance advisor.
Phones are where patients feel a group first. A patient who calls the Henderson office and is told to "call Summerlin" sees two businesses. A patient whose call is answered at either desk with the right chart open sees one. The choices:
| Question | Option A | Option B | What to weigh |
|---|---|---|---|
| Numbers | One main number for the group | One number per office | Local search listings and existing patients' habits favor keeping each office's number; a main number simplifies marketing |
| Routing | Calls ring the office dialled, then overflow to another desk | Every call rings a central team | Overflow needs the same scheduling access in both offices |
| Scheduling | Each desk books its own office | Any desk books any office | Shared scheduling needs a shared database or cloud PMS |
| Recordings | Kept for a set period | Not recorded | A compliance and records decision; ask your advisor |
Whatever you choose, write it in each office's sheet, including what happens to calls during an outage. Legend's articles on VoIP phone systems for dental offices and on replacing POTS lines in a dental office explain the technology for further reading. The phone carrier itself is one of the vendors your group needs to own, which is the next section.
Which vendors does a group rely on, and who owns each relationship?
A growing group depends on many outside companies: the practice software and imaging vendors, an internet carrier per office, the phone carrier, card-terminal and payment providers, the IT provider, and the landlord or HVAC contractor who controls the closet's cooling. Each needs one named owner in your group, an account number on file and a contact who answers.
When something breaks, the slowest part is often finding out which company to call and whose name is on the account. A vendor register fixes that. Keep one for the group, with a row per vendor per office.
Vendor register (one row per vendor per office)
| Vendor type | What they provide | Account number | Support contact and hours in Pacific time | Group owner | Contract renewal date |
|---|---|---|---|---|---|
| Practice-management software | Database, updates, licences | ||||
| Imaging software and sensors | Capture, storage, drivers | ||||
| Internet carrier, Office 1 | Primary line | ||||
| Internet carrier, Office 1 backup | Second line | ||||
| Internet carrier, Office 2 | Primary line | ||||
| Phone carrier | Numbers, routing | ||||
| Card terminals and payments | Terminals, processing | ||||
| IT provider | Workstations, network, backups, accounts | ||||
| Landlord or HVAC contractor | Closet cooling, after-hours air | ||||
| Domain and email | Domain name, Microsoft 365 or Google |
Two columns repay attention. Hours in Pacific time: Las Vegas keeps Pacific time and changes its clocks with most of the country, so it sits two hours behind Central time and three behind Eastern all year. A vendor whose line closes at 5 p.m. Eastern is gone by 2 p.m. at your front desk. Landlord or HVAC: in a Las Vegas summer, a closet in a retail-center suite can depend on building air that is set back at night or on weekends. Whoever controls that thermostat is part of your IT.
Two quiet failures to guard against in a growing group are a backup subscription that lapses without anyone noticing, and a provider nobody can reach when something breaks. A register with renewal dates and an owner for each line is the plain defence against both.
What IT records should a growing group keep ready for a partner or buyer?
Keep records that show what you own, what it runs, and that it works: a device inventory, a list of licences and contracts, backup restore evidence, network diagrams, administrator accounts, security policies and training dates. Whether you stay independent or partner later, these records make every conversation faster. They also make your own IT easier to run today.
Owners in this market get letters from DSOs. Some will partner, some never will. Either way, a buyer, a lender, an insurer or a new office manager will ask the same questions, and the answer should be a folder rather than a week of searching.
Buyer-ready IT records (one folder per office, plus one for the group)
- [ ] Device inventory: every computer, server, firewall, switch, sensor and printer, with purchase date and location.
- [ ] Software and licence list: product, version, number of seats, licence holder, renewal date.
- [ ] Contracts: IT provider, software vendors, carriers, phones, payment processing, with term and notice periods.
- [ ] Backup restore evidence: date of each test restore, what was restored, who checked it.
- [ ] Network diagram for each office: internet lines, firewall, switches, Wi-Fi, where the server and closet are.
- [ ] Administrator account list: which accounts have admin rights, who holds them, where the passwords are stored.
- [ ] Security policies and staff training records with dates.
- [ ] Incident log: what went wrong, when, and what was done.
- [ ] The vendor register and the outage matrix from earlier in this guide.
This list deliberately says nothing about valuation, contract terms or legal duties. Those belong with your accountant and attorney. What it does is keep your options open. For a year-by-year view of when to replace hardware and revisit these records, see the dental IT roadmap.
What does IT cost when a practice adds offices?
Cost grows with users, devices and locations, so each office adds to the monthly figure, and a new or acquired office adds one-off project work. Legend's ongoing support is published as "Starting at $360 per month"; the price for a group depends on its size. Hardware procurement, major cabling projects and software licensing are quoted separately.
Proposals for similar offices can range widely, which usually means the quotes cover different things. When you compare proposals for a second or third office, ask each provider to split its price into the same lines:
- monthly support for the existing offices;
- monthly support added for the new office (users, workstations, servers, network devices);
- one-off setup for the new office: cabling, closet, workstations, firewall, moving data;
- one-off work to bring the first office up to the group standard;
- software licences, carriers and hardware, which are usually passed through.
Ask also what happens to the price when you add office three. A quote that only works for two offices will be rewritten next year.
Can a Dallas-based provider support offices across the valley?
Yes, if the model fits how dental IT problems actually arise. Most issues are handled remotely, and physical work is scheduled. Legend is headquartered in Dallas, two hours ahead of Las Vegas all year. Its helpdesk is staffed 24/7 at 1-800-794-1588, alongside 24/7 monitoring, and its stated model is "Onsite dispatch by appointment across served dental markets; remote-first nationwide."
In practice, day-to-day software and support issues are handled remotely; cabling, installations, equipment moves and new-office build-outs are scheduled onsite by appointment. Its published support model is "In-house engineers; no outsourced first-level triage." Legend has "Served over 3,500 practices since 2004", shows a "4.8 rating · 173 Google reviews", and Ian Lynch's published role is: "Ian Lynch — 22 years in dental IT; oversees the NOC, onsite dispatch and client technology roadmaps."
Legend's Las Vegas project pages include a September 2025 installation for the new Smile Elegance Dental office, completed before it opened; the Smile Elegance project page has the photos. For what Legend's service covers for Las Vegas practices, see the page for anyone choosing a dental IT company in Las Vegas.
If you want a starting point before you sign the next lease, you can request a Free Dental IT Assessment for your current office and use the findings as the standard for the next one.
What to ask your IT provider before office two
Put these to any provider, in writing, before the second office opens.
- Will office two connect to office one's database, or run its own, and what does each choice need from the network and the internet lines?
- What is the group standard for workstations, firewall and backups, and how will office one be brought up to it?
- How will one account per person work across every office, and how fast is a leaver switched off everywhere?
- If office one's server goes down, which other offices stop working, and what is the plan for that?
- What is the restart order for each office after a power cut, and who carries it out?
- Where is the offsite backup kept, and when did someone last restore an office from it?
- Which vendors will you call on our behalf, and which do we call ourselves? Put that in the contract.
- How is the price built when we add office three, and which costs are one-off?
Key takeaways
- In 2025 no state had a larger share of DSO-affiliated dentists than Nevada, so an independent group competes with central systems and hires associates trained on them.
- Standardize what crosses between offices first: software version, image storage, accounts, backup design and records.
- Fold acquired offices in with an inventory first and planned steps after; most surprises sit in the seller's name.
- One utility serves the valley, so plan for an outage that hits every office at once, and keep the offsite backup outside the valley.
- Keep the records a partner or buyer would ask for; they also make today's IT easier.
Sources
- ADA Health Policy Institute 2025 workbook on practice size and DSO affiliation, Nevada rows. Opened November 9, 2026.
- Census County Business Patterns 2023, dentists' offices in the Las Vegas metro.
- FOX Weather, report on the July 1, 2025 Las Vegas Valley dust storm and power outages.
- NV Energy outage map and outage listings.
- NIST Time and Frequency Division, daylight saving time rules.
Frequently asked questions
What should a Las Vegas practice standardize before opening a second office?
Standardize the pieces patients and staff cross between offices: the same practice-management product and version, one decision on where images are stored, one named account per person with multi-factor sign-in, the same backup design with an offsite copy, and one written sheet per office. Leave the internet carrier and closet layout local. Decide each item once, then bring the first office up to the same standard.
How does Nevada's DSO-heavy market change IT decisions for an independent group?
No state had a larger share of DSO-affiliated dentists than Nevada in 2025, and among its dentists in their first five years, affiliation was the majority path. Independent groups compete with offices that share scheduling, images and logins, and hire associates used to those systems. Matching that takes early decisions on shared software, accounts and storage, without needing a head office.
What should a group check in a retiring dentist's office in Henderson or Summerlin before folding it in?
Check what sits in the seller's name: software licences, the domain, email, internet and phone accounts. Confirm you can export the patient database and read the image archive. Note the old server's age and test its backup with a real restore. Record every administrator password, the closet and cabling state, and each room's sensor and driver. Change nothing until that inventory is done.
Should every office in a Las Vegas group run the same practice-management and imaging versions?
Yes, as a goal, because mismatched versions break shared charts, image viewing and group reports. Get there in stages. Inventory each office, choose a target version, test it on one operatory, move the data with a tested restore, then roll out room by room after hours. Keep the old system's data reachable and recorded until you no longer need it.
How should staff who work in both the Summerlin and Henderson offices be set up?
Give each person one named account that works in every office, with practice-software and imaging access set by role, not location. Map printers and scanners per office so the nearest one appears at sign-in, and keep patient files off desktops. When someone leaves, disable that one account the same day, which removes their access to every office at once.
What happens to a multi-office Las Vegas group when one storm cuts power across the valley?
All of them can lose power in the same storm, since one utility serves the valley; the July 1, 2025 dust storm left over 30,000 NV Energy customers dark. Plan which systems keep running, where patients are redirected, who checks each office, and who owns the restart order. A server in one office's closet can stop every office that depends on it.
How should phones and the front desk work across several Las Vegas offices?
Decide four things before office two opens: one main number or one per office, how calls overflow between desks when one is busy or closed, whether any desk can book any office, and how long recordings are kept. Shared booking needs a shared database or cloud software. Recording retention is a records question for your compliance advisor. Write each answer into the office sheet.
What IT records should a growing Las Vegas group keep ready for a future partner or buyer?
Keep one folder per office: a device inventory with purchase dates, software licences and versions, contracts with notice periods, dated backup restore tests, network diagrams, the administrator account list, security policies and training records, and an incident log. These records answer a buyer's, lender's or insurer's questions quickly, and they make the group's day-to-day IT easier to run.
The bottom line
Before the next lease or purchase is signed, get a clear baseline of the office you already run. Ask for a Free Dental IT Assessment and treat the written findings as a multi-office baseline: one sheet per office, ready before the next one opens.

