Choosing an IT Company for a Prosthodontic Practice (2026)
The try-in is booked for early afternoon. The lab emails late in the morning: the full-arch scans you sent on Friday never arrived in the portal. Your IT company says the network is fine and it must be the scanner software. The scanner reseller says the scanner is fine and it must be the network. The patient drove in from an hour away. If you own a prosthodontic practice, you have been the person holding both phones, and you know that the IT company you choose decides how often that happens.
This guide is the buying side of that sentence. It sets out what a prosthodontic IT agreement has to cover, where each vendor's published support stops and the IT company's job starts, what good support looks like across one case, how to add a mill or printer without a bad month, the signs that a provider is a generalist, how to change providers with cases at the lab, and the questions and checks that belong in the signing meeting. For the technology itself, read the digital dental workflow, from the IT side; this page assumes you run it. Vendor documents checked 18 November 2026; written by Ian Lynch (22 years in dental IT; oversees the NOC, onsite dispatch and client technology roadmaps).
The right IT company for a prosthodontic practice owns everything your scanners, CAD seats, mills, printers, implant planning software and lab portals stand on: the computers, network and Wi-Fi, firewall rules, storage, backups and every login. Each vendor supports its own software; everything underneath, and the handoff when a fault sits between vendor and network, is the IT company's.
- A prosthodontic IT agreement has to name the scanner carts, CAD seats, printers, mills, planning seats, portal accounts and case-file storage; an item that is not written down is not in the price.
- The vendor supports its application; the IT company owns the PC, network, firewall rules, storage, backups and accounts underneath it, and the handoff between the two belongs to the IT company in writing.
- 3Shape, Align and Formlabs each publish network rules (5 GHz only and -60 dBm for TRIOS Share, 1 Mbps upload per iTero scanner, port 443 to named Formlabs addresses with no fixed IP ranges) that the IT company must apply before a device arrives.
- Good support is mostly invisible: free disk and a tested signal before the records visit, a checked CAD seat before design day, a confirmed portal before the try-in, and a monthly restore of every workflow folder.
- Switching IT companies with cases at the lab works when scanner registrations, CAD licences, printer cloud accounts, portal logins and firewall rules are inventoried before notice and nothing changes on a production day.
In this guide
- Which items belong in a prosthodontic practice's IT agreement?
- Vendor support or IT company: who owns each fault in a prosthodontic office?
- What does a well-supported prosthodontic case look like, stage by stage?
- What should an IT company do before a new scanner, mill or printer arrives?
- What does day-to-day IT care of an in-house dental lab involve?
- What gives away an IT company that has never supported a digital lab?
- Can you switch IT companies with cases at the lab?
- What to ask your IT provider about scanners, CAD seats, lab devices and portals
- What to verify before you sign
- How Legend Networking works with prosthodontic practices
- Frequently asked questions
- The bottom line
Which items belong in a prosthodontic practice's IT agreement?
A prosthodontic support agreement has to name what a general dental agreement leaves out: scanner PCs and their Wi-Fi, CAD workstations, networked printers and mills, implant planning seats and licences, lab portal accounts, growing case-file storage, vendor coordination, and maintenance windows that respect production days. An item the agreement does not name, the price does not include.
The ADA's National Commission on Recognition of Dental Specialties and Certifying Boards describes prosthodontics as the specialty "pertaining to the diagnosis, treatment planning, rehabilitation and maintenance of the oral function, comfort, appearance and health of patients with clinical conditions associated with missing or deficient teeth". In practice that means more scanning, more design, more manufacturing and more lab traffic per patient than a general office sees, and every one of those steps runs on a computer somebody has to look after. Below, that workflow becomes twelve agreement lines. Read any proposal against the last column; every line it leaves out comes back later as a separately billed project.
| Part of the practice | What breaks if nobody owns it | Who owns it | Must be written into the agreement? |
|---|---|---|---|
| Scanner carts and laptops (TRIOS, iTero, Medit, Primescan or another system you run) | Scans that will not post-process, upload or open on a second PC; a cart stuck on an unsupported Windows version | IT company for the computer, Wi-Fi, updates and backup; the scanner maker or reseller for the scanner software | Yes, naming who signs off Windows updates on scanner PCs and how often free disk is checked |
| Wi-Fi where the scanners are used | Uploads that fail at the far chairs, or a scanner that cannot join the network | IT company (survey, design, fixes); the scanner maker publishes the spec | Yes, with a signal survey at every scanning position as a deliverable |
| CAD workstations (exocad DentalCAD, 3Shape Dental System or another system you run) | A design seat that slows to a crawl on full-arch cases after an update; a licence device the PC can no longer see | IT company for the PC, drivers, Windows, file paths and backup; the CAD reseller for the application and licence | Yes, with the vendor's approved specification named as the standard the PC is kept to |
| Printers and mills (SprintRay, Formlabs, a mill or another system you run) | A design PC that cannot find the printer; cloud print services blocked by the firewall; a job lost when power dips | IT company for the network path, firewall rules and the PC that drives the device; the maker for the device and its software | Yes, with the maker's published network list applied and kept |
| Implant planning seats (coDiagnostiX, Blue Sky Plan, DTX Studio Implant or another system you run) | Plans that will not open on the second PC; a dongle or account licence that stops working after a move | IT company for the PC, licence server or account access, and backup; the planning vendor for the software | Yes, with the licence model recorded (dongle, dongle server or account) |
| CBCT acquisition PC and imaging server | Volumes that cannot be exported for the lab or surgical guide; a full disk on the imaging server | IT company for the PC, server, storage and backup; the imaging vendor for its software and bridge | Yes, with storage growth reviewed on a stated schedule |
| Practice management and imaging software (Dentrix, Eaglesoft, Open Dental, Archy; DEXIS, Vatech, Carestream, Planmeca Romexis) | The chart, the schedule and the imaging bridge, as in any dental office | IT company for the server or internet line, workstations, backup and accounts; the vendor for the application | Yes, as in a general agreement |
| Case-file storage (scans, designs, CBCT exports, photos) | Files on one cart or one CAD PC that no backup job includes; a disk that fills mid-case | IT company | Yes: a written map of where files live, which folders are in the backup, and a dated restore test |
| Lab portals and vendor clouds (3Shape Communicate, MyiTero, Medit Link, DS Core, your labs' own portals) | A shared login that outlives the person who made it; a lab that can still see your cases | The practice names an owner per account; IT company runs the joiner and leaver process and multi-factor sign-in | Yes, with the account list as a living document |
| Vendor coordination | A fault that sits between the scanner reseller and IT and gets bounced for a day | IT company owns the ticket end to end and brings the vendor onto it | Yes: the agreement states which side places the vendor call and who stays on the ticket |
| Maintenance and update windows | A reboot during a design session or a print run | IT company | Yes: only when nothing is being scanned, designed or printed, and never on a records or try-in day you have flagged |
| Monthly reporting | Nobody knows which workflow PC missed its backup or is out of disk | IT company | Yes, with the workflow PCs listed by name |
Legend's own approach to each layer is set out on its page on IT support for prosthodontic practices. Everything below is written from the buyer's chair, as a standard to hold any provider to, Legend included.
Vendor support or IT company: who owns each fault in a prosthodontic office?
The vendor supports its application: errors inside the scanner, CAD, planning or printer software, its licence, its portal and its training. Beneath it, the IT company answers for the PC, Windows and drivers, the network and Wi-Fi, firewall rules, storage, backups and accounts. Whoever you sign with should accept the handoff as theirs, in writing.
Scanners cause a large share of the support calls in a digital dental office, and when one fails, its maker often answers that the fault is a driver on the practice's PC. That is the daily reality the agreement has to settle. The table below takes each system a prosthodontic office runs and splits it three ways: what the maker's own published documents put on the practice's network and PC (and so on the IT company), what the maker keeps, and the gap that nobody owns unless the agreement says so. Every vendor line was read in the vendor's own document on 18 November 2026; where a vendor's requirements page could not be opened, the row says so and sends you to the Legend post where it was verified.
| System | What the maker's documents put on your network and PC (IT company) | What the maker keeps (vendor or reseller) | The gap nobody owns unless the agreement says |
|---|---|---|---|
| 3Shape TRIOS with TRIOS Share (wireless) | 3Shape says Share "is limited to work with 5GHz frequency band only", wants a signal "stronger than -60 dBm at the scanner location", lists TCP ports 20-21, 80, 23795 and 23796 on the scanner, says "Hidden SSIDs are not supported" and that "Redirection of traffic done for example by Captive Portals must be disabled" | Scanner hardware, TRIOS software, Dental System, 3Shape Communicate, licences | Who checks the signal at a new chair position before a cart is moved there, and who re-tests after an access point is replaced |
| iTero | Align's Element 5D manual tells clinics to "ensure that your internet connection upload speed is at least 1Mbps per scanner", says "Open the following ports (in case of a firewall): 80 - HTTP - TCP 443 - HTTPS - TCP", and rates Wi-Fi "Excellent >-50 dBm Good -50 to -60 dBm" | Scanner, software, MyiTero, Invisalign and lab connections | Who adds up the upload the office needs when a second scanner arrives, and who owns the FTP rule the manual says not to block |
| Medit, Primescan and other scanners | Each publishes its own network and PC rules; Medit's pages could not be opened from here today, so none is quoted. The verified specs are in intraoral scanner IT requirements | Scanner, software, Medit Link, DS Core | Same as above: the signal survey and the upload budget |
| exocad DentalCAD and 3Shape Dental System (CAD) | The vendor's approved PC specification, which the IT company keeps the workstation to through every Windows and graphics-driver update. exocad's own page could not be opened from here today; the October 2026 figures are in dental CAD and scanner computer requirements | The CAD application, the licence (dongle or account), module updates, design support through the reseller | Who tests a full-arch design file after a driver update before the next design day, and who holds the dongle inventory |
| Formlabs printers and PreForm | Formlabs says "PreForm and Formlabs hardware communicate with Dashboard via port 443 (HTTPS), api.formlabs.com, and gateway.formlabs.com", asks that api.formlabs.com, gateway.formlabs.com and *.amazonaws.com are not blocked, warns that "we cannot provide a list of exact FQDNs" or "fixed IP ranges", uses "a single port (35)" for print upload, syncs time over "NTP (UDP port 123)" and "cannot be configured to use a customer-managed internal NTP server" | Printer, resin, firmware, PreForm, Dashboard | Who applies the allowlist on a firewall that filters by address, and who decides whether the printer runs "Via USB, without network access of any kind", as Formlabs also allows |
| SprintRay and other printers and mills | Each maker publishes its own list of addresses and ports; SprintRay's support articles could not be opened from here today, so none is quoted. The buying and network guide is 3D dental printers: buying and IT guide | Device, firmware, slicer, cloud design services | Who asks the maker for the list before the device ships, and who keeps it when the firewall is replaced |
| coDiagnostiX, Blue Sky Plan, DTX Studio Implant (implant planning) | The PC and, where the licence is a dongle, the USB port or dongle server; Dental Wings now describes coDiagnostiX plans as "dongle-free and managed through our AXS platform", so some seats are account-based | The planning software, licence terms, guide design services | Who records which licence model each seat uses, so a PC rebuild or a move does not strand a plan. Requirements are compared in implant planning software computer requirements |
| CBCT (DEXIS, Vatech, Carestream, Planmeca or another system you run) | Acquisition PC, imaging server, storage, backup, the bridge into the chart | Imaging software, the unit, calibration, its own support plan | Who watches storage growth and who exports DICOM for a surgical guide when the usual person is away. See CBCT computer and network requirements |
| Practice management and imaging software | Server or internet line, workstations, Windows, SQL where used, backup, accounts | The application, its updates, its bridges | Who schedules the vendor's update so it does not land on a records day |
| Lab portals and vendor clouds | Named accounts, multi-factor sign-in where offered, removal of leavers, the account recovery address | The portal, its retention, its own backups | Who owns each account in the practice, in writing, with a date |
Two dates sit under every row. Microsoft's lifecycle pages say "Windows 10 will reach end of support on October 14, 2025", and Windows Server 2016 reaches its extended end on 12 January 2027 (Microsoft shows 1/13/2027 in Pacific time). A scanner cart or imaging server still on either is the IT company's problem to raise, with the vendor's own compatibility list in hand, not something it discovers when a case fails. For the server, the options and dates are laid out in Windows Server 2016 end of support for dental offices.
What does a well-supported prosthodontic case look like, stage by stage?
Good prosthodontic IT support is mostly invisible: before the records visit the scanner cart has free disk and a tested signal, before design day the CAD seat has been checked after its last update, before the try-in the lab portal has been confirmed, and between cases every workflow folder has been restored from backup.
The clinic sees IT only when something fails. The agreement should describe the work that stops failures, stage by stage. The table is written for a full-arch case because it touches every device; a single crown touches a subset.
| Case stage | What IT must already have done | What IT does if it fails that day | What you should be able to see afterwards |
|---|---|---|---|
| Records visit (scans, CBCT, photos, face scan) | Scanner cart patched on the maker's approved schedule, free disk above the maker's cleanup threshold, Wi-Fi signal surveyed at that chair, CBCT acquisition PC and server with headroom | Rules the PC, Wi-Fi and firewall in or out first, then calls the scanner or imaging vendor with you and stays on the ticket | A ticket that names the fault, the fix and the side that owned it |
| Case sent to the lab | Portal accounts named and working, upload budget covers every scanner, the firewall passes the ports the maker lists | Checks the PC and the line, then the portal vendor; confirms with the lab what they can see | The case ID, the time sent and the confirmation from the lab in the ticket |
| Design (in-house CAD) | The CAD seat kept to the vendor's specification, graphics driver and Windows checked after each update against a saved full-arch file, licence device or account inventoried | Restores the last known-good driver, moves the licence or opens a reseller ticket with the version numbers already filled in | A change log for the CAD seat: what was updated and when it was tested |
| Make (print or mill in-house) | The device reachable from the design PC, the maker's allowlist applied, the device on clean power, the job folder in the backup | Fixes the network path or firewall rule; if the device itself is the fault, hands over to the maker with the device log | The allowlist on file, dated; the device's network address recorded |
| Try-in and remake | Any new scan follows the records-visit row; the CAD project folder from the first visit is still in the backup and has been restored once | As above | The monthly restore log shows the case folder opened |
| Delivery and archive | Every folder the case touched (scanner, CAD, print, CBCT export, photos) is in a backup job and has been restored and timed this month | Not applicable if the earlier rows were done | The restore log with the date, the case and how long it took |
Between cases, the work is scheduled, not reactive: patch windows agreed with you and kept off records and try-in days; a disk check on every scanner cart and CAD seat; a review of who holds each portal account; a restore test of one recent case every month. A restore-test method is set out step by step in the dental backup and disaster recovery checklist, and the retention and account questions that sit around lab cases are in how to send scans, STL and CBCT files to your dental lab safely.
The monthly report is where you check that the quiet work happened. For a prosthodontic office it should list, by name: each scanner cart and CAD seat with its Windows version, last patch date and free disk; the backup status of each workflow folder, not only the server; the date and result of the last restore test; portal and email accounts added or removed; tickets opened, closed and still open, with the vendor side marked. The HIPAA Security Rule's data backup plan standard, 45 CFR 164.308(a)(7)(ii)(A), asks for procedures "to create and maintain retrievable exact copies of electronic protected health information"; a report that shows a restore, not only a backup, is practical evidence that the habit exists. Reading that standard against your own practice is work for your compliance adviser; the IT company supplies the evidence.
What should an IT company do before a new scanner, mill or printer arrives?
Before a new device ships, the IT company should read the maker's published PC and network requirements, confirm or order the PC, plan the device's place on the network with the maker's address and port list applied, survey the Wi-Fi where it will be used, add its folders to the backup map, and name the account owner.
Most bad months in a prosthodontic office start with a device that arrived before IT knew about it. Formlabs, for example, publishes that its printers reach Dashboard over port 443 at named addresses and that it cannot give fixed IP ranges; a firewall configured by address alone will block that printer on day one, and the fix is a rule, not a fault. Use this list as the work order you hand the IT company the day you sign the purchase.
Before the device ships
- Send the IT company the maker's PC requirements and network requirements pages, or ask it to obtain them from the reseller, and get written confirmation of what will change.
- Agree which PC will drive the device: a new one to the maker's specification, or an existing one that meets it today, not one that "should be fine".
- Decide where the device sits on the network: the lab-device segment the design PC can reach, with the maker's addresses and ports allowed, or, for a printer the maker allows to run offline, a USB connection with no network at all.
- For a wireless scanner, book the signal survey at every position where it will be used, against the maker's published signal figure.
- Add the device's file locations to the written file map and the backup job before the first case, and name who owns its cloud or portal account.
On install day
- The maker or reseller installs the device and its software; the IT company is present or on the line for the network join, the firewall rule and the first test file.
- A first real file goes end to end: scan to design, design to printer or mill, case to portal, and the IT company records what was tested.
- The device's network address, firmware version, software version and account owner go into the inventory the same day.
In the first month
- The device's folders appear in the monthly report and the first restore test includes a file from it.
- The maker's update cadence is written into the maintenance calendar so firmware and software updates land on a non-production day.
If you are adding a device as part of opening or moving, the planning runs earlier and wider; our guide to specialty practice IT in Houston walks through when IT should be in the room for a specialty office, and the same sequence applies in any city.
What does day-to-day IT care of an in-house dental lab involve?
An in-house lab is a small manufacturing floor beside a clinic: design PCs, a printer, a wash and cure unit, sometimes a mill, all networked. The IT company runs it by keeping those devices on their own segment, applying each maker's allowlist, scheduling updates off production days, watching disk and power, and testing the path from design PC to device.
Treat the lab as its own environment inside the practice, with its own rules.
| In the lab | The IT company's job | Why prosthodontists feel it |
|---|---|---|
| Network segment | Puts printers, mills and furnaces with network ports on a lab-device segment the design PCs can reach, and keeps clinical and guest traffic off it | Design software often finds devices by network discovery; a device on the wrong segment simply disappears from the print setup |
| Allowlists | Applies and records each maker's published address and port list on the firewall; re-applies it when the firewall is replaced | Formlabs, for one, publishes named addresses and no fixed IP ranges, so a rule written by address breaks silently |
| Time and updates | Lets the devices reach the time servers the maker names (Formlabs printers use NTP over UDP 123 and cannot use an internal time server) and schedules firmware and software updates off production days | A device with the wrong time or a mid-run update can refuse a job or fail one |
| The design PC | Keeps it to the CAD vendor's specification, holds a saved full-arch test file and opens it after every driver or Windows update | A design seat that "works" on a single crown can stall on a full arch; the test file catches it before the patient does |
| Free disk | Alerts before the scanner maker's cleanup threshold and before the CAD project folder fills the design PC | Raw scan data and design projects are large; a full disk is a lost case, not a slow one |
| Power | Puts the design PC, printer and mill on protected power sized by the maker's figures, and tells you what a protected supply can and cannot ride out | A print or mill job interrupted by a flicker is a remake; the resin and the chair time are gone either way |
| Backup | Includes the design PC's project folder and the print job folder in the backup job, and restores one lab file in the monthly test | Most practice backups cover the server only; the lab files live on the lab PCs |
| Who to call | Owns the ticket when a job fails, rules the network and PC in or out first, then brings in the maker with the device log already pulled | The maker supports its device; nobody else will coordinate across the two unless the agreement says so |
None of this requires the IT company to know how to design a crown. It requires the IT company to treat the lab's devices as production equipment with published requirements, and to have read them.
What gives away an IT company that has never supported a digital lab?
The signs are consistent: every scanner, CAD or printer fault is "a vendor issue" with no one owning the handoff; the proposal has no line for scanner PCs, CAD seats, lab devices or portal accounts; nobody has asked where your case files live; updates happen on whatever day the technician is free; and no prosthodontic project can be shown.
Below, each signal sits beside what it tends to cost a prosthodontic office and one question that brings it into the open.
| Signal | The cost to the practice | Ask this before signing |
|---|---|---|
| "That's a vendor issue" closes the ticket | A day of bounced calls on a try-in day; you become the coordinator | "When a fault sits between the scanner software and the network, who owns the ticket until it is fixed, and will you call the vendor with us?" |
| The proposal has no line for scanner carts, CAD seats, printers, mills or portal accounts | Each is "out of scope" the first time it fails, and billed as a project | "Show me where in the agreement each of our lab devices and portal accounts is named." |
| Nobody asked where your scans, designs and CBCT exports live | Files on one cart or one CAD PC that no backup includes; discovered on the day a disk dies | "Which of our workflow folders will be in the backup on day one, and when will you restore one to prove it?" |
| Updates land whenever the technician is free | A reboot during a design session; a driver change that stalls full-arch work the next morning | "Which days are protected from updates, and how do you test the CAD seat after a driver update?" |
| The firewall is configured by address only, and nobody has asked the makers for their lists | A new printer or scanner blocked on install day; a cloud design service that stops after a firewall change | "How do you handle a maker that publishes addresses but no fixed IP ranges?" |
| No prosthodontic project you can check | You are the first; every lesson is learned on your cases | "Which prosthodontic or in-house-lab offices have you set up, and can I see the project page or speak to one?" |
| Scanner cart on an unsupported Windows version, unmentioned | A cart that the maker will not support, found out when a case fails | "Which of our devices are past their Windows or vendor support dates, and what is the plan?" |
| Shared "front desk" login on a lab portal, unremarked | A former employee who can still open patient scans | "How are portal accounts named, protected and removed when someone leaves?" |
If three or more of these describe your current provider, read the switching section next. If you are comparing providers for the first time, the general evaluation lives in how to choose a dental IT company, and this page adds the prosthodontic layer on top.
Can you switch IT companies with cases at the lab?
Yes, if the switch is planned around the lab calendar rather than the IT company's. Build a handoff inventory of every scanner registration, CAD licence, printer cloud account, planning licence, portal login, static address and firewall rule before you give notice, overlap the two providers for one full case cycle, and change nothing on a production day.
Switching is where prosthodontic offices get hurt, because the things that break are not the server. They are the scanner that was registered to the old company's email, the CAD dongle nobody can find, the printer's cloud account under a technician's name, the static address the mill was given by hand, and the lab portal whose recovery email went to the old provider. For the general method read how to switch dental IT providers without downtime; what a prosthodontic office adds is the inventory below. Fill every row before notice.
| Account or setting | Where it tends to sit | Have this before you give notice |
|---|---|---|
| Scanner software accounts and registrations (3Shape Account, MyiTero, Medit Link) | Created at install, often by the reseller or the IT technician, with an email you do not control | The account owner changed to a practice address; a list of which carts are registered to which account |
| CAD licences (dongle, dongle server or account) | A USB dongle in a drawer or on the design PC; a dongle server on the office server; an account at the reseller | The dongle inventory with serial numbers; the licence account's owner and recovery email; the reseller's contact |
| Printer and mill cloud accounts (Dashboard, cloud design services) | Under whoever set the printer up | The account moved to a practice owner; the maker's allowlist exported from the firewall |
| Implant planning licences | A dongle, a dongle server or a vendor account, depending on the product and plan | The licence model per seat written down, with the vendor account owner |
| Lab portals and vendor clouds | Shared logins; recovery emails pointing at a person | Named logins per person, multi-factor sign-in on, recovery address a practice mailbox |
| Static addresses and firewall rules for lab devices | In the firewall and in the devices themselves, undocumented | An export of the firewall configuration and a list of every device address |
| Domain registrar, DNS, Microsoft 365 or Google Workspace administrator | Often held by the IT company | Administrator roles on practice-owned accounts, as the switching guide sets out |
| Remote access and monitoring agents | On every PC, including scanner carts and CAD seats | A list of which agents are installed where, so the old ones are removed only after the new ones are working |
| The file map and backup | The old provider's documentation, if any | The written map of where every workflow file lives and which jobs back it up; a restore performed and witnessed before notice |
Then sequence the switch against your cases, not the calendar month.
- Before notice. Complete the inventory. Have the current provider restore one full case (scan, design, CBCT) to a test folder while you watch. Read the exit terms.
- Give notice with a date that falls after your next try-in cycle. The new provider reads the inventory and the makers' requirements pages and writes its plan.
- Overlap for one full case cycle. The new provider installs its monitoring beside the old agents, surveys the Wi-Fi at the scanning positions, and tests the design-to-device path, without removing anything.
- Move the accounts. Scanner, CAD, printer, planning and portal accounts move to practice-owned addresses with the new provider watching; nothing is deleted.
- Cut over on a non-production day. Firewall and remote-access changes happen when no case is being scanned, designed, printed or sent.
- Remove the old provider's access last. Only after a real case has gone scan to lab to design to device under the new provider, and after the first restore test from the new backup opens the files. The HIPAA Security Rule's termination procedures specification, 45 CFR 164.308(a)(3)(ii)(C), asks for "procedures for terminating access to electronic protected health information when the employment of, or other arrangement with, a workforce member ends"; your compliance adviser owns how that applies to a departing vendor.
- Thirty days of acceptance. Every ticket in the first month is reviewed with you against the scope table at the top of this page.
A switch done this way is quiet. A switch done on the IT company's schedule is the try-in that opens this page.
What to ask your IT provider about scanners, CAD seats, lab devices and portals
Ask each question in writing and keep the answers with the agreement. A specific answer with a name, a date or a document is a good sign; general reassurance is not. The questions below are shaped around the contract, not the technology; the technology scorecard is in our digital workflow guide.
Scope and ownership
- Which of our scanner carts, CAD seats, printers, mills, planning seats and portal accounts are named in the agreement, and which are excluded?
- If a fault falls between a maker's software and our network, whose ticket is it, and will you be on the vendor call with us?
- Which makers' requirement documents have you read for our devices, and where are they kept?
Files and recovery
- Which of our workflow folders (scanner cases, CAD projects, print jobs, CBCT exports, photos) will be in the backup on day one?
- When will you restore one full case to prove it, and how will we see the result each month?
- Where do you alert on free disk for the scanner carts and CAD seats, and against which maker figure?
Change and updates
- Which days are protected from updates and reboots, and how do you record our records, design and try-in days?
- How do you test the CAD seat after a Windows or graphics-driver update, and with which file?
- How do you handle a maker that publishes addresses but no fixed IP ranges on our firewall?
Accounts and people
- Who will own each scanner, printer, planning and lab-portal account in our practice, and how are leavers removed?
- Is multi-factor sign-in on for every account that offers it, and who holds the recovery addresses?
- Who in your team has set up a prosthodontic or in-house-lab office before, and will they be on our account?
Exit
- If we leave, in what form do we receive the file map, the firewall export, the device inventory and the account list, and within how many days?
- Which remote-access and monitoring agents will you remove, and how will you prove it?
For the general contract questions on term, pricing structure and exit, bring 20 questions to ask before signing a dental IT contract to the same meeting, and read what a dental IT SLA should actually say before you compare response promises.
What to verify before you sign
Verify five things with evidence rather than assurance: a prosthodontic or in-house-lab project you can see; the written scope with your devices named; the pricing structure and what moves it, without taking a price as a promise of scope; the exit terms and the form your documentation comes back in; and the names of the people who will actually hold your account.
- A project you can check. Ask for a published project page or a reference for a prosthodontic or in-house-lab office. Legend's are linked below; any provider should have an equivalent.
- The scope in writing. Lay the scope table at the top of this page beside the proposal. Every row either appears in the agreement or is listed as excluded. "Comprehensive support" is not a row.
- The pricing structure, not the price. Understand what moves the monthly figure (seats, devices, locations, storage) and what is quoted separately (hardware, cabling, licences). A low figure with the lab devices excluded is not a low figure. If you want one provider to own the whole environment rather than a break-fix arrangement, this is the moment to compare managed IT services for dental practices line by line against what you are being offered.
- Exit terms and documentation. The agreement should say what you receive when you leave and in what form, and that the file map, inventory and firewall export are yours.
- The people. Names, not a team size. Who answers, who escalates, who has set up a digital lab before. A shortlist can start from a published ranking: the best dental IT companies list records what each company publishes about itself, and this evidence test applies to every name on it, Legend included.
If the practice is in Texas, the city pages are the local layer: dental IT support in Houston is the nearest to the Pearland project linked below, and the locations index covers the rest. A national provider's page should still say how onsite work is arranged where you are.
How Legend Networking works with prosthodontic practices
Legend Networking is a Dallas-based dental IT company. Served over 3,500 practices since 2004. Legend supports the IT environment for Dentrix, Eaglesoft, Open Dental and Archy, and for DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging. Around the scanners, CAD seats, printers, mills and planning software a prosthodontic practice runs, the split is the one this guide describes: the vendor or reseller supports the application, and the IT company answers for the ground it runs on.
Support is remote-first nationwide, with onsite dispatch by appointment across served dental markets. In-house engineers; no outsourced first-level triage. Systems have 24/7 monitoring, and the helpdesk is staffed 24/7 at 1-800-794-1588. On Google, Legend holds a 4.8 rating from 173 reviews. Two prosthodontic projects are documented on Legend's own project pages: a prosthodontic practice opening in Georgetown, Texas and the grand opening of a new prosthodontic practice in Pearland, Texas.
If you are looking for a provider rather than a specialty guide, start with our page on dental IT support, which sets out how support, monitoring and onsite visits are arranged nationwide.
Frequently asked questions
Is a general dental IT agreement enough for an office with a digital lab?
The server, workstations and firewall are the same kind of equipment. What differs is the digital lab beside the clinic: scanner carts, CAD seats, printers, mills and planning software, each with a maker's published PC and network rules, plus lab portals and case files that live outside the practice software. A prosthodontic agreement has to name those items; a general one usually does not.
Must the IT company know exocad or 3Shape Dental System before it can support us?
It does not need to design in them. It needs to have read each maker's PC and network requirements, keep your workstations to that specification through every update, apply the makers' firewall lists, and know who to call at the reseller when a fault is inside the application. Ask which requirement documents they have read for your devices and where they keep them.
Who fixes a scan that will not reach the lab: the scanner company or the IT company?
Start with the IT company, which should rule the PC, Wi-Fi, firewall and internet line in or out quickly, then hand over to the scanner or portal vendor with the case ID and the error already recorded. The agreement should say the IT company owns that ticket until it is closed. Faults parked between the two sides are the ones that cost a try-in appointment.
What prep should happen before a mill or 3D printer joins the practice?
Read the maker's PC and network requirements, confirm or order a PC that meets them, plan the device's place on the lab-device segment with the maker's addresses and ports allowed, add the device's folders to the backup map, name the cloud account owner, and run one real file end to end on install day. Firmware updates go into the maintenance calendar on non-production days.
Can a prosthodontic practice be supported remotely?
Monitoring, patching, backup checks, account changes and first-line fixes are all done remotely, and that is most of the job. Some tasks need hands on site: a Wi-Fi survey at the scanning positions, a cabling change for a new mill, a cart that will not boot. Ask how onsite visits are arranged where you are, and how remote and onsite staff share one ticket.
Will our scanner registrations and CAD licences survive a change of IT company?
Nothing should change if the accounts and dongles are inventoried first. Scanner registrations, CAD licences, printer cloud accounts and planning-software licences belong to the practice; move each to a practice-owned email before notice, record dongle serial numbers, and keep the reseller contacts. The risk is an account created under a technician's name that nobody noticed until the technician was gone.
How long does a change of IT company take when cases are at the lab?
Plan it around one full case cycle rather than a number of days: inventory before notice, an overlap while the new provider installs monitoring and tests the path from design PC to device, account moves, a cutover on a non-production day, removal of the old provider's access after a real case has run end to end, then a month of reviewed tickets.
Whose name should be on our lab portal, domain and Microsoft 365 accounts?
The practice should, with named people. Lab portals and scanner clouds hold patient scans, so each person has their own login, multi-factor sign-in is on where offered, and recovery addresses are practice mailboxes. The domain registrar, DNS and Microsoft 365 or Google Workspace administrator roles sit on practice-owned accounts that the IT company is granted access to, not the other way round.
How can we tell whether an IT company has worked in prosthodontic offices before?
Ask for a published project page or a reference for a prosthodontic or in-house-lab office, ask which makers' requirement documents the team has read for your devices, and ask who on the account has set up a digital lab before. A provider that can only describe general dental work is a provider that will learn your workflow on your cases.
Which figures should be watched on our scanner carts and CAD seats?
Free disk against the maker's cleanup threshold, Windows version and patch state against the maker's compatibility list, graphics-driver version on the CAD seat, backup status of the case and project folders, and the health of the remote-access agent. The monthly report should list each cart and seat by name with those figures, and the restore test should include a file from one of them.
The bottom line
Whether you are replacing a provider or choosing your first, start with the file map, the device inventory and the account list, because those are what a switch or a bad month puts at risk. The Free Dental IT Assessment is a sensible first step: it returns written findings and prioritized recommendations on your computers, software, network security, backups and performance. After that, measure whichever provider wins against the twelve-line scope table near the top. Legend's page on dental IT support explains how we work with practices nationwide, and the IT support for prosthodontic practices page covers the specialty itself.

