Import & export
Move core practice data between Smileline accounts, import CRM CSVs, or export clearly labelled entity CSVs.
By the end of this page you'll know which transfer to use: Core Practice Transfer for a quick Smileline-to-Smileline account migration, or entity CSVs for selective portability and migration from another CRM.
Everything on this page happens under Settings → Import & export. Owners and managers can use entity CSVs. Core Practice Transfer is owner-only.
CSV uploads can be up to 20 MiB, 500,000 data rows and 64 KiB per row. Split a larger export into separate files before uploading it.
Move a Smileline practice without a database snapshot
Core Practice Transfer packages the supported CRM relationship graph behind an authenticated API. It does not need direct database access and it does not copy a database snapshot.
The package includes:
- practice display settings, locations, boards and stages
- treatments, lead sources, lost and cancellation reasons, contact methods, tags and referrers
- appointment types, operatories and practitioners
- patients, channel-specific contact preferences and their evidence history
- each patient's chart number, codice fiscale, previous system number and NHS ethnicity code
- each patient's occupation, GP, emergency contact and clinician preference, with each professional contact's kind, so a GP arrives as a GP
- journeys, safe normalized attribution touches and stage history
- tasks, appointments and appointment participants
It deliberately excludes authentication and practice memberships, billing, subscriptions, agreements, conversations, messages, files, audit logs, automations, templates, campaigns, booking and provider operations, payments, credentials, webhooks, PMS state, NHS numbers, Reputation state, referrals, reports, chat, knowledge-base and dialer state. Staff references are matched to existing destination members by exact email; unmatched staff assignments become unassigned.
A codice fiscale, previous system number or ethnicity code that doesn't fit the destination — not a valid value, already held by another patient there, or an ethnicity code the NHS list doesn't know — is never dropped: the patient is still imported, and the value is added as a line in the patient's note saying why it wasn't recorded.
Core Practice Transfer is a structured migration, not a point-in-time backup or disaster-recovery archive. The source remains live while the export runs, so use a quiet migration window and stop making source changes before the final export.
Before you start
Create the destination as a new, otherwise unused Smileline practice. Complete onboarding with the same legal country and accounting currency as the source, but do not change the generated CRM configuration or connect integrations. The source and destination must be different practices.
The unused built-in email channel created during onboarding is allowed and stays in place during the transfer. A configured sender, connected mailbox, sending domain or existing inbox contact makes the destination ineligible.
Export and import
Create the source package
As a source owner, tick the best-effort export acknowledgement and click Create transfer package. You can keep using Smileline while the background job runs, although a quiet window gives the cleanest result. Smileline verifies row counts and relationship closure before marking the package ready.
Download it
Click Download under Recent jobs. The private package expires after seven days. Keep it secure: it contains patient and practice data even though capabilities and credentials are excluded.
Upload it to the destination
Switch to the destination practice, choose the .smileline-transfer.zip package, and click Upload transfer package. Packages can be up to 80 MiB. Smileline checks the manifest, policy version, file list, sizes, hashes, row shapes, duplicate identifiers and complete foreign-key graph before offering the import.
A package made by an older Smileline release fails with "Unsupported Core Practice Transfer format or policy version". Create a new package from the source and upload that one instead.
Smileline uploads the package in fixed chunks. Retrying the same chunk is safe, but an accepted chunk cannot be replaced with different bytes; cancel the transfer and start a new upload if the selected file changes.
The destination is locked as soon as validation starts. Other members can switch to another practice, but only an owner can finish or cancel the transfer.
Import and verify
When the job says Ready to import, review any unmatched-staff count and click Import. Smileline replaces the generated seed CRM rows, creates deterministic destination IDs, regenerates appointment identities, verifies every imported table count, checks each live appointment's practitioner (and operatory, where its location requires one) the same way the source practice does, and then unlocks the practice.
If an imported appointment is missing its practitioner or a required operatory, the import stops with a message saying so and the practice stays locked. Click Cancel to reset the destination, then create a new package in the source practice and import that.
Your recall types stay, but their Books online as appointment type is cleared because the generated appointment types are replaced (a cancelled import clears it too): choose it again under Recall types, or a recall link asks the patient to call.
Reconnect integrations and rebuild excluded automations after checking the migrated data. If a recoverable queue step fails and Retry is available, use it while the job's finite processing window remains. If Smileline says the import can no longer resume, click Cancel instead. Cancellation completely resets and reseeds a partially imported destination before unlocking it.
The destination reset also has a finite retry window. If the job tells you to contact support, the destination stays locked to preserve the failed import evidence. Do not recreate the practice or upload another package until support has reviewed it.
Switch from Dentally
UK and Irish practices moving from Dentally upload Dentally's full export (the .zip) under Switch from Dentally. It's owner-only. Smileline checks the whole export first, imports it without contacting anyone, then goes live when you say. Read Switching from Dentally for every step.
Import from DenGro or Boxly
Both platforms get a one-click path: their export columns are recognised automatically, so you skip straight to choosing a board.
Moving over from a CRM you ran alongside Smileline? Read Switching from another CRM first. Leads that already reached Smileline are updated, not duplicated, and the page explains when.
Export from the other platform
- DenGro — go to Contacts → Leads, filter to what you want to migrate, then click Download leads. Tick "I understand" and download the CSV.
- Boxly — open a box, click Export → Comma Separated Values (.csv). Boxly emails you the file; repeat per box you want to bring over.
Upload it
Click Import data, pick DenGro or Boxly, choose the file and continue. The columns arrive pre-mapped — review the list and adjust anything that reads "Don't import" that you'd like to keep.
Choose a board and map their stages
Pick which journey board the imported leads land on, then match the other platform's stage names ("Consultation Booked", "Follow Up"…) to your board's stages. A stage whose name matches one of yours is picked for you; anything else starts on your board's first stage. A stage you map to your going-ahead stage imports as going ahead. Treatments with a matching name are picked the same way, and treatments you don't have yet default to Create, so "Implants" arrives as a treatment automatically.
The same step has a follow-up option: one task in Leads for every imported lead that stays open. See Follow-ups for open leads.
Run the check, then import
The dry run reads every row without writing anything and tells you how many patients would be created or updated, how many need review, and which rows have problems (a broken phone number, a missing name). For leads, it also shows how many are already in Smileline and will be updated rather than duplicated, how many are left as they are, how many new journeys it adds, and how many New · Call now cards and enquiries close. Rows with errors are skipped — everything else imports when you click Import.
A DenGro row brings the whole picture across: the patient's details, their journey (stage, status, potential value, lost reason), marketing consent with its original date, tags, and the attribution trail — channel, source, UTMs and click ids all land on the lead's touch history. The "(attribution meta)" columns are the web address parameters DenGro captured with the lead: they're kept as they are, and fill any UTM or click id DenGro's own columns left empty. Consent is recorded separately for every populated, unblocked contact channel, so SMS, WhatsApp and email remain independently auditable.
Leads DenGro has GDPR-erased ("Forgotten at" has a value) are skipped automatically — erased people must stay erased.
Import from any other CRM
Choose Other CRM / CSV instead. You'll additionally pick what the file contains:
- Leads (patients + journeys) — one row per lead, the shape most CRMs export
- Patients — demographics and contact details only
- Journeys, Appointments, Tasks — child records matched to existing patients by email or phone
- Vocabularies — treatments, tags, lead sources and the other settings lists
The mapping step recognises common column names ("Surname", "DOB", "Postcode"…) and shows sample values next to each column so you can verify the guess. Every row needs at least a first name and an email address or mobile number.
For leads, map a Created date column: without one, the import can't recognise a lead Smileline already has by its date, and the mapping step warns you. A tags cell can separate tags with ;, , or |, or hold a list in square brackets such as ["VIP","Implants"].
An appointments file can map a Booked on column: when the booking was made in the other system. The appointment keeps that date as its booking date. The mapping step picks a column named "Booked at", "Booked on" or "Date booked" for it. It picks a created-date column ("Created at", "Date created") instead only when the file has no booked column, so a blank booked cell stays blank rather than taking the created date. Imported appointments are history, not bookings your team made in Smileline, so the dashboard's Bookings made never counts them (see Bookings on the dashboard).
Dates and phone numbers vary by platform, so the values step has two dials: the date format (detect, day-first, month-first or ISO) and the default country for phone numbers without a prefix.
Money values must use the practice's locked currency. A matching EUR, GBP
or USD code, or €, £ or $ symbol, is accepted; a different or
unsupported currency is reported as a row error rather than converted. Amounts
must be zero or positive; negative or implausibly large values are reported as
row errors rather than imported.
Codice fiscale and previous system numbers
A patients or leads file can bring two identity numbers:
- Codice fiscale — the patient's Italian codice fiscale, for an Italian practice. A column holding a UK National Insurance number is not picked for it.
- Previous system no. — the number your old system gave the patient. The mapping step picks it for a column named "Chart number", "Chart no", "Patient number", "Record number" or "Numero cartella". It is kept beside the chart number Smileline gives each patient, never in its place, and searching for it finds the patient.
A value that doesn't fit is never dropped. When a codice fiscale isn't 16 letters and digits once its spaces are removed, another patient already has it, or the practice isn't in Italy, or when a previous system number is longer than 64 characters, the patient is still imported and the value is added as a line in the patient's note saying why it wasn't recorded.
GPs and emergency contacts
A patients or leads file can also bring the clinical record's care contacts:
- Occupation — picked for a column named "Occupation", "Job" or "Profession".
- GP — the GP's name. The values step lists each GP name in the file under Their GPs: match it to a GP in the Address book, or leave New GP and the import adds it. A GP whose name matches one you have is picked for you. Map the GP's phone or address columns to Note (appended) if you want to keep them.
- Emergency contact name, Emergency contact relationship and Emergency contact phone — picked for columns such as "Emergency contact", "Next of kin" and "NOK phone". The phone is kept as typed when it can't be read as a number.
- Clinician preference — no preference, female, male or prefers not to say.
The emergency contact is one group: a relationship or a phone needs a name. A row with an emergency phone or relationship but no name still imports; the check says how many rows that is, and those details are written into the patient's note instead.
When a row updates a patient you already have, these fill gaps only, and the emergency contact fills only when the patient has none at all.
A file that can't be read
The file is stored the moment it arrives, before anything reads it. If it can't become an import — it isn't a readable CSV, or Smileline couldn't start the import — you see why at once, and the file is kept under Kept files on this page instead of being thrown away. An upload interrupted before Smileline could open its import or keep it appears there too, within about half an hour; if Smileline couldn't store the file at all, nothing is kept and you're asked to send it again. Retry reads it again and opens its import — one import per file: if the upload had in fact opened one, Retry opens that one, and that file can no longer be discarded. Discard asks why and deletes the file. Only a person can discard a kept file: Smileline never deletes one by itself. A kept file holds whatever the CSV holds, so discard one uploaded by mistake.
Import stock items
Bring a store room's inventory in from a spreadsheet, or recount it from one. Open Inventory and click Manage → Import from a spreadsheet, or click Import data here, choose Other CRM / CSV and pick Stock items. Owners and managers, signed in, can do this wherever the clinical workspace is open; an API key or connected app can't.
Each row is one item, or one lot of an item. The mapping step recognises columns such as:
- Site — the location's name. Leave it out if the practice has one location; with more than one, every row needs it. A name two of your locations share can't say which one, so give them different names first.
- Name and Quantity, which every row needs. A quantity is how many there are now, so a blank one is a row problem, never zero.
- Room — a room of that site with that name, or a new one.
- Unit, Minimum level, Category (a category's name in English, Spanish or Italian), Tags (new ones are added), Barcode, Serial number, Service due and Warranty ends.
- Unit cost, in the practice's currency, as other money columns are read.
- Lot number and Expiry date.
The rows that name the same item at a site are counted together, wherever they are in the file: by barcode when they have one, otherwise by name, ignoring capitals. So an item with three lots can be three rows anywhere in the file, and becomes one count.
Run the check
The check reads the whole file and shows, by item, how many are New items, how many are Recounts of items the site already has, how many need review, and which rows have problems. An item is recounted when:
- the site has a live item with its barcode, or
- it has no barcode match and exactly one live item at the site has its name.
Items matched by name alone are listed under Matched by name. Check them before you import: if one is really a different item, give it a barcode or another name in the file and upload it again. The items the import will leave for you to review are listed too, each with its reason.
Import
Click Import. Each item is written whole, with all its lots, so a run that stops part-way and is resumed never counts an item twice.
- A new item takes the first row's details and opens at the file's quantity and lots. Its stock is valued at the unit cost (a row without a cost uses the item's first unit cost), and its history starts with an opening balance.
- An item already here is recounted to the file: each lot the file names is counted, and what no lot holds is the rest of its rows. Its other details are not changed. Units the count adds are valued at the file's unit cost, if it gives one, otherwise at the item's average cost. Its history shows a count from the import.
An item is recounted only while its stock is what the check saw. If someone takes, restocks or counts it in between, it waits for you instead, so the import never undoes their change.
Neither raises a low-stock or out-of-stock alert. The movements are recorded as the person who started the import. Importing a new file later is a new recount.
Review what's left
An item waits for you instead of being guessed at when:
- more than one item at the site has its name, or an item with its name has a different barcode;
- the file names it more than once in different ways (by barcode in one row and by name alone in another);
- the file names some of its lots, and the item holds others the file doesn't mention;
- one of its rows has a problem;
- the site's items, or the item's stock, changed after the check;
- or it couldn't be written.
A row that names no item at one site — no name or barcode, a site the practice doesn't have, or a name two sites share — waits on its own.
The job shows Needs review, and isn't complete until each one is settled. For each item, click All rows and problems to read every row as the file gave it, with its problems. Then choose the item at its site to recount, or A new item, and click Import, or click Discard to leave it out. When the item you choose holds lots the file doesn't mention, also choose Lots not in the file: keep them (they stay, and the item's total includes them) or count them as zero. Rows with a problem are left out when you import it. A row that names no item can only be discarded: correct the file and import it again.
How duplicates are handled
When an imported row shares an email address or mobile number with an existing patient:
- Strong agreement (enough else lines up too, for example the same email and mobile plus the full name, or the same email, date of birth and full name) — the row merges into the existing patient automatically. A different date of birth never merges automatically.
- Anything weaker — the row is held for review rather than guessed at. The job shows Needs review; click it to see each held row next to the patient it resembles, with both dates of birth, and choose Merge into existing or Import as new. A group of similar matches can be resolved at once with Merge all or Import all as new, except a group whose dates of birth differ. See Review held matches in bulk.
When someone and their family member share that email or mobile, the row is compared with the person whose contact it is. A row that also carries the family member's own mobile or email is compared with the family member. Tasks, appointments and journeys in a file find their patient the same way.
A held row whose existing patient has since been erased stays in the review, detached from them: it reads Existing: Erased patient, Merge into existing is gone, and Import as new creates it as a new patient. The job's counts don't change.
Patient merges only fill blanks, including a re-run or later file matched by id: nothing you've typed is overwritten, and a note line the patient already has isn't added again. A codice fiscale or previous system number is added only when the patient has none yet. An opt-out in the file is still applied.
A journey is updated only while nobody on your team has worked it in Smileline. For a lead that arrived in Smileline before the import, the same person on the same board within 2 days of the row's created date counts as the same enquiry. Switching from another CRM explains both rules.
When one person can have several deals, map a Journey ID column from your first import. Without one, each person's id stands for a single journey, and a second row with the same id in one file is reported as an error.
Re-uploading the same patients or leads file is safe. A DenGro lead keeps its DenGro id. Other rows are recognised by the file's contents and their id or row number. Either way a second run adds no patients, journeys, cards or notes; consent evidence may be recorded again. A tasks file is not recognised again: importing it twice adds its tasks twice.
A row whose id points to a patient who was erased in Smileline is not imported: it is reported as a row problem, patient erased, so importing an old file again never brings an erased person back.
Ids carry across files only under a preset such as DenGro. A different plain CSV doesn't recognise an earlier file's ids, and Boxly exports have no id, so their rows match leads already imported by person and created date and leave them as they are. A later plain CSV with a Journey ID column can't recognise deals an earlier CSV imported and adds them again, so leave those rows out of it.
Export
The Export section downloads any entity as a CSV that opens straight in
Excel or Sheets — patients, journeys, appointments, tasks and every settings
vocabulary. Money cells include the locked EUR, GBP or USD code so they
cannot be re-imported as another currency. A download holds up to 10,000 rows;
anything bigger, patients included, automatically becomes a background job with
no row limit and appears under Recent jobs when ready. A big export from
the patients list lands here too,
with that list's search, filters, sort and columns. One file can hold up to
512 MiB of CSV and one row up to 1 MiB: an export past either stops straight
away with a message saying why — for a row, which record — so you can shorten
that record or contact support.
The appointments file has a Booked At column after Created At. Booked At is when the appointment was booked: when it was created in Smileline or, for one synced from your practice management system or imported from a file, the booking time that system or file gave. It is blank when that time is unknown. Created At is when the row reached Smileline. Importing the file maps Booked At to Booked on, so every appointment keeps its booking date and one with a blank cell stays blank.
A background entity export fixes an upper creation-time boundary when it
starts, then walks rows by (created at, id) rather than mutable page offsets;
a patients export walks the patients list's own order the same way. Rows
created after that boundary belong to the next export, and a redelivered
completed job does not rebuild its file. This is a bounded high-water export,
not a database snapshot: a row that already existed may contain an edit made
before the worker reached it, and a patient whose sorted value (say, its last
name) is edited while the export runs can be skipped or appear twice. The
default Created order never moves.
Entity CSVs are data-portability files, not a lossless backup or a whole-practice disaster-recovery archive. Use Core Practice Transfer for the supported Smileline-to-Smileline CRM graph, and keep your own approved retention and backup process.
While an import runs
Imports run in the background in batches — you can leave the page. The job row under Recent jobs shows live progress, and the counts (created, updated, errors, to review) update as it goes. Cancel stops the job at the next batch; rows already written stay.
If an import fails part-way — an outage, a fault in one batch — the job shows Failed with two buttons. Resume continues from where it stopped, in the same phase (the check or the import itself), without re-running the rows already handled; Cancel closes the job and keeps what was written. Until you resume or cancel it, a failed import keeps the leads it wrote: uploading the same file again reports those rows as held by the open import and imports the rest.
A CSV import, and resolving its held rows, sends no outbound webhooks to your endpoints, and never sends messages, notifications or ad conversions.
While an import works through a lead, an action on that lead on the Leads page may briefly ask you to try again, and a journey you have open may say it was changed by someone else. Check the latest version and save again, or refresh the page. Run big imports when the front desk is quiet.
Every import and export is recorded in Settings → Activity log.
Uploaded CSV files are removed after a terminal job's download/review window. Row-error and possible-match snapshots are redacted 30 days after the job is finished. Unresolved snapshots have a hard 90-day limit, so an abandoned review cannot retain raw patient details indefinitely.
Billing and subscription access
Your plan, what you've used so far and your prices — pay-as-you-go, the SEO & Social plan and the older price list — and exactly what happens after a failed payment or cancellation.
Practice archive
Take the complete record of the practice out as machine-readable files with an index of every part and original document, a manifest and a validation report.