Transferring a website maintenance plan means handing over the authority, records, schedules, and recovery information needed to operate the site safely. It is not the same as copying the public pages. The destination owner should be able to renew the domain, update content, run checks, restore service, and understand outstanding work without depending on the departing person.
Define the handoff scope
List domains, DNS providers, hosting, repositories, deployment systems, content management, forms, email delivery, analytics, consent tools, certificates, backups, monitoring, vendor accounts, and support contacts. Mark the authoritative record for each item. Separate website assets from unrelated client data and private projects. Assign a receiving owner before moving access.
Transfer domain authority deliberately
Confirm the registered name holder, registrar, recovery methods, renewal contact, billing owner, domain lock state, and transfer process. ICANN's transfer policy says eligible registered name holders must be able to transfer domains between registrars when policy requirements are met, and registrar transfer processes should be documented. Do not start a registrar transfer without the authorized owner and a verified recovery path.
Export content and media separately
Use the platform's documented export and inspect its limits. WordPress.com explains that its content export includes posts, pages, comments, categories, tags, and links to media, but not the theme design, customizations, plugins, or actual media files. Download authorized media separately and keep the source accessible during a staged import when links are used to retrieve files.
Capture the maintenance calendar
Record routine checks, deadlines, dependencies, and owners. Include domain and certificate renewals, software updates, backup checks, restore drills, accessibility reviews, content reviews, broken-link checks, form tests, analytics reviews, and vendor renewals. Distinguish an automatic check from a human review and state what evidence proves completion.
Inventory access without exposing secrets
Create an account matrix showing service, role, owner, recovery contact, least-required permission, and offboarding step. The receiving owner should create or accept their own account. Passwords, multi-factor codes, signing keys, and payment information remain owner-entered. Stop before saving a consequential account or billing change unless the authorized owner process permits it.
Document deployment and rollback
Write the approved path from source change to test, release, live verification, and rollback. Record repository and environment names without copying secrets. Identify which public hostname, Worker, application, or storage service belongs to this website so another property is not changed accidentally. Include the live checks required before a database or build artifact can be called deployed.
Rebuild integrations one at a time
List form destinations, transactional email, scheduling, maps, payments, reviews, analytics, and monitoring. Record the data owner and removal procedure for each integration. Use safe test data and avoid sending external messages or creating charges during a rehearsal. Confirm that contact routes still reach the approved destination after the handoff.
Transfer evidence and open work
Provide recent backup receipts, restore-test results, deployment receipts, incident notes, known limitations, change logs, and pending decisions. Label evidence with dates and environments. Do not convert a recommendation into completed work. Include failed tests and unresolved risks so the new owner does not repeat assumptions.
Rehearse on a staging destination
Import a representative content set and approved media, then test navigation, forms, redirects, metadata, accessibility, performance, and administrator access. Keep the current public site unchanged while resolving gaps. Verify that the receiving owner can run a maintenance check and locate rollback instructions without assistance.
Complete the handoff at an owner gate
Ask the receiving owner to accept the inventory, schedules, access, evidence, and outstanding work. Only then retire old accounts or services through the approved deletion and billing process. Preserve a recoverable record of what changed. The transfer is complete when the new owner can operate and recover the site, not when a folder has been sent.
Sources
- Transfer Policy — ICANN
- Export your website's content — WordPress.com Support