WordPress plugin integration offboarding

Agnieszka Chorzepa
Agnieszka Chorzepa
  • Updated

This document outlines the steps required to successfully offboard a client who uses the Passle WordPress plugin as a way to integrate with Passle. 


1. Update and Clean Up Code

The first step is for the client/agency to remove all references to the Passle custom post type across their codebase. Check templates and remove any Passle-related code, such as the hosting bundle. This ensures that the site can function independently of the Passle plugin after it is removed.

2. Upload Passle Content to WordPress

Before uninstalling the plugin, the client should import their Passle content into WordPress. Passle can provide a data export earlier to facilitate this migration. Please verify that all content and media have been successfully transferred. This step helps to make sure that nothing gets lost while we make the transition.

Please remove all images and any content that is served from Passle servers, as you are no longer covered under the Passle licences.

3. Uninstall the Passle Plugin

Once the content migration is complete, the client/agency can safely uninstall the Passle WordPress plugin. After uninstalling, they should notify the Passle team, who will then proceed to:

  • Delete the client’s API key
  • Delete the webhook

Recommended areas to review

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.

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 at 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).


 

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request