Importing data from AlfaDocs into a new management software: the guide
How to export patients, medical records, treatment plans, price lists, and invoices from AlfaDocs and import them into a new management software without data loss and in compliance with GDPR.

Importing Data from AlfaDocs into a New Practice Management Software: The Guide
To import data from AlfaDocs into another practice management software, four steps are needed: take stock of what you want to bring with you, request a complete export in readable formats (CSV or Excel for tabular data, PDF for signed documents), check and clean the files, then import them and spot-check them before shutting down the old system. The real work is not clicking export. What matters is deciding what to migrate, in what order, and how to protect health data that by law are special categories of data. In this guide, you will find the method we use with practices that switch to Treatbase, along with the checks to perform on the files and the most common errors.
TreatbaseSwitch to a practice management software without losing your dataTreatbase is a dental practice management software with simple and fast data migration, designed to support practices during the transition.Discover Treatbase
In brief
Start with the inventory, not with the export. List the data you use every day (demographics, records, treatment plans, price list, schedule, invoices, consents) and decide what is really needed in the new software.
Request structured formats. Tables should be exported in CSV or Excel, signed documents and images in their original formats, with an index linking them to each patient.
Check the files before importing them. Character encoding, delimiters, date formats, tax IDs (fiscal codes), and duplicates are the most frequent causes of errors.
Treat the migration as processing of health data. Encrypted transfers, restricted access, written agreement with the vendor: the GDPR requires it.
Plan for an overlap period. Keep the old account in read-only mode until you have spot-checked that everything has arrived.
Table of Contents
What you can take from AlfaDocs
Before exporting: inventory and schedule
Step-by-step migration
How to prepare and check files
Privacy and security during migration
Frequent errors and how to solve them
Our point of view
Switching to Treatbase
Frequently Asked Questions
Sources
What you can take from AlfaDocs
A dental practice management software contains much more than a list of patients. Before requesting any export, it is best to be clear about which data categories exist in your practice, in what format they are usually exported, and how critical they are to daily work.
Data | Typical export format | Priority | Practical notes |
|---|---|---|---|
Patient demographics | CSV or Excel | Essential | It is the key to everything: all other data links back to the patient |
Medical history and clinical charts | CSV, Excel, or PDF per patient | Essential | Verify that clinical notes remain linked to the date and the operator |
Odontogram and completed procedures | CSV or Excel | High | Check tooth numbering and procedure codes |
Treatment plans and estimates | CSV, Excel, or PDF | High | Distinguish between accepted, ongoing, and completed plans |
Procedure fee schedule | CSV | High | The fee schedule is easily rebuilt, but prices must match |
Calendar and future appointments | CSV or Excel | High | Future appointments are the most urgent to migrate |
Invoices and payments | CSV, Excel, XML of electronic invoices | High | Issued invoices remain valid: needed for history and deposits |
Signed informed consents | Essential | Must be preserved intact, with the original signature | |
X-rays, photos, documents | Original files (JPG, PDF, DICOM) | Medium or high | Large file sizes: plan transfer times accordingly |
Recalls and reminders | CSV or Excel | Medium | If missing, they can be reconstructed from the last visit |
The rule we give practices is simple: everything of clinical or legal value must be taken with you in full; operational details (recalls, calendar colors, settings) can be rebuilt in the new system, often better than before.
Who owns the data
Your patients' data belongs to the practice. Under the GDPR, you are the data controller, while the software vendor acts as the data processor. Article 28 of EU Regulation 2016/679 requires that the contract with the processor stipulates that, at the end of the service, data must be deleted or returned at the choice of the controller. When you request the export, you are exercising exactly this: the return of your data.
Before exporting: inventory and schedule
A well-executed migration is decided before touching a single file. Hold a brief meeting with those who use the practice management software every day: owner, hygienists, reception, administration.
What to decide in that meeting:
The scope. Active and historical patients? How many years back? Many practices migrate everything, but separating patients without visits for a long time makes checking much faster.
The transition date. Choose a time with a lighter workload, for example, a weekend or during the summer closure week. Avoid days when the front desk is busy with submissions and tax deadlines.
Data freeze. From the moment of the final export, no one should enter any more data into the old software. Otherwise, you will end up with appointments and payments recorded in two different places.
The point of contact. One person from the practice coordinates the migration and signs off on the final checks. Usually, this is the office manager.
The outgoing contract. Check the duration of the current subscription and the cancellation terms, so you can keep the old account active in read-only mode for as long as necessary.
Step-by-step migration
Here is the sequence that works for most practices, whether single-location or multi-site.
Request a complete export. Write to your current vendor requesting the export of all practice data, specifying the categories from the table above. Explicitly ask for signed consents and attached documents, which often get left out of a standard tables-only export.
Test export. Before the final export, run a preliminary round on a copy: you need this to understand file structure, column names, and formatting issues.
Field mapping. Map each column of the source file to the corresponding field in the new management software: “Last Name” to last name, “Tax ID” to tax ID, and so forth. This is where you determine whether a piece of information lands in the right place or ends up in a general notes field.
Data cleaning. Eliminate duplicates, standardize dates and phone numbers, correct invalid tax IDs. We discuss this in detail below.
Test import. Upload a subset, for example 50 patients selected from both simple and complex cases, and check that records, treatment plans, and invoices read correctly.
Final export and data freeze. On the agreed day, freeze the old system, perform the final export, and import it.
Spot checks. Compare the numbers: total patients, future appointments, current year invoices, open treatment plans. Then open around ten random records and compare them with the old system.
Training and launch. On the first working day with the new software, keep the old account open in read-only mode, in case a quick comparison is needed.
Import order
Order matters because each piece of data depends on the previous one. First the price list and practitioners, then demographics, then clinical records and completed procedures, then treatment plans and estimates, and finally calendar, invoices, and documents. If you import invoices before patients, the system won't know whom to attach them to.

How to prepare and check files
Most import errors stem from formatting details that are invisible to the naked eye. Before uploading any CSV file, go through this checklist.
Character encoding. Save files in UTF-8. With other encodings, names like “Nicolò” or “D’Agostino” turn into strings of strange symbols. If you open the file and see garbled characters instead of accented letters, this is the issue.
Field delimiter. In Italy, Excel often saves CSVs with a semicolon because the comma is the decimal separator. Check which delimiter the destination system expects and ensure that no text field contains the delimiter without being wrapped in quotes.
Date format. Standardize all dates into a single format, for example 08/11/2026 or 2026-11-08. A file mixing two formats produces incorrect birthdates: 03/04 could become March 4 instead of April 3.
Amounts. Check that €1,250.00 is not read as 1.25. It is best to export amounts without thousands separators and with a consistent decimal separator.
Tax ID / Fiscal Code. This is the best unique identifier for the patient. Verify that it is 16 characters long, uppercase, without spaces. Patients without a tax ID should be flagged, not discarded.
Duplicates. The same patient recorded twice (“Rossi Maria” and “Maria Rossi”, or with two different phone numbers) is common in practices with years of history. Merge duplicates before migration: doing it afterward, with charts and invoices already linked, takes much longer.
Phone numbers and emails. Standardize numbers with the international country code (+39) if the new software sends reminders via SMS or WhatsApp. A mistyped number means a reminder not delivered and an empty dental chair.
Mandatory fields. Every system has fields without which a record is rejected: usually first name, last name, and an identifier. Filter the file for rows with these fields empty before importing.

The verification sheet
Prepare a small summary spreadsheet with baseline totals: number of patients, number of invoices per year, total revenue collected per year, number of future appointments. After the import, run the same counts in the new software. If the numbers match, you have the simplest proof that the migration is complete.
Privacy and security during migration
Migrating dental data is fully considered processing of health data. Recital 35 of the GDPR defines data concerning health broadly: it includes medical history, clinical treatments, and the physiological state of the patient. In practice, almost everything contained in a dental chart.
The Regulation requires the controller to assess the risks of processing and adopt measures to mitigate them, such as encryption (Recital 83). Translated into migration practice:
Never send patient files as regular email attachments. Use an encrypted channel agreed upon with the new vendor, or a password-protected archive with a strong password shared via a different communication channel.
No scattered copies. USB drives, reception desktop screens, download folders: every temporary copy must be deleted once migration is complete.
Restricted access. Only the practice’s point of contact and the vendor's technical team should work on the full files.
Written agreement with the new vendor. Before handing over data, the new software provider must be appointed as a data processor via a contract compliant with Article 28.
Updated record of processing activities. Record the change of vendor and the transition date.
Privacy notice to patients. The principle of transparency under Recital 39 requires processing terms to be accessible and understandable: if you mention the software vendor in your privacy notice, update it.
Deletion from the old system. Once verification is complete, request written confirmation from the outgoing vendor confirming the deletion or return of data, as required by Article 28.
For doubts about specific cases, such as the retention of records of patients no longer in treatment or handling data in an acquired practice, speak with your DPO or a privacy consultant familiar with the healthcare sector.
Frequent errors and how to solve them
Problem | Probable cause | Solution |
|---|---|---|
Unreadable accented letters | File not saved in UTF-8 | Re-export or re-save the CSV in UTF-8 |
All columns merged into a single one | Incorrect delimiter | Specify the correct delimiter to the system (; or ,) |
Inverted birthdates | Mixed date formats | Standardize all dates into a single format |
Amounts divided by one thousand | Thousands separator read as a decimal | Export amounts without thousands separators |
Rejected rows | Empty mandatory fields | Filter and complete rows before importing |
Duplicate patients | Duplicates in historical records | Merge duplicates before migration |
Invoices without an assigned patient | Imported before demographics | Follow the order: demographics first, invoices second |
Missing consents | Tables-only export | Request a separate export of PDF documents |
Appointments at the wrong time | Time zone or 12/24-hour format issue | Check against known appointments and correct the format |
Procedures without a price | Mismatched fee schedule codes | Import the fee schedule first and align the codes |
When an error affects many rows, do not fix it manually in the new software: fix the source file and repeat the test import. It is faster and leaves a clean audit trail.
Multi-location practices
If you manage a group or chain, migration is also an opportunity to standardize. Before importing, agree on a single fee schedule, unified procedure naming, and shared rules for clinical records. Migrating location by location using the same schema reduces time for the second and third locations because field mapping is already complete.
Our point of view
Every week we talk to practice owners who delay switching software out of fear of losing data. It is an understandable fear: that database contains years of clinical history and patient relationships.
Our experience shows that migration should not be the practice’s problem. That is why at Treatbase, data migration is simple, fast, and completely free of charge: we don't ask dentists or reception staff to become CSV experts.
There is also an aspect that matters more than the transfer itself. Moving data from one system to another only makes sense if the new tool gives you back time. Treatbase fills out clinical charts by voice, enables hands-free periodontal charting, and automates invoices and reminders. That is where chairside hours lost to bureaucracy are recovered.
The moment of migration is also the best time to tidy up: merge duplicates, unify the fee schedule, and standardize charts across locations. Those who approach it methodically start off with a practice cleaner than before.
Matteo
Switching to Treatbase
If you are considering leaving your current practice management software, Treatbase is a cloud-based dental practice management platform with voice AI: fill out clinical charts by voice, perform hands-free periodontal charting, manage scheduling, billing, payments, digital consents, and automated reminders to reduce no-shows. Data migration is included at no additional cost.

It works for solo practices and multi-site groups, offering staff and permissions management, performance analytics, and multilingual support for practices in Italy, Switzerland, and Spain. Discover Treatbase practice management software and ask how to bring your data over.
Frequently Asked Questions
How long does a migration from AlfaDocs take?
It depends on the amount of data and especially on documents and images, which take up much more storage than tables. The part that requires the most time from the practice is usually preparation: inventory, cleaning up duplicates, and spot checks. With a clear plan and a test export, the actual transition is condensed into a few days of work.
Will I lose my invoice history if I change software?
No, as long as you include it in the export. Issued invoices remain valid and must be retained: request the export of billing data and, for electronic invoices, the XML files. Importing them into the new software is also necessary to see deposits and balances for ongoing treatment plans.
Do I need to notify patients about the software change?
A new consent is not required to change the software vendor, but your privacy notice must remain accurate. If it names the software vendor or processing methods, update it. When in doubt, confirm with your DPO or privacy consultant.
Can I keep the old software accessible after the migration?
Yes, and it is recommended for a short period in read-only mode until spot checks are completed. From the day of the final export, however, no one should enter data into the old system. Afterward, request data deletion or return from the outgoing vendor, as required by the GDPR.
What happens to signed informed consents?
They must be transferred intact, in their original format, with the signature. Request a separate export of documents with an index linking them to each patient. In Treatbase, consents are archived digitally alongside the patient's record.
Sources
Regulation (EU) 2016/679, GDPR, official text in Italian (EUR-Lex) Regulation (EU) 2016/679, ELI page (EUR-Lex)