Gravity Forms
+ Legacy Markup & 3.x Migration Assistant

Gravity Forms forms built before version 2.5 often still run on legacy markup: the old list-based HTML, the old stylesheet and the CSS Ready Classes such as gf_left_half. Legacy markup is planned to be removed in a future Gravity Forms version, and Gravity Forms 3.0 already changed things many themes and snippets rely on: the submit button is a <button>, the date picker no longer uses jQuery UI and some spinner filters are gone. Switching a form is one toggle, but finding out what that toggle breaks is the hard part. The Gravity Forms Legacy Markup & 3.x Migration Assistant add-on does that work for you.

The readiness scan lists every form that still uses legacy markup and reads your theme, child theme, must-use code snippets, Additional CSS and form classes for legacy selectors, Ready Class styles and the hooks and scripts that Gravity Forms 3.0 removed or changed. Each finding comes with the file and line, a severity and a suggested modern equivalent. The scan is strictly read-only: it never edits a theme file, a snippet or your Additional CSS.

The converter turns the old column Ready Classes into the modern column layout and the list classes into the choice layout settings, and lists the classes that need a look. A side-by-side preview renders each form with legacy and with modern markup, a dry run lists every change without saving anything, and the bulk switch saves a timestamped backup of each form first, then switches it. One-click rollback per form or per batch writes the backup back exactly as it was. Admin-only, no outside connection. For Gravity Forms 2.9 and newer.

The scan only lists and reads files: the active theme and its parent, the must-use plugins folder where code snippets often live, the Customizer Additional CSS and the CSS classes of every form. Its rules were built from the Gravity Forms source and change log. The bulk switch takes a site-wide lock with a single atomic database update, so a double click or two administrators at once give one backup and one change. Before a form is switched, its complete form settings row is saved in the add-on's own table with the date and a SHA-256 checksum; the switch then turns legacy markup off and applies the class conversion. Rollback writes the saved row back unchanged and checks the checksum. Unlike tools that copy forms between sites, fix configuration errors, migrate forms from other form plugins or replace text, it focuses on moving existing forms from legacy to modern markup. Everything runs on your own server — no outside HTTP request beyond the licence and update checks.