Forms, webhooks and CRM links after moving to WordPress
An IT consultant explains how to rebuild contact forms, webhooks and CRM integrations in WordPress after converting an AI website.
Convert2WP – convert your AI website to WordPressClick here
Forms are backend, not design
A contact form in an AI-built site often looks finished but sends its data to a function inside the builder's own platform. When the site is converted, the form looks exactly the same in WordPress, but there is nothing behind it any more. That is expected: the converter moves the design and pages, not the backend.
So every form needs to be rebuilt deliberately. I see it as an opportunity, because WordPress form tools are mature and far more flexible than most builder forms.
Making an inventory of every form
I start with a list: every form on the site, which fields it has, where submissions used to go, who reads them and which follow-up actions happen. Newsletter signup, contact, quote request, event registration and job application often all behave differently.
Clients are regularly surprised by this list. Forms get added over time and nobody keeps track. Writing it down prevents the classic launch-day problem where one forgotten form silently goes nowhere.
Choosing a form engine
For most sites a well-maintained form plugin is the right choice. It offers conditional fields, file uploads, spam protection, stored entries and integrations. I look for one that stores submissions in the database, because email alone is not reliable enough as the only record.
I rebuild the form in the plugin and then replace the converted static HTML form with the plugin form, keeping the visual style. Usually that means adjusting a few CSS classes so the new form matches the design exactly.
Delivery you can rely on
WordPress sends email through PHP by default, which many mail providers treat as suspicious. Notifications end up in spam or never arrive. I always configure sending through an authenticated SMTP service or a transactional email API, with SPF, DKIM and DMARC records set correctly on the domain.
After that I test delivery to several mailbox providers. It takes ten minutes and prevents weeks of lost leads that nobody notices because no one knows the messages are missing.
Webhooks to connect other systems
Many businesses want form data to go straight into a CRM, a spreadsheet or an automation platform. Webhooks are the cleanest way. On submission, the form plugin sends a JSON payload to a URL, and the receiving system processes it.
I keep payloads explicit and documented: field names, formats and which fields are required. I also add a shared secret or signature so the receiving end can verify the request really came from the website. Unsigned webhooks are an open door for junk data.
CRM integrations and data mapping
Native integrations with popular CRMs save time, but the mapping between form fields and CRM fields still needs care. Phone numbers, countries and consent checkboxes in particular are often formatted differently. A wrong mapping can create duplicate contacts or lose consent information you legally need.
I test with realistic data in a sandbox account of the CRM when possible. Every field is checked once end to end, so the sales team receives exactly what they expect.
Spam and abuse protection
A form without protection is filled with spam within days. I combine a honeypot field, a time-based check and an invisible challenge from a privacy-friendly captcha service. Heavy visual captchas hurt conversion and are rarely necessary.
Rate limiting at the server or firewall level adds another layer for forms that trigger expensive actions, such as sending documents or creating accounts.
Privacy and retention
Form data is personal data. I set a retention period for stored entries, limit who can view them in the admin area and make sure the privacy notice explains what happens with submissions. Entries older than the retention period are deleted automatically.
Rebuilding forms is real work, but it gives you a setup you understand completely. Small issues in the first weeks, like a missing field in the CRM, are normal and quick to fix once the structure is in place.