Compare the move from your current system
Bring the questions that match the way you work: Pabau practice workflows, Phorest growth and retail tools, Fresha booking channels, Consentz clinical evidence or ANS patient limits and team growth.
Switching clinic software
Client contact import is live. Clinic owners can open Clinic setup → Import clients, upload a CSV with up to 500 records, map the supported fields and approve the exact preview. Existing client records are not overwritten or merged.
Preparing a move? Use the printable switching checklist to plan exports, bookings and records.
A controlled handover
The owner-only importer is inside the protected clinic app. Map fields, review validation and duplicate exclusions, approve the preview, then reconcile the result. Broader assisted migration is assessed separately; this public website does not accept client files.
We help your clinic find the structured client-list export available from its current software. The current supplier controls what can be exported, so we inspect the actual structure before promising a move.
No files are uploaded to this public site or sent by ordinary email. If the scope looks suitable, Rytura provides a separate encrypted transfer route and records who is authorised to use it.
We inventory the source columns, match supported Rytura fields and flag uncertain, duplicate or unsupported information. We do not invent meaning where the source is ambiguous.
The importer validates the staged rows before creating clients. Review proposed records, skipped rows, duplicate exclusions and unsupported fields in the preview.
The clinic owner approves the exact preview before running the import. Importing contact details does not create marketing consent or send client invitations.
The import is recorded for the clinic to reconcile. Existing clients are not overwritten. Untouched, unused imports can be undone within 24 hours; staged details are removed after import, cancellation or expiry.
Supported scope
The actual scope depends on the source export, data quality and agreed Rytura field map. A familiar column heading does not prove that two systems mean the same thing.
These fields can be assessed for migration when the source is structured and their meaning can be validated.
These are not included in a standard client-list promise and must never be assumed to transfer automatically.
No universal vendor promise. A CSV, spreadsheet or other structured export can still contain incompatible, missing or ambiguous data. Rytura confirms what is supported only after reviewing the actual export structure through the approved secure route.
Security and proof
The clinic sees what changed, what did not move and what needs a decision. Unsupported fields are exceptions, not silent guesses.
An approved private transfer route replaces public forms and ordinary email. Staged files are access-restricted and time-limited.
Every file, staged row, mapping and import job is bound to one clinic. Cross-clinic reads or imports fail closed.
Field transformations and duplicate decisions are versioned, deterministic and visible to the clinic before approval.
A rehearsal produces source totals, proposed records, skipped rows, duplicates, warnings and unsupported fields.
An authorised clinic contact checks counts and samples against the source, then explicitly approves or rejects the proposed import.
The approved run is logged and reversible to its agreed boundary. Staged data is deleted on the documented retention schedule.
Switching questions
If your question involves an actual client record, wait for the approved secure route. The first conversation should stay at clinic and system level.
See Rytura security principlesFuture bookings are assessed separately from a client-list import. Reconcile dates, time zones, practitioners, locations, statuses and linked payments. Agree a cutover point and how new or changed bookings are captured. Keep the original system accessible until the clinic has verified the destination or another agreed operating plan.
Not automatically. We first review the export your current supplier can provide and the meaning and quality of its fields. We confirm the supported scope before any migration work begins; some vendors, formats and fields may not be supported.
A supported client-list migration focuses on the agreed fields. Notes, forms, consent evidence, photographs, prescriptions, treatment history, appointments and financial records receive a separate assessment, and the confirmed scope is agreed before work begins.
Keep the export off the public website and ordinary email. If a migration is agreed, Rytura provides the approved encrypted transfer route separately for client, patient, health, payment or login information.
Only after a secure review and dry run. Your clinic receives field mapping, record counts and exceptions to validate, then gives explicit approval for the agreed production import. No approval means no production import.
They are reported as exceptions rather than silently guessed. The clinic reviews the proposed duplicate handling and unsupported fields. The production plan includes reconciliation, an audit trail and an agreed rollback point.
The clinic retains its legal, professional and records-management responsibilities, including authority, lawful basis, notices, source access and retention duties. Rytura applies the agreed migration controls around that clinic-owned responsibility.
Bring the questions that match the way you work: Pabau practice workflows, Phorest growth and retail tools, Fresha booking channels, Consentz clinical evidence or ANS patient limits and team growth.
The migration review should produce a written decision for each data type. Agree what will be imported, what needs separate assessment and what must remain accessible in the old system or an approved archive. A supplier name alone cannot establish what its export contains.
Agree a change window, a final reconciliation, clinic sign-off and the point at which the old workflow stops accepting new activity. Avoid running two reminder processes unintentionally. Do not delete the old information as part of a routine cutover without your clinic’s records-management decision.
Use the printable switching checklist. Compare source-system fit through our Pabau, Phorest, Fresha, Consentz and Aesthetic Nurse Software comparisons. These guides do not promise a universal importer.
Planned onboarding support · case-by-case review
Tell us which clinic system you use and the approximate size of the client list. We will discuss fit and the safe next step without asking you to send health data by email.