This document outlines the recommended areas to review to successfully offboard a client that uses the Enterprise API endpoints to integrate with Passle.
Update and clean up code
Check templates and remove any Passle-related code, such as the hosting bundle. This ensures that the site can function independently after the offboarding.
Passle content export
You will receive the Passle content export, which you can upload to your CMS if you wish to do so.
Please remove all images and any content that is served from Passle servers, as you are no longer covered under the Passle licences.
Redirects
The client may need to set up redirects from their old Passle URLs to their new URLs. These redirects should match the structure of their new site to avoid broken links. This step should be managed by the client/agency.
API keys and integration access
Passle will revoke API keys and remove any webhooks on the agreed offboarding date. Remove any scheduled jobs, caches or sync processes that call the Passle API so they don’t fail or throw errors.
DNS and domains
If you use a custom domain or subdomain pointing at Passle (e.g. a CNAME), update or remove those DNS records before the cut-off date. If Passle sends emails from a custom address on your domain, also remove the related DNS records (SPF, DKIM, return-path) and update any reply-to addresses.
SEO considerations
Update canonical tags, sitemaps and robots.txt to point to the new URLs, and resubmit the sitemap to Google Search Console so old Passle URLs drop out of search results.
Feeds and syndication
Check for anything consuming Passle RSS feeds or syndication, such as newsletters, social scheduling tools or partner/aggregator sites, and repoint or remove it.
User access
Passle will deactivate user accounts and any SSO configuration. Remove Passle from your identity provider (e.g. delete the app registration).