Skip to content
Forms Migration

Pilot

Book a pilot

Send one form, check your database, pilot one screen, compare, and switch when the results match.

How a pilot runs

Five steps

  1. Step 1

    Send one form

    The team returns your own screen, running in a browser.

  2. Step 2

    Check your database

    For a move to PostgreSQL, we list every Oracle feature your database uses and check each one against Oracle itself, before you decide. We also name every piece of PL/SQL that will not carry over, and what calls it. A quote, not a surprise.

  3. Step 3

    Pilot one screen

    On a copy of your database, with your own users doing real work.

  4. Step 4

    Compare

    What Forms Migration saves and prints is checked against what Oracle Forms saves and prints.

  5. Step 5

    Switch

    When the results match, one screen or one database at a time.

Where a project needs your team

  • Embedded Java beans and some custom screen items have no web equivalent. They need a replacement designed, and the screen says so.
  • Logic kept in database packages outside the form is read from your database, so the pilot needs access to it.
  • Not every rule converts. Refused rules are listed with their reasons, and your team finishes them in the rule editor.
  • No big-bang switch: one screen or one database at a time.

Talk to us

Starting fresh? There is no pilot to book. Tell us about your application and we will talk it through.

Email, call or message us on WhatsApp. Tell us about your Oracle Forms, and we reply with how to send one form.

Email
[email protected]
Phone and WhatsApp
+974 7769 7795