SOPs — Offboarding
Offboarding SOP
Always download a backup before deleting anything. No exceptions. Store backups in the client's Google Drive offboarding folder.
1
Cloudways
Option 1 — Archive for future use (recommended if uncertain)
1
Create a full backup using Cloudways' backup feature
2
Download the backup to Google Drive (client offboarding folder)
3
Delete the application from the server to free up resources
4
If no other apps on the same server, delete the server too to stop billing
Option 2 — Full removal
1
Download backup first
2
Applications tab → select application → Delete Application
3
Servers tab → select server → Delete Server
4
Deactivate any add-ons (email, monitoring) to stop further charges
Simply stopping a server does not halt billing. Charges continue for allocated resources until the server is deleted.
Option 3 — Disable access without deletion
1
Applications tab → select application → Application Settings → toggle Disable (stops web access, SFTP/SSH, cron jobs)
2
Update DNS records — point domain to a placeholder or remove DNS records
Use this if the client might need the site again. Keeps data intact but makes it inaccessible.
2
WhatConverts
Option 1 — Transfer ownership to client
1
Log into WhatConverts Master Account → Master Account Settings → Users → Account Users → + Add Account User
2
Enter client's email, assign appropriate permissions, click Finish
3
Coordinate with WhatConverts support to transfer full account ownership to the client
Option 2 — Delete the profile
1
Export all lead data and reports to Google Drive before deletion
2
Log into the client's WhatConverts profile → Profile Icon → Additional Settings → Delete Profile
3
Confirm deletion — this removes all leads, phone numbers, and forms. Phone numbers are released.
3
Google Ads
Two options depending on whether the client is continuing to run Google Ads themselves:
- Client keeps running ads: Change all LP final URLs to the client's main website (not the MM-hosted landing pages). Remove MM's manager access from the account.
- Client pausing ads entirely: Pause all campaigns. Remove MM's manager access. Confirm billing is set up under the client's own account, not MM's.
Before removing manager access, confirm the client has their own login and can access the account independently. Don't leave them locked out.
4
If the client wants the landing pages
Static HTML pages (new pipeline): Pages built via the MM LP pipeline are pure HTML files hosted on Cloudways — no WordPress, no Elementor, no plugin licenses. Transfer is simpler than the legacy WordPress process.
Option A — Cloudways-to-Cloudways transfer (recommended for static HTML pages)
1
Client creates their own account at Cloudways.com ↗
2
Client sends MM the email address of their new account
3
MM initiates an Application Transfer from the Cloudways dashboard
4
Client accepts the transfer email — entire site and billing moves to their account instantly, zero downtime
Option B — Manual file export (any hosting)
1
Download the
index.html and assets/ folder from the GitHub repo2
Provide to the client as a ZIP file
3
Client's hosting provider handles upload and DNS configuration
For static HTML pages, there are no software licenses to worry about — no Elementor, no WordPress, no plugin fees. The client receives plain files they can host anywhere.
Legacy WordPress pages (old pipeline)
For pages built on the old WordPress + Elementor workflow, the original transfer options still apply. The client needs to purchase their own Elementor Pro license after transfer. See the archived ClickUp SOP for the Cloudways-to-Cloudways WordPress transfer process.