Off-boarding

Source code ownership transfer

• Our default is to work on the client's codebase, unless otherwise agreed upon.
• In some cases, clients might want the static snapshot of the codebase or website, typically shared on their file-sharing platform (like Dropbox, Google Drive, etc).

Access Removal

• Web Hosting platforms (like WP Engine, AWS, SiteGround, etc)
• Content Management Systems (like WordPress, Sanity, Contentful, etc)
• Analytics & Tag Management (like Google Analytics, Google Tag Manager, etc)
• DNS & CDN Management (like Cloudflare, etc)
• CRM System (if any, like Hubspot, Salesforce, etc)
• Any client-owned email address (if any)
• Plugin/Software License Ownership Transfer on Client’s Owned Email and Access Removal
• Any other third-Party Platform Access Removal
• Documentation (Files/Folders) Access Removal (like Confluence, Notion, etc)
• Project Management Tools Access Removal (like Jira, Trello, etc)
• Rotate all the keys and passwords for "live" services before off-boarding.

Communication

• Keep the client about the off-boarding process and the timeline.
• Communicate the completion of the off-boarding process.
• If there are any issues with self-removal, notify the client in advance.
• If there are any pending items when the engagement is wrapped up, explicitly state in writing that the client needs to take care of them.