Switching clinic software
Rytura helps you identify a structured client-list export from your current software, maps the supported fields and validates a dry run. Nothing reaches your live Rytura clinic until your authorised clinic contact approves the exact result.
A controlled handover
This is assisted migration work, not a public upload or one-click importer. Each gate makes the source, supported scope, exceptions and final approval visible.
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 proposed import is rehearsed away from the live clinic. Counts, sample records, duplicate decisions and exceptions are reconciled into a review your clinic can understand.
Your authorised clinic contact approves the exact mapping, exception plan and record counts. Rytura does the supported migration work only after that explicit sign-off.
The approved import is run with tenant isolation, an audit trail and rollback point. We reconcile the live result, then delete staged data according to the agreed retention window.
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 principlesNot 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.
No. A supported client-list migration is not a promise to move full clinical history. Notes, forms, consent evidence, photographs, prescriptions, treatment history, appointments and financial records need separate assessment and may remain unsupported.
No. The public Rytura website has no migration upload. Do not attach an export or send client, patient, health, payment or login information by ordinary email. If a migration is agreed, Rytura provides the approved encrypted transfer route separately.
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.
No. The clinic must confirm its authority, lawful basis, notices, source access and retention duties. Rytura applies the agreed migration controls, but software migration does not replace the clinic's legal, professional or records-management responsibilities.
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.