Check your exit terms first
Before anything else, read what your current contract says about data export and termination. Some cloud providers charge for a full export, some restrict its format, and some require notice before termination that you will want to give early.
If your provider offers a self-service export, take one now regardless of what you decide. Having your own copy of your data is sensible practice whether or not you move.
What we need
Cloud-to-cloud migrations are usually clean, because the data is already structured and the export is already designed to be machine-readable.
- Patient master export, usually CSV or Excel
- Billing history export for the period you want carried across
- Test master with rates and reference ranges
- Report PDFs, if your provider allows bulk download
- A few sample reports so we can match your format
Timing the switch
The one thing to get right is billing continuity. Switch at a clean boundary — the start of a month, or better, the start of a financial year if the timing happens to suit. This keeps your bill numbering sequential and makes the accounting straightforward.
Do not switch during a period you know will be busy. The week before a corporate health camp is a poor choice even though the migration itself is low-risk, because your staff will have no slack for questions.
What to ask us before you move
The same questions you should have asked your current provider, and which we would rather answer honestly than discover a mismatch in month three.
- Does Diagnosuya support the specific analysers you have integrated?
- Does it handle the departments you report on, including anything unusual?
- Can it reproduce report formats you have already customised?
- Does it support your current multi-branch or franchise structure?
- Are there features you rely on today that we do not have?