Moving from OPERA 5 to OPERA Cloud: a hotelier's checklist

Every OPERA 5 property has heard some version of “you have to migrate” from a vendor with something to sell. The truth is less dramatic and more useful: Oracle publishes exact support dates, the migration changes specific things about daily operations, and the hotels that struggle are usually the ones that treated it as an IT project rather than an operational one. This checklist covers what is actually documented, what changes, and how to keep guest communication running through the switch.

Where OPERA 5 support stands

The dates worth knowing come from Oracle’s own Applications Lifetime Support Policy, not from vendor slides. As of the July 2026 edition, the last supported on-premise release, OPERA 5.6, has Premier Support until December 2027, extended by Oracle from an earlier April 2027 date, with error correction in that final stretch applying only to release 5.6.28 and later. No Extended Support tier is available for any OPERA 5 release. Earlier releases left Premier Support years ago: 5.5 in October 2021, a transition Oracle partner Mastel Hospitality documented for its customers at the time.

Two nuances matter. First, there is no published shut-off date: after Premier Support ends, OPERA 5 enters Sustaining Support indefinitely, which means the software keeps running but new fixes, updates and certifications stop. Second, Oracle has extended the 5.6 date before, so check the current policy document for your version rather than relying on any article, this one included. The operational question is not “when does OPERA 5 die” but “how long do we want to run the front office on a system that no longer receives fixes”.

What migration changes day to day

OPERA Cloud is not OPERA 5 in a browser; it is a different system with the same vocabulary. Teams report that familiar workflows change shape, screens are organised differently, and some tasks take more clicks than muscle memory expects, which makes retraining a real workstream rather than a formality. Reports are their own chapter: standard OPERA Cloud reports differ from V5 output, and custom reporting is rebuilt in Oracle’s separate Reporting and Analytics product rather than carried across.

The interface landscape changes too. Point-to-point OPERA 5 interfaces, OXI most prominently, are replaced by OHIP, Oracle’s API platform for OPERA Cloud. Every connected system, from the booking engine to guest messaging, moves to the new model, and Oracle’s own migration documentation notes that code mappings no longer translate automatically, so codes must match across systems. That is rework per vendor, and it belongs on the plan from day one.

Keeping guest communication running

Guest communication is one of the few systems that can stay continuous through the whole migration, because chatlyn supports both sides of it. On OPERA 5, the Oracle OPERA on-premise integration runs guest journeys from scheduled reports over a secured SFTP connection. On OPERA Cloud, the Oracle OPERA Cloud integration subscribes to realtime events through OHIP. A property switches from one to the other during cutover, and the guest-facing journeys, confirmations, pre-arrival messages, AI answers on WhatsApp and webchat, carry on unchanged.

For mixed estates the same dual support means a group can migrate property by property while every hotel keeps messaging guests. If OHIP is new territory, the plain-language guide what is OHIP? covers what the platform does and what connecting a vendor involves.

Timeline and pitfalls hotels actually report

Recurring lessons from practitioners, consultants and published reviews of real migrations:

Dirty data migrates as dirty data. Years of inconsistent OPERA 5 use, duplicate guest profiles above all, arrive intact in OPERA Cloud unless cleaned first, and then undermine reporting and front-desk work in the new system.
Groups migrate in years, not months. Consultants working with large estates describe phased rollouts across brands and regions; single properties move faster, but 6 to 12 weeks of preparation per property is a realistic floor.
Interface re-certification is the hidden workstream. Each OXI-era connection needs an OHIP replacement, with code mappings aligned per vendor, and the slowest third party sets the pace.
Reports need rebuilding. Teams that lived in custom V5 reports should prototype their key reports in OPERA Cloud before cutover, not after.
Training is bigger than expected. Reviewers report changed workflows and higher click counts for routine tasks; the properties that fare best schedule real training time and keep a superuser per shift.
Cutover pauses operations. Check-in, payments and housekeeping updates can pause during the switch, so plan the window for low occupancy and rehearse the manual fallback.

None of these argue against migrating. They argue for treating the migration as an operational programme with an owner, a data-cleanup phase and a vendor-by-vendor interface plan.

The checklist

Confirm your OPERA 5 version and its support dates against Oracle’s current lifetime support policy.
Inventory every interface on the property, with its vendor, data direction and OHIP replacement status.
Clean the data before it moves: guest profiles, rate codes, routing rules.
Prototype your five most-used reports in OPERA Cloud’s reporting environment.
Plan per-vendor interface migration, and confirm with each vendor, chatlyn included, how continuity works during cutover.
Schedule the cutover window for low occupancy, with a rehearsed manual fallback.
Book real training time and name a superuser per shift.
After go-live, verify the OHIP event flow end to end: a test booking should trigger the confirmation message within moments.

Frequently asked questions

Is OPERA 5 end of life? Oracle publishes no shut-off date. The last supported release, 5.6, has Premier Support until December 2027 per Oracle’s current lifetime support policy, with no Extended Support tier; after that it runs on indefinite Sustaining Support, without new fixes or certifications. Check the policy for your exact version.

How long does an OPERA 5 to OPERA Cloud migration take? Weeks per property, years per large group. Realistic preparation runs 6 to 12 weeks for a single property, with data cleanup and interface re-certification the usual long poles.

Do we lose our integrations when we migrate? Every OPERA 5 interface is replaced by an OHIP-based connection, so each vendor needs a migration plan. chatlyn supports both sides: SFTP-based journeys on OPERA 5 today and realtime OHIP events on OPERA Cloud after, so guest communication continues through the switch.

Can guest messaging keep running during the cutover? Yes. The journeys run on the on-premise integration until cutover and on OHIP after; the AI keeps answering guests on WhatsApp and webchat throughout, and only the data source behind the journeys changes.