This update was included in v3.0+ of the Zero BS CRM Core, and with it comes improvements in page-load times, object read, update and view operations, and more generally a whole bucket more kick-ass.
This guide will walk you through the steps of the essential database migration that comes with v3.0 of ZBS.
- Before you get started, it is essential you backup your database
- You’ll need to be a WordPress Administrator to run this upgrade routine
- This process will mean that some of your object ID’s change. The system remembers old ID’s and can expose these if you need them. Please let us know via support if this is an issue for your business workflow
- You don’t need any special skills to run this upgrade, it’s all run via a web-based wizard.
Running the Upgrade
If you started using Zero BS CRM after version 3.0, you’ll never need to do this, but if you started with us earlier, you’ll see that when you go to use the CRM you’ll be presented with a message (you should also get a ZBS Notification telling you to run the upgrade):
If you’re an admin, you’ll see a button ‘go to update’ – clicking this will take you to the upgrade routine. (If you’re not a site admin, you’ll need to get one to do this for you.)
Note for Multisite users: Please read this before migrating
Here’s the first upgrade page:
This page gives you a rundown on the migration you’re about to run. Click ‘Get Started’ to move on to the next page:
Please read the page carefully before you hit the green button. It’s important that:
- You BACKUP your database before you run the routine – it’s been very well tested, but we’re not responsible for your loss of data if you do not back up before you run this!
- Your extensions may be disabled temporarily, and they may need to be updated after the migration (please see Extension Compatibility below)
- Please allow time. A 2k contact database may take 3-5 minutes, depending on your server hardware. A 10k-100k+ list might therefore take 25 minutes+
- Please be ready to leave the next page open until the ‘Complete’ page shows (below)
… it’s imperative you take these seriously, but once you understand them tick the boxes and click “Start Upgrade” (which will be greyed out until you confirm with the checkboxes).
Database Upgrade: Processing:
Once you get going, you’ll see a page like this – this page will automatically start workers which will process 20 objects at a time. This backs your data up as it goes, as well as migrating all ‘old database objects’ into new (and improved) v3 objects. The progress bar will go up as it works, and you can pause this with the ‘Pause’ button (but please try to run it in one sitting, especially if you’re using API/Sync extensions).
After this has completed, you will see a page like this:
Database Upgrade Complete
This means you’re all set! Your ZBS CRM has successfully upgraded your database. Win. Now your CRM will be faster, your edits will be cleaner, and lots more awesomeness is on the way.
Do you see “Non-critical Errors?” – Skip below to the Error Code section to learn more about these.
Note: If you’re using PRO extensions
It’s highly recommended that if you’re a Pro CRM user (or bundle owner) that you update ALL of your extensions now – only the latest versions will properly support v3.0 functionality.
V3.0 is a huge evolution for ZBS CRM, and as a result we can only run the latest extension versions along with it. (Much of the database structure has been solidified & refined, making for a very solid & fast foundation, which has meant a lot of the extensions needed to be refitted.)
What this means for you. If you want to keep using your extensions, you’ll need to update them before using them with v3.0!
The V3.0 Migration smartly deactivates any extensions it finds which are not compatible with v3.0. You’ll need to update these before you reactivate them!
v3.0 Compatible Extensions
- Advanced Segments – v1.3+
- API Connector – v1.6+
- Automations – v1.4.1+
- AWeber Connect – v1.2+
- Awesome Support Connector – v2.5+
- Bulk Tagger – v2.3+
- Client Password Manager – v1.4.1+
- Client Portal Pro – v1.7+
- Contact Form 7 – v2.5+
- ConvertKit Connector – v2.5+
- CSV Importer PRO – v2.0+
- Envato Order Importer – v2.4.2+
- Exit Bee Connect – v1.1+
- Funnels – v1.2+
- Google Contact Sync – v2.6+
- Gravity Forms – v2.6+
- Groove Sync – v2.6+
- Invoicing Pro – v2.6+
- Live Storm Connect – v1.1+
- Mail Campaigns – v2.0.3+
- MailChimp Connector – v2.6+
- Member Mouse – v1.5+
- Optin Monster – v1.1+
- PayPal Sync – v2.6.1+
- Registration Magic – v1.1+
- Sales Dashboard – v2.6+
- Stripe Sync – v2.6.2+
- System Email Pro – v1.1+
- Twilio Connect – v1.5+
- Woo Sync – v2.9+
- WordPress Utilities – v1.2+
- WorldPay Sync – v2.4+
Migrating on Multisite
Multi-site site owners can migrate their ZBS databases the same way as every other site owner, with the one key note:
Due to the nature of a v3.0 upgrade, some extensions will not work after 1 user migrates their core ZBS database. This means that if you have many users with sites using Zero BS CRM with extensions, that the migration routine will turn off any out-of-date network-activated extensions.
To ensure clean migrations for all users on a multisite, we recommend updating ALL EXTENSIONS on the multisite before updating the core plugin, so as users are not able to deactivate extensions network-wide by way of running the migration wizard.
Migration Error Codes
The v3.0 migration engine has been checked and cross-checked to provide as wide compatibility as possible, you may however still come across some conflicts/error codes. This section gives you more information on the specific error codes given upon Migration completion (with non-critical errors):
Note 1: You can also see a copy of the ‘Migration report’ which stores these errors at any point by going to ‘ZBS Settings -> System Status’ and then clicking ‘V3 Migration Logs’ at the bottom of the page.
Note 2: This migration report will also be emailed to you.
301 – This error code occurs when you have objects (Companies, Quotes, Invoices, or Transactions) which have duplicate references. Ultimately this reflects a non-unique field where the v3.0 database model requires a unique field. (e.g. 2 different Invoices have References which are identical.) In this instance, only the first Invoice will be added, and the error here will give a JSON encoded copy of the Invoice which was not added.
701 – This error occurs when you had two records which had to be unavoidably merged. In the v3.0 Migration, the only case where this can happen is if you have two different company objects with the same email address against them.
702 – This error code suggests that you have a discrepancy between your invoice total values from <v3.0 and the v3.0 invoice it has been translated into. This may happen for those of you who had invoices including Discounts or multiple Taxes. Ultimately if you see 702’s it implies that the invoice has been fully recalculated and produced a different total.
710 – This error code will be shown if you have out-of-date CRM extensions installed. V3.0 requires the absolute latest versions of the extensions.