Migration intelligence for hospitals
Assess your clinical apps for the cloud, one approved step at a time.
Cutover reads the code of one application and reports what it finds. It does not change anything.
Only people invited to a workspace can sign in. Each workspace is private to its own organization.
Access
You are not invited yet
This Google account is not invited to any Cutover workspace. Ask your workspace admin to invite this email address, then sign in again.
Step 2
Who are you today?
Cutover shows each role the views and decisions it owns. Your role in a workspace is set by its admin.
Your workspace
Cutover
Analyses
Only sample or public code. No patient data.
People in this workspace
Invited people can sign in with Google, using that exact email address. They see only this workspace.
Pending invitations
Members
New customer workspace
Creates a separate workspace for one customer and invites its first admin. You cannot see a customer's data unless you are invited into that workspace.
Step 3
Name the application
Use a name your team will recognise. It appears on the analysis list.
Optional detail can go in the comments later.
Step 4
Connect the code
Paste the GitHub location of the code. Cutover checks that it can read it before going on.
Step 5
Confirm the data rules
Step 6
Analyzing
The stages run in this order. Cutover does not report each stage separately yet, so the ticks show the overall state, not each stage.
Step 7
Action items
Comments
Step 8
What next?
Choose one. You can come back to the findings at any time.
Download the report
The report contains only what your role may see.
Invite a reviewer
Workspace admins add people from the workspace page.
Continue to planning
Coming in a later phase.
Delete these results
Removes the analysis, its comments and its action items. This cannot be undone.
Cutover reads code only. Source code is not stored, and results are deleted after the retention period.