1. Home
  2. Upgrading to Jetpack CRM v5.0

Upgrading to Jetpack CRM v5.0

Jetpack CRM v5.0 brings with it a whole host of new improvements and moves some paid features into the free core CRM.

In this new major version we’ve started removing some of the oldest backward compatibility code which supported users who may still be on versions below v3 of Jetpack CRM (then called Zero BS CRM).

Before you upgrade to v5.0, please check the following (and as always, back your data up first).

This article provides upgrade steps for those users who had Jetpack CRM before v5.0 but hadn’t yet fully upgraded their database. If you started fresh on v5.0, or you’ve already migrated your database, you shouldn’t need to do anything.

If you’re on a recent version of Jetpack CRM you should be good to go. The only pre-requisite that you’ll need to make sure you’ve completed is to check that your data is already migrated to our v3 Database.

If you can edit contacts, and see no notices for ‘migration required’, the chances are you’ve already been migrated. If you want to double-check this, you can view the System Status tab in CRM Settings -> System Assistant (/wp-admin/admin.php?page=zerobscrm-systemstatus&tab=status). If you see Database Version 3.0 next to “Database Version”, you’re set!

If instead the database version is less than 3, you’ll need to upgrade the databae before upgrading. Please see this guide on upgrading your database.

For users who are still on ‘Zero BS CRM’:

If you’re one of the few people still using the older versions of Jetpack CRM (previously named Zero BS CRM or ZBS CRM), you’ll first need to upgrade to Jetpack CRM v4, then run the database migration before you can upgrade to version 5.

You can download specific versions of Jetpack CRM from the bottom of our WordPress.org plugin listing page. We recommend you download the highest version 4, (likely v4.11):

Delete the old plugin and install/activate Jetpack CRM v4. You can then migrate your data to the latest database version. You can read more about the v3.0 database migration here.

Updated on May 24, 2022

Was this article helpful?

Still not found an answer?
If you've searched the knowledge base and still can't find a solution, please submit a ticket.
CONTACT SUPPORT