When a small business website changes hands, a surprising amount of essential information can disappear into old emails or individual logins. A new designer may receive the site address but not know who manages the domain, where backups live, or which forms send customer inquiries. That creates risk even if the site looks normal.
A website handoff is an organized transfer of access, responsibilities, and documentation. Whether an employee leaves, an agency relationship ends, or a business hires a new webmaster, the handoff should make the website maintainable without sharing passwords in plain text.
Build an inventory before changing access
Begin with a concise record of systems rather than a pile of credentials. List the domain registrar, DNS provider, web host, WordPress administrator accounts, email service, analytics tools, form delivery tools, backup location, and any licensed themes or plugins. Record which organization owns each account and which person is responsible for renewals.
Account ownership is not always the same as day-to-day access. A contractor can be permitted to maintain a site without owning the domain or receiving billing administrator access. Make those boundaries explicit, especially for email and payment-related services.
- Website address, primary domain, and any known alternate domains
- Hosting provider and where DNS records are managed
- WordPress role assignments and approved administrator contacts
- Backup provider, frequency, retention, and restoration procedure
- Plugin and theme licenses, renewal owner, and supported update process
- Forms, mailbox destinations, spam filtering, and notification ownership

Document what runs the site
Make a short technical map: theme, page builder (if any), critical plugins, caching layer, and any custom code. Note the locations of custom styles or scripts instead of assuming the next maintainer will recognize them.
Include the website’s actual deployment process. If content is edited on a staging site before being promoted, explain which site is authoritative and how changes are reviewed.
Transfer access without leaving shared passwords behind
Create individual accounts with the least permissions needed for each role. If a new maintainer needs administrator access, provide it through an approved secure account-invitation or credential-management process, not an email containing the business owner’s main password. Enable multifactor authentication where it is available.
Once the replacement team confirms access, remove former users who no longer require it. Before deletion, check whether their WordPress posts need reassignment. Rotate shared secrets that cannot be delegated, such as old API keys or credentials previously known to departing personnel. Avoid rotating settings blindly: an unexpected change can disconnect forms, analytics, or integrations.
Prove the backup can actually be restored
Seeing a recent backup in the dashboard is reassuring but not equivalent to recovery. Confirm which files and database tables are covered, whether the backup is stored off-site, and whether someone can retrieve the archive. The receiving maintainer should know the approximate recovery process and what prerequisites it has.
When possible, perform a restore on an isolated staging environment. This catches missing files, incompatible database versions, and archives that cannot be opened. The article on testing a WordPress backup provides an additional checklist for that stage.

Record the business-critical functions
A handoff should say what “working” means to the organization. Include contact forms, quote requests, booking integrations, store checkout if relevant, phone links, maps, newsletter signups, and other conversions that support the business.
For each function, name its destination, owner, and a safe test method. A contact form that displays a success message without delivering an email may look fine during a visual review, so verify actual delivery with the appropriate mailbox owner.
Preserve the search and measurement setup
Do not remove analytics or search-verification connections merely because they belong to the previous vendor. First identify who owns the properties and grant the business durable access where possible. Document which tools measure search impressions, organic visits, and inquiry completions.
Record any important redirects and the current sitemap location. If the new team changes URLs, it should preserve the pages that have valuable incoming links or search visibility. A disciplined WordPress migration checklist is useful if the handoff also involves changing hosts or domains.
Complete a short acceptance review
- Confirm the site owner can access the registrar, hosting, and WordPress.
- Open the site on desktop and phone; check navigation and page formatting.
- Submit controlled tests through important forms and confirm delivery.
- Check that a backup exists and the restore instructions are usable.
- Reopen the SEO and analytics properties under the intended long-term owners.
- Confirm who approves updates, who responds to incidents, and how support requests are handled.
Capture the outcome in a dated handoff note. Open questions are better documented as unresolved than treated as complete. Never invent a successful restore test or claim email delivery was verified without checking it.
A handoff should reduce dependence on any one person
A good handoff protects the organization and helps the next maintainer do competent work. The most valuable deliverable is not a long password spreadsheet; it is a clear map of ownership, operational dependencies, verified recovery options, and practical next steps. If the site also needs design changes, a related St. Paul website design service page illustrates one route to discussing that work.
