Migrating from SCO OpenServer to Linux
Some systems should move to Linux and some should not. We work out which yours is, and then carry out the move with the data, scripts, printing and users intact.
Ask about moving off SCO
What "moving off SCO" can mean
The right route depends on the application, not the operating system. The first job is always to find out what the application is built with and whether a Linux version exists.
Virtualise and keep it
The system moves to current hardware unchanged. Nothing is rewritten. For an application with no Linux version, this is usually the right answer.
About virtualisation When a Linux version existsMove the application to Linux
Many business applications, databases and language runtimes that ran on SCO also run on Linux. The data, scripts, print routes and users are carried across.
Ask if yours can move When the application is being replacedMove the data
The history held in the old system is extracted into a form the new one can load, and the SCO system is kept readable for as long as you need it.
Ask about data migrationHow a migration is planned
Most of the risk in a migration is in what nobody wrote down: the cron job that sends a file every night, the printer that needs a particular escape sequence. We find those first.
-
Inventory
The application, database, scripts, scheduled jobs, printers, terminals, file transfers and users.
-
Feasibility
A short written report: what can move, what cannot, the options and what each would cost.
-
Pilot
The new system built from a copy of your data, so the awkward parts are found before they matter.
-
Parallel run
Your staff test the new system against the old one until the output matches.
-
Switch over
A final data transfer outside working hours, with the old system kept as a fallback.
Migration questions
Can our SCO application run on Linux?
It depends on what it is built with. An application supplied only as SCO binaries, with no Linux version and no source code, generally cannot. One built on a database or language that also exists for Linux often can. We look at the application and tell you which case you are in before you spend anything on a migration.
Should we migrate, or virtualise and stay on SCO?
If the application does its job and has no Linux version, virtualising it removes the hardware risk at a fraction of the cost of replacing it. Migrating makes sense when there is a supported Linux version, when the application is being replaced anyway, or when you need something SCO cannot provide.
How do you move the data without stopping the business?
The new system is built and loaded from a copy while the old one keeps working. The final transfer of changes is done outside working hours, after your staff have tested the new system with real data.
What happens to the old SCO system afterwards?
We usually keep it as a virtual machine that can be started when someone needs to look something up. It costs almost nothing to keep and avoids arguments about what the old figures were.
Find out whether your system can move
Tell us what the application is, who supplied it and which SCO release it runs on.
- You deal with the people who do the work
- No obligation, and no upgrade required before we will help
- We tell you plainly if something is not worth doing