Forms, CRMs and Email: The Integration Inventory Most Teams Skip

A website rarely works alone. It hands enquiries to a CRM, sends notifications to staff, adds subscribers to a mailing list and reports events to analytics. These connections are often configured once and forgotten. During a migration, a single forgotten integration can mean days of lost leads before anyone notices.

Why integrations get missed

Integrations are frequently configured outside the website: a webhook in a form plugin, an API key in a settings screen, a tag added through a tag manager or a rule in the CRM that matches a field name. None of these show up in a page-by-page content review.

Build the inventory from both ends

Start on the website. For every form, record where submissions go, any hidden fields such as a source page or campaign value, and the confirmation behavior. Then go to each receiving system and look for connections pointing back to the website:

• CRM: web-to-lead forms, API integrations, field mappings, assignment rules.
• Email marketing: sign-up forms, tags applied on submission, automations triggered.
• Email delivery: which service sends website emails, sender addresses and DNS records that authorise sending.
• Booking and scheduling tools: embedded widgets and redirect URLs after booking.
• Payments: gateways, webhook endpoints and return URLs.
• Chat and support widgets: script snippets and account owners.
• Analytics and advertising: tags, conversion events and consent requirements.

Document field mappings

Many integrations depend on exact field names. A CRM rule might look for a field called company, while the new form sends organisation. Record each mapping explicitly and confirm it during testing with real test submissions.

Respect consent and privacy

Analytics and marketing tags should follow the consent choices your site offers. When rebuilding, make sure tags still wait for consent where required, that privacy notices describe current services and that you are not collecting more personal data than the business needs. Retire integrations nobody uses rather than migrating them by default.

Treat credentials carefully

API keys and secrets should be stored in environment configuration, not in code or in shared documents. A migration is a natural moment to rotate credentials, restrict their permissions and confirm who owns each third-party account.

Test with real flows

For each integration, define a test that proves it works end to end:

1. Submit the form on the staging site.
2. Confirm the record appears in the CRM with the correct fields.
3. Confirm the notification email arrives and is not filtered as spam.
4. Confirm any automation fires as expected.
5. Confirm analytics records the event only when consent allows it.

Use clearly labelled test data and clean it up afterwards.

Plan the switch-over

Some services need configuration changes at launch, such as new webhook URLs or allowed domains. List those changes in the launch plan with the person responsible for each. After launch, repeat the tests on the live site.

The result

An integration inventory turns invisible plumbing into a checklist. It protects the moments that matter most to the business, the enquiries, bookings and orders, and makes the migration safer for everyone who depends on them.