Moving off SCO

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

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.

The process

How 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.

  1. Inventory

    The application, database, scripts, scheduled jobs, printers, terminals, file transfers and users.

  2. Feasibility

    A short written report: what can move, what cannot, the options and what each would cost.

  3. Pilot

    The new system built from a copy of your data, so the awkward parts are found before they matter.

  4. Parallel run

    Your staff test the new system against the old one until the output matches.

  5. Switch over

    A final data transfer outside working hours, with the old system kept as a fallback.

Questions

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.

Next step

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

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.