Vella ConnectTesting now · Eaglesoft, read‑only

It was always yours. They just kept it.

Twenty years of charts, ledgers, images and history, sitting on a server in your own building, in a format only your vendor can read. Vella Connect reads all of it, read‑only, into one record, with a note of where every piece came from.

Connect read‑only tonight Read the data promise

No inbound connection. No consultant. Yours whether or not you ever switch.

Vella Connect · Riverview Dental

Eaglesoft 21 · on‑premise · connected 9:12 pm

Read‑only

Your serverPractice‑management DBstays where it is

outbound only · nothing written back

One recordEvery fact, tied to its sourcetable · row · timestamp

First read7,778,759 records · 20 years✓

Reconciledagainst what the source said it held✓

Flagged4,118 images unreadable at sourcemanifest

Nothing changes in your PMS.Findings by morning

Where it actually lives

You could look at it. But, you couldn't have it.

Your practice's record is the most valuable thing in the building, and the terms of access were set by whoever sold you the software.

On a server, in your building

You bought the machine. You pay to maintain it, back it up and keep it patched. None of that makes the contents reachable.

In a schema only they read

The structure is proprietary. Table names, relationships and codes were designed for the software's convenience, not yours.

Behind a report writer

You can print what someone decided you might want. Anything else needs an export tool, a fee, or a consultant.

Twenty years of your own work, and the honest position is that you have a licence to view it.

Read-only is enough to run claims — ask us how →

Twenty years of rings

Your practice has twenty years of history. Your software can reach about three.

A tree records every season it has lived through. So does a practice: every patient, every plan, every claim, every write‑off. The difference is that nobody has cut your software open to see whether the early years are still readable.

What each band means

The last two or three years

Live in the active database. Reportable, searchable, mostly intact.

Four to ten years back

Archived, partially migrated, or carried through a conversion that dropped fields nobody checked.

Everything before that

Technically retained. Practically unreachable without a specialist, a fee, and a fortnight.

Vella Connect reads every ring — and tells you which ones were already damaged when it got there.

Illustrative. The real shape of your rings depends on your system, your conversions, and how many times you've changed software.

What comes out

Not a report. A manifest.

Every read returns an itemised list of exactly what was recovered, counted against what the source system said should be there, and a plain account of anything that didn't survive.

Reconciliation manifest — Willow Park Dental

Source: Dentrix G7 · on‑premise · records from 12 March 2006

Verified against source

Record typeRecoveredState

Patients

Demographics, contacts, coverage, relationships

47,912Complete

Appointments

Including cancellations, no‑shows and reschedules

1,284,006Complete

Procedures

CDT‑coded, with provider, tooth and surface

1,106,338Complete

Treatment plans

Presented, accepted, declined, and never scheduled

212,540Complete

Claims & remittances

Submissions, denials, appeals, ERAs

341,220Complete

Payments & adjustments

Insurance, patient, write‑offs, credits

894,771Complete

Clinical notes

Chart entries, perio charting, narratives

612,004Complete

Imaging

Radiographs, intraoral photos, pans — 2.1 TB

89,4164,118 unreadable at source

Fee schedules & contracts

By carrier, with effective dates

68 carriers11 missing since 2014 conversion

Communication history

Calls, texts, emails, recall attempts

3,190,552Complete

Years covered2006 – 2026 · 20 years, 3 software conversions

Records recovered7,778,759 of 7,793,888 expected

Recovered intact99.81%

Each record carries its origin (source table, source row, extraction timestamp), so any figure computed from it can be traced back to the thing it came from.

Manifest sealed sha‑256 · 7f2b91c4…e08a · countersigned to your account, not ours.

Illustrative manifest. Yours is produced from your own system, on the first read, and kept current after it.

We show you what's broken.

Four thousand images that won't open and eleven fee schedules lost in a conversion you had nothing to do with. None of that is our fault or yours — but you should find out from us, in writing, rather than from a patient two years from now.

And where every piece came from.

Connect isn't just the read. It's the trail: source table, source row, timestamp, attached to each record — which is what makes every number Vella ever shows you traceable back to something real.

The exit tax

Getting your own data out costs more than keeping it in.

Not by accident. Every hour and every fee between you and your records is a reason to stay where you are, and the bill always arrives at the exact moment you're trying to leave.

01

Somebody has to be paid to open it

The database is on your server, but reading it usefully takes a specialist who knows the schema. That's a conversion project with a scope document, a contract and a start date.

$5K–$25Ktypical quoted range for a full conversion

02

And it takes weeks you're still operating through

Extraction, mapping, validation, reconciliation, all while the practice keeps running and the data keeps changing underneath the copy someone already took.

4–12 weeksfrom signed scope to verified output

03

What arrives is often less than you had

Images stay behind. Note formatting flattens. Fee schedules and historical contracts quietly don't make the trip. Nobody tells you which. You find out later, usually from a patient.

Partialand rarely reconciled against the source

04

So most owners simply don't

The cost isn't really the money or the weeks. It's that a rational person looks at all of it, decides it isn't worth the disruption, and stays, which was the point of pricing it that way.

Stay putthe outcome the pricing was designed to produce

The lock was never technical. It was commercial.

Nothing about a dental database makes it genuinely hard to read. It's hard to leave because leaving being hard is worth money to somebody, and for twenty years nobody in the industry had a reason to change that.

Ranges reflect quotes commonly reported by practices for full‑history conversions. Yours will depend on your system, your version, and how many conversions you've already been through.

The promise

Yours either way. In writing.

Vella Connect works whether or not you ever become a customer. That isn't generosity. It's the only version of this that's honest, given what the page above is accusing everyone else of.

01

You keep it, in formats anyone can read

Open, documented, portable. Take it to us, take it to a competitor, or take it to a hard drive in a drawer. The read is the deliverable, not a hook.

02

We delete our copy when you say so

One request, no conversation about why. Deletion is confirmed in writing, with the date and what was removed — because a promise you can't check isn't one.

03

Nothing is learned from without permission

Your record is used to run your practice, full stop. Contributing anonymised patterns to the wider network is off by default, opt‑in, and reversible — and it never includes anything that identifies a patient or a practice.

04

Protected health information, handled properly

Read‑only, outbound only, encrypted in transit and at rest, with a business associate agreement in place before a single record moves. PHI is tokenised before it ever reaches a model.

If we ever need to hold your data hostage to keep you, we've already lost you.

Read the promise in full →

Then what

You don't have to switch to find out what it says.

Three rungs, and two of them are perfectly good places to stop. Most software makes you commit before it shows you anything. This runs the other way round.

Rung one

Connect, read‑only

Vella Connect reads everything, reconciles it against the source, and hands you a manifest of exactly what came back — including what was already broken.

You can stop here

Rung two

See what it says

Now that it's one record, it can answer questions: what's genuinely recoverable, where the money leaks, and whether your payers are paying what they contracted to. On your data, in weeks.

See what your data says →You can stop here

Rung three

Let her run it

If the first two rungs earned it, Vella takes the record and operates on it — the schedule, the claims, the follow‑up. Migration is on us, because by then you've already done the hard part.

Meet Vella →

Two of the three rungs cost us money and win us nothing.

We're aware. The alternative is asking a practice owner to hand over twenty years of history on the strength of a demo and a pricing page, which is exactly the arrangement that got the industry here.

It was always yours. Now you can actually hold it.

Every patient you've treated, every plan you've presented, every dollar you've collected — in one place, in a format you own, with a record of where each piece came from. Whatever you decide to do next.

Connect read‑only tonight Switching to Vella

Tell us which system you're on. That's the whole first conversation.

Open formatsDeleted on request, confirmed in writingBAA before anything movesYours whether or not you switch

The scalable operating system that actually improves financial performance on its own.

Launching Q4, 2026

hello@canopy.dental

Platform

Meet Vella Sentinel What‑If™ engine Morning Clarity Platform Architecture

Solutions

Solo Practices For DSOs Group Practices Switching to Vella HIPAA & Security

Company

About & Founders Investors Get a plan for your tools

Resources

Model your practice Canopy University

Intelligent practice. Zero friction.