wiki/clients/current/cordwainer/2026-04-05-forms-migration-priority.md · 408 words · 2026-04-05

Cordwainer Forms Migration — WP Forms to Gravity Forms

Overview

During a February 2026 internal sync, Mark flagged the Cordwainer site as a "cluster" inherited from a previous developer — a mix of mismatched plugins, duplicate tag manager accounts, and non-standard tooling. The highest-priority remediation item is replacing all WP Forms instances with Gravity Forms, which is the agency's standard form plugin.

This task was assigned to Eshok and is to be completed promptly.

Background

The Cordwainer site was not built from scratch by the agency — it was adopted from a prior developer's setup. This left a patchwork of plugins and configurations that have caused ongoing instability. Mark has been working through a broader cleanup, including:

Despite this progress, WP Forms remains on the site and represents the most significant outstanding risk to form reliability and site stability.

Decision

Replace all WP Forms instances with Gravity Forms and remove WP Forms from the site entirely.

Rationale:
- Gravity Forms is the agency's standard; it is more stable and better supported within the team's workflow
- WP Forms was introduced by the previous developer and is inconsistent with the agency's stack
- Standardizing on Gravity Forms reduces future maintenance overhead and support risk

"We're using WP Forms. Well, the first thing I think we need to do like now is we need to get Jeff or whatever developers available and we need to convert all these forms to Gravity Forms and get these WP Forms out of here." — Mark Hope

Scope

The number of forms is estimated at three to four.

Action Items

Sources

  1. Index
  2. 2026 02 13 Impromptu Zoom New Dawn Cordwainer Aviary
  3. 2026 04 05 Elementor Rebuild