If you are running a version older than v5.0, you need to update your Jetpack CRM plugin.
Jetpack CRM v5.0 introduces many new improvements and moves some previously paid features into the free core CRM.
This major update also removes some of the oldest backward compatibility code, which supported users running versions earlier than v3 (previously called Zero BS CRM).
Before you upgrade
Before upgrading to v5.0, we strongly recommend backing up your data. You can use Jetpack VaultPress Backup for this purpose.
Do you need to upgrade your database?
The following instructions are intended for users who had Jetpack CRM installed before v5.0 but have not yet completed the database upgrade:
- If you are starting fresh with v5.0 or have already migrated your database, no action is needed.
- If you are on a recent Jetpack CRM version, verify that your data has been migrated to the v3 database.
To confirm this, check if you can edit contacts without seeing any “migration required” notices. For extra assurance, navigate to the System Status tab located at Jetpack CRM → System Assistant (URL path: https://yoursiteurl/wp-admin/admin.php?page=zerobscrm-systemstatus&tab=status).
If you see Database Version 3.0 next to “Database Version,” your database is up to date.
If your database version is less than 3, you will need to upgrade the database before proceeding with the CRM upgrade. For detailed instructions, please refer to our database upgrade guide.
For sites that are still on ‘Zero BS CRM’:
If you are still using an older version of Jetpack CRM, previously named “Zero BS CRM” (ZBS CRM), you should do the following:
- Upgrade to Jetpack CRM v4 first.
- Run the database migration.
- Finally, upgrade to Jetpack CRM v5.
You can download specific versions of Jetpack CRM from the bottom of our WordPress.org plugin listing page. We recommend downloading the latest version 4 release (likely v4.11).
Delete the old plugin, install and activate Jetpack CRM v4. Then, migrate your data to the latest database version. Detailed information on the v3.0 database migration is available here.