Setup and migration
Moving systems doesn’t have to be scary
We guide you through the move, bring across the information your practice relies on and set up a clean foundation for the future. Once it’s done, you can leave servers, manual upgrades and your old software behind.
Windows migration utility
Start your Sunix migration check
Download the Windows beta, enter your practice name and press Start. The utility checks bounded Sunix locations and sends limited diagnostic reports.
ooptify Migration for Windows
- Build
- 0.1.0-beta7 · ZIP with portable EXE
- ooptifyCollector_0.1.0-beta7-documents1.zip
- Windows compatibility
- Windows x64 beta. The minimum supported Windows version and compatibility on your computer have not yet been established. Confirm your system with our team.
- ZIP SHA-256 checksum
- f7e85260b96aa8a4b97778dd72fe28d97269689aaa899ec88108085dc2df023b
13.82 MB (13,817,712 bytes). Unsigned beta release. If Windows blocks the executable or reports an unknown publisher, stop and ask our team to verify the release; do not bypass the warning.
Contains ooptifyCollector.exe, START-HERE.txt and SHA256SUMS.json. Python is not required. This is the two-folder local collection revision of beta7. The verification below describes the checks performed on this exact package.
Extracted EXE: 14,102,839 bytes. SHA-256:30a142512e5f0762520c76c64135f7b7f6d6b882935e53139ac10af7f837c96dChecksums verify file integrity, not publisher identity. Do not run as administrator or change antivirus or firewall settings.
What has been checked?
On 28 October 2026, 81 focused source tests and 83 frozen-code tests passed. Three actual EXE collection checks verified 612 synthetic files, source preservation, missing-folder rejection and permission gates. Five further synthetic EXE tests covered 20 launches. Three native GUI callback tests and 43 discovery/warning tests passed. Package and runtime resource integrity checks passed.
The full legacy suite was not rerun for this narrow fix. Real mapped-network access and native junction traversal remain unverified; this beta retry was approved with that limitation. Live reporting and physical dialog clicks were not tested for this revision. Live renewal and replay have not been tested. These checks do not establish compatibility with every Windows version, discovery completeness, backup consistency or production data import.
Discovery has limits
The checklist keeps its 500-entry listing limit. Where Windows confirms case-insensitive directory semantics, up to 28 fixed DBF/FPT metadata checks can verify known names beyond that limit. Unknown semantics remain limited. Memo requirements and document references still need separate authorized inspection. Review the displayed scope before pressing Start. Discovery checks bounded Sunix locations with existing authorised access. It does not perform an unrestricted whole-computer or network-wide scan. A found file still needs review; the checklist does not certify that a backup is complete or consistent. The five bundled synthetic sample files remain available through --sample.
Download, open and Start
Use the utility on the Windows computer you want to check.
- 1
Download and extract
Download the ZIP and extract all three files into a local folder. Read START-HERE.txt, then double-click ooptifyCollector.exe. Python is not required.
- 2
Enter your practice name
Enter only your practice name. It is an unverified diagnostic label, not account access. On later launches, the saved name is prefilled. No account, invitation, administrator setup, PowerShell or manual JSON exchange is required.
- 3
Read the notice and press Start
If you know the Data folder, enter its exact path in Known Sunix Data folder; this checks only that folder. Otherwise leave it blank for bounded discovery. Read the diagnostic notice, then press Start. Nothing is transmitted before Start. If diagnostics cannot start, the reason stays visible beside the practice name. The completion dialog shows the run outcome separately from diagnostic sent, pending or unavailable status. Close it to continue. Run again repeats discovery; do not use it just to send reports.
Diagnostics only: patient files stay local
After Start, the installation sends only app status, bounded counts and predefined error codes. Patient data, filenames, paths, raw logs and file contents are excluded. Patient files are never uploaded by this utility. Reports are retained for 30 days. Seven-day diagnostic leases renew automatically with the same installation and key; revocation blocks renewal. This renewal behaviour has not been live-tested.
Offline work can continue. At most 20 reports are queued for seven days, with at most three network attempts per launch while the app is open. No service or autostart task is installed. If diagnostics are rejected, the app does not create a replacement identity.
Before reading or exporting records
Confirm a completed consistent offline backup and permission before reading database records or exporting anything. These are separate prerequisites after discovery. Review the checklist and unresolved items with our team. Discovery does not certify backup completeness or consistency, and local export does not import data into ooptify.
Local export now includes all files in the selected backup's Documents/WordDoc and Documents/Drawings trees, including unreferenced files. Nested relative paths, file hashes and possible source-record links are kept locally. Templates, EMail and other document folders are excluded. Missing or inaccessible required folders, links, cancellation or collection limits stop the export; no complete result is claimed. Patient attachment allocation and cloud transfer are not implemented.
Two live/backup candidates are not themselves an error. Select one consistent backup; do not combine them. Discovery limits remain, and an UNKNOWN diagnostic needs local issue-category evidence. This release does not claim to resolve an unidentified warning.
Keep patient files out of website contact forms and email. Agree any separate data transfer destination and handling arrangements with our team before sending files.
What moves across
Your history comes with you
We currently migrate practices from Sunix and Optomate. No two systems structure information in exactly the same way, so a perfect one-to-one copy is not possible — but we bring across as much useful data as we can.
The important data comes with you
We migrate your patients with as much clinical history as possible, appointments and appointment types, recalls and inventory.
Nothing useful gets stranded
Information that does not fit neatly into ooptify is preserved in a legacy tab on the patient record, so you can refer to it without returning to the old computer.
No new servers or computers
ooptify runs on anything with a modern browser, from a basic tablet to a Mac. It works best in Chrome and Safari.
Updates happen while you sleep
Improvements and new features are released overnight. We will brief you ahead of meaningful changes so your team knows what to expect.
Staff accounts and practice settings are configured fresh, giving your team a clean setup designed around how you work today.
How it works
Your migration in five stages
A clear path from exploring the training version to opening the practice on ooptify.
- 1
Explore ooptify and get your questions answered
Try the training environment, speak with us and make sure ooptify is right for your practice. We will answer your workflow, data and timing questions before you commit to a date.
- 2
We prepare your migration checklist
We will give you a clear list of what to supply, including reports and exports from your current system and the information we need about your practice.
- 3
Choose your first day on ooptify
You choose when you want to start. Three days before that date, we ask for the final files from your current system so we can begin the production migration.
- 4
We complete and check the migration
Our team works through the migration and validates the result. As soon as it is ready, you can begin using ooptify — often before your planned start date.
- 5
Open the practice and begin
On your first day, open ooptify in your browser and carry on with the practice. Your new system, staff setup and migrated information will be ready for you.
Not comfortable finding the files? With your permission, we can securely remote into your computer and retrieve the required exports for you.
Ready for a fresh start?
Try ooptify first, then talk with us about your data, timeline and migration plan.
