Website redesign / Integrations
How to Manage Integrations During a Website Redesign
Forms, CRM, analytics, search, payments, booking, identity, and content feeds can be invisible until they fail. Treat integrations as business processes with owners, data, and recovery paths.
Inventory every connection and its business owner
List visible and background integrations: forms, CRM, email, analytics, consent, search, booking, payments, maps, recruitment, customer portals, product feeds, chat, automation, and reporting. For each one, record its purpose, owner, vendor, credentials owner, data sent and received, triggers, failure alerts, cost, and contractual limits.
Trace complete workflows rather than isolated tools. A contact form may create a CRM record, notify a team, start an email, and feed attribution reporting. Missing any step can make the new site appear functional while the commercial process is broken.
Decide what to retain, replace, simplify, or remove
Do not migrate an integration only because it exists. Check whether it is used, reliable, supported, compliant with current requirements, and compatible with the future platform. Compare the cost and risk of retaining it with the change required in the wider business process.
Agree the source of truth for customers, leads, content, products, and consent. Define field mappings, identifiers, ownership, retention, and deletion behavior with the relevant technical and legal advisers. If the redesign also changes platform, the redesign versus replatforming guide helps separate experience work from infrastructure change.
Design failure states and test real scenarios
Specify authentication, permissions, rate limits, timeouts, retries, validation, duplicate handling, error messages, logging, and fallbacks. A friendly success message should appear only after the business has actually received the data or the system can recover it reliably.
Test with representative records and every material branch: valid and invalid input, consent choices, duplicate contacts, unavailable services, delayed responses, expired credentials, vendor limits, and partial failure. Verify downstream records and notifications, not only the browser screen. The redesign launch testing guide helps place these checks in the wider QA plan.
Plan cutover, monitoring, and recovery
Set dates for configuration freezes, credential changes, data migration, DNS or platform cutover, webhook updates, and production verification. Name the person who can approve rollback or a temporary manual process. Preserve the old configuration long enough to diagnose issues without leaving insecure access in place indefinitely.
After launch, monitor form delivery, sync failures, analytics events, payment or booking completion, response times, and vendor alerts. Compare expected volumes with actual records. Document the final data flows, owners, renewal dates, and recovery steps in the handover so the integration does not become undocumented infrastructure.
Protect the processes behind the pages
Does your redesign depend on business-critical integrations?
Northform can map those dependencies into the scope, interface states, test plan, and launch sequence from the start.
Discuss your website redesign Explore website redesign services →