Adding a Second (or Fifth) Dental Office Across Greater Houston: The IT Plan

The Cypress office is booked solid. A lease in Katy waits for signature, or a retiring Pearland dentist has offered you his practice. Systems built for one front desk must soon serve two offices and one patient list.

This page is for the owner of two to five offices, or the person running operations for one, in the months when the group is growing. It works through where Houston practices are adding offices, the decisions that belong before office two, what changes when the office is bought rather than built, how the clinical software should be set up, what a regional storm does to every site, how to set up staff who float, which vendors the group now depends on, how phones and internet join the offices together, and what IT costs. A list of questions for your IT provider and a short FAQ close it.

Where are Houston practices opening their second offices?

Mostly where new households are arriving. No American metro gained more people in a year than Houston–Pasadena–The Woodlands: 126,720 more residents by July 1, 2025, per Census Vintage 2025 estimates. Harris County topped every U.S. county for numeric growth, Montgomery came fourth and Fort Bend eighth.

Here is that growth by county, taken from Census release CB26-56, published March 26, 2026:

Read these as head counts of residents. They do not measure dental demand, and no Houston office should read its own patient numbers into them. What they suggest, and this is our reading rather than a Census finding, is why the second office so often sits one county over from the first: an owner in Cy-Fair looks west toward Katy and Waller, a practice in Sugar Land looks south and west through Fort Bend, and an office near Spring looks north toward The Woodlands and Conroe.

For IT, the county line matters for three practical reasons. The new address may have a different set of internet carriers built to the building. It may sit in a different flood or drainage picture, which affects where equipment goes inside the suite. And it puts real distance and traffic between offices, which changes how often anyone can carry a drive, a laptop or a spare part from one site to the other. Plans that assume "someone can just pop over" tend to fail on the first Tuesday it matters.

For the wider picture of practice IT in the metro, from support models to storm season, start with Legend's Houston dental IT guide.

What has to be decided before office two opens?

Eight things: where staff sign in and keep email, whether the practice-management database is shared, where images are stored, how phones and numbers work, how each office reaches the internet, where the backup copy lives, which security rules apply everywhere, and who holds each vendor contract. Each has a shared and a per-site answer, and early is cheaper.

The table below is meant to be printed and handed to whoever is building the new office: your IT provider, your low-voltage contractor and your office manager. Write the choice in the margin of each row and the name of the person who owns it.

Two rows usually decide the rest. Whatever you pick for the database fixes how much hardware office two needs and how badly it suffers when office one's connection fails. The tenant choice sets how people, email and access work for as long as the group exists. Make those two first, then fill in the others.

For an owner whose plan already runs past two or three offices toward a group run on shared standards, Legend's page on IT for DSOs and multi-location dental groups covers that stage of growth, and the full guide to DSO IT covers standards and onboarding in depth.

What changes when you buy an existing Houston practice instead of building one?

A built office starts empty and takes your standard. A bought office arrives with someone else's server, licences, backups, phone numbers and vendor contracts, some of them in the seller's name. The work moves to before closing: find out what exists, whether the data can be restored, and what can be transferred, before you own it.

A new suite in Katy is a list of things to buy. A practice in Pearland that has run for decades is a list of things to find. The seller's office manager may know where the server sits and which password opens it. She may not know when the backup last restored, whether the imaging software licence transfers with the sale, or which carrier holds the main number.

Legend's page on Houston Dentrix and imaging support makes the point that growing groups take on whatever each acquired office was already running. The detailed pre-closing checklist sits in the article on IT due diligence before you buy a practice. The Houston-specific additions are short:

• • Ask for a restore, not a report. A log showing that backups "completed" is not the same as watching a recent backup open on another machine. Ask to see one before closing.
• • Find out where the backup copy physically sits. A copy on a drive in the same building, or at the seller's home a few miles away, shares the same storm.
• • Read the internet and phone contracts for transfer terms. Some are in the seller's personal name; some auto-renew for multi-year terms.
• • List every remote-access tool on the network. The seller's IT person, the imaging vendor and the software vendor may each have one. Each should be known and either kept on purpose or removed on the day of transfer.
• • Check the property and insurance side as well as the IT side. Which floor the server sits on, and what the policy covers for equipment and lost production, are questions for the seller, the landlord and your insurer.

The last point has a Houston history. In 2017, Dr. Ian Healy, an orthodontist, bought a practice in a suburb northeast of Houston; one day later Hurricane Harvey's water filled the office four feet deep, as AAO News reported. He told AAO News that years of work toward owning a practice were wiped out overnight. Dr. Healy is not a Legend client, and his story is about far more than IT. It is the clearest reminder on record that the day you take ownership is the day the risk becomes yours.

Should every office run the same practice-management and imaging setup?

Usually the same platform, though not always the same database. Running the same practice-management and imaging software at every office makes training, support and reporting simpler. Whether offices share one database or keep their own is a separate decision that depends on the platform, the internet at each site and how often patients cross between offices.

A bought practice often runs a different platform from yours. Converting it is a real project, with data mapping, staff retraining and a period when the new office is slower. Some owners convert in the first months; others run both platforms for a year and convert when a hardware refresh is due anyway. Neither is wrong, as long as the decision is made deliberately and written down with a date.

Three questions shape the database choice:

1. 1. How often does a patient visit both offices? If hygiene is at one site and surgery at another, a shared record matters. If the offices serve separate neighbourhoods and rarely share a patient, separate databases cost less in complexity.
2. 1. Can office two work if the link to office one drops? With a server at the first office, the second office depends on both offices' internet. With a hosted platform, each office depends on its own. With separate databases, neither depends on the other.
3. 1. What does the software vendor support for several locations? Vendors publish their own multi-site requirements; get the current document from yours and file it with the growth plan.

Imaging needs its own answer. Acquisition stations for sensors, panoramic units and CBCT write to an archive; every operatory that reads those images needs a reliable path to that archive. A second office that reads large scans over a modest internet connection will feel slow on the days it is busiest.

On Legend's side, the published list is specific. Legend supports the IT environment of Dentrix, Eaglesoft, Open Dental and Archy for practice management, and of DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging for imaging. The platform pages for Dentrix IT support and Open Dental IT support, and the overview of practice-software and imaging support, describe that work. Questions about the software's own licensing, features and conversions belong with the software vendor.

What happens to every office at once when a storm hits Greater Houston?

Usually they all close together. Offices across the metro sit under one weather system, and many draw power through one delivery company, whose whole territory Hurricane Beryl hit in July 2024. A second Houston office is not a backup for the first; the plan needs a copy and a way of working outside the metro.

Many owners expect two offices to protect each other: if Cypress floods, Katy takes the patients. That holds for a local problem, such as a burst pipe, a cut fibre line or a break-in. It does not hold for a regional event, and Houston has a recent record of regional events:

• • Hurricane Beryl, July 2024. In its July 13, 2024 update, CenterPoint Energy wrote that Beryl reached its entire 5,000-square-mile service area. Every office inside that area was in the same event.
• • Winter Storm Uri, February 2021. The utility's release of February 18, 2021 put the peak at about 1.4 million of its customers affected, counting ordered load shedding and storm damage together. Ice, not wind, closed offices across the region that week.
• • The season itself. The National Hurricane Center's climatology says the Atlantic season "runs from June 1 to November 30," with most activity between mid-August and mid-October.

Check which delivery utility serves each of your addresses; for many offices across the metro it is the same one. Whatever the answer, a backup copy held at your other Houston office, or on a server in the same metro, can be just as dark as the office it was meant to protect. The plan needs at least one copy of the practice data held outside the region, and a tested way for staff to read the schedule and contact patients from wherever they are.

Storm mode by site. Agree these answers in May, not in the week a storm is named.

Treat the table as a planning frame and rehearse each row with your provider before relying on it. It deals with offices working together; preparing one building and its equipment before landfall is covered in the storm-season IT plan for Houston offices, and Legend's service for off-site copies is on its page about backup and disaster recovery for dental practices.

How should staff who work at more than one office be set up?

As one person, not as a visitor at each office. Give each employee a single account that works at every site they cover, grant access by role and by office, and remove all of it on the day they leave. Keep privacy-training records in one place for the whole group, not in each office's drawer.

Floating staff are where the shortcuts appear. An assistant who covers Katy two days a week is handed the Katy front desk's password because setting up her own access "can wait". A hygienist who left the Cypress office still has a working sign-in at the Pearland office, because nobody there knew she had one. Neither is malicious; both are how patient records end up opened by the wrong person.

A workable setup for staff across offices:

• • One account per person, in the shared tenant, used at every office. No shared front-desk logins, at any site.
• • Access by role and by office. Decide whether a floating assistant needs the schedule for one office or all of them, rather than copying a colleague's access.
• • Multi-factor sign-in on email and on every remote-access route, the same at each office.
• • A start checklist and a leaving checklist that name every system at every office: practice management, imaging, email, phones, payment terminals and vendor portals.
• • Removal on the last day, at every office at once, by one person who has the full list.

Texas adds a records point. Health and Safety Code Sec. 181.101 puts privacy training for each new hire within 90 days of the hire date, with a signed completion statement retained until six years after it was signed. For a group, the practical question is filing: when an employee works at three offices, decide which office or which person keeps that statement, so it can be found in one place. Its required content and how it fits your own practice belong with a compliance adviser.

The practice-level protections that sit alongside these records, from phishing to remote access, are covered in the Houston cybersecurity guide for practices.

Which vendors does a group now depend on, and who must tell whom about a problem?

More than most owners expect. Each office adds an internet carrier, a phone provider, payment processing, perhaps a lab portal and an answering service, alongside the practice-management and imaging vendors. Keep one list for the group: what each vendor touches, who holds the contract, and who calls whom if something goes wrong.

A single office can get away with contracts in a drawer. Three offices cannot. The list does not need special software; a shared spreadsheet with these columns covers it:

The last column matters because of a Texas rule. Business and Commerce Code Sec. 521.053(c) says a person who maintains computerized data containing sensitive personal information it does not own notifies the owner immediately after discovering the breach. How that applies to a given vendor is for your attorney to say; what the list gives you is a named contact at your practice for each vendor to reach.

Review the list each time an office opens, is bought or changes a system, and once a year regardless. Every vendor nobody remembers is a remote-access route nobody is watching.

How do phones and internet work across several Houston offices?

One phone system with every office on it lets calls roll from a closed office to an open one, and each office needs its own internet with a second path where the office cannot afford to stop. Decide early whether patients see one main number or a number per office; it shapes signage, listings and the call flow.

One number or one per office. One number for the group is simple to market but sends every patient through the same greeting and menu. A number per office keeps each office's identity and its listings, while the phone system still routes calls between sites. Many groups keep each acquired office's existing number, because patients have dialled it for years, and add routing behind it. Whichever you choose, write down the call flow for a normal day, a busy day and a closed office.

Phones depend on internet. Most current phone systems carry calls over the internet. If an office's internet drops, its phones may drop with it, unless calls are set to roll elsewhere. That is one reason the storm table above routes calls by situation. Legend's page on dental phone systems is a starting point for the options.

A second internet path. For an office that holds the shared database or the phone system, or that cannot close for a day, a second circuit from a different carrier is worth pricing. Check what each address can get on the FCC National Broadband Map before signing a lease; a building with only one carrier changes the plan. How the offices' networks are built and joined is covered on the page about network design for dental offices.

Same equipment where you can. Buying the same model of firewall, switch and workstation for each office makes problems easier to find and spare parts easier to share. It also means one set of settings to document rather than three.

What does IT cost when a practice has more than one office?

Three published lines apply: "Starting at $360 per month"; "Backup protection from $39.99 per month (storage-dependent)"; and "Hardware procurement, major cabling projects and software licensing are quoted separately." A group should request a quote broken out by office, with one-time project work kept apart from monthly support.

That is the whole of what Legend publishes about price; it does not publish a per-office formula, and this page does not invent one. A useful quote for a growing group separates three things:

• • Monthly support, listed per office, so you can see what changes when an office is added, bought or closed.
• • One-time work for the new or acquired office: equipment, cabling, internet and phone installation, migrations and conversions. Hardware procurement, major cabling projects and software licensing are quoted separately.
• • Backup, which depends on how much data each office holds. Imaging archives are usually the largest share.

Who you would be talking to, in Legend's published terms:

• • Headquartered in Dallas; 22+ years in dental IT (since 2004); served over 3,500 practices since 2004.
• • 24/7 monitoring, and a staffed 24/7 helpdesk at 1-800-794-1588.
• • In-house engineers; no outsourced first-level triage.
• • Onsite dispatch by appointment across served dental markets; remote-first nationwide.
• • The NOC, onsite dispatch and client technology roadmaps are overseen by Ian Lynch, who brings 22 years in dental IT.
• • Google: 4.8 rating · 173 Google reviews. Around Greater Houston, Legend has worked with practices such as Soothe Smile Studio in Cypress, northwest Houston, and Triple Oak Dental & Wellness in Katy, west of Houston; both project pages record a practice opening.

What to ask your IT provider before office two

Put these to any provider, including the one you have now, and ask for the answers in writing.