Table of Contents

  1. Introduction

  2. Why You Should Keep Dolibarr Up to Date

  3. Understanding Dolibarr’s Release Cycle

  4. Checking Your Current Dolibarr Version

  5. Pre-Update Considerations

  6. Backing Up Your Installation

  7. Evaluating Customizations and Compatibility

  8. Preparing a Staging Environment

  9. Choosing the Right Update Method

  10. Method 1: Manual Update via File Replacement

  11. Method 2: Using Git for Updates

  12. Method 3: Using Softaculous or Installer Tools

  13. Running the Dolibarr Update Wizard

  14. Common Errors During Update and How to Fix Them

  15. Verifying Database Schema and Integrity

  16. Post-Update Configuration Steps

  17. Updating Custom Modules and Themes

  18. Testing After the Update

  19. Keeping Track of Future Updates

  20. Conclusion

1. Introduction

Dolibarr is an open-source ERP/CRM solution used by businesses around the world. As with any software platform, staying on the latest version is critical for accessing new features, improved performance, bug fixes, and security enhancements. This guide walks you through every step of updating your Dolibarr installation to the latest stable version, whether you're running a small business instance or a large-scale deployment.

2. Why You Should Keep Dolibarr Up to Date

  • Security: Patches close vulnerabilities that may expose data.

  • Features: New versions include expanded capabilities.

  • Compatibility: Updated integrations and libraries ensure ongoing support.

  • Bug Fixes: Critical fixes are bundled in every new release.

  • Community Support: Most forums and developers refer to the latest version.

Running outdated versions risks data loss, feature limitations, and integration failures.

3. Understanding Dolibarr’s Release Cycle

Dolibarr follows a predictable versioning pattern:

  • Major versions (e.g., 17.0.0) bring structural changes.

  • Minor updates (e.g., 17.0.3) include bug fixes and patches.

New stable versions are released roughly every 6 to 12 months. Stay informed via www.dolibarr.org or GitHub.

4. Checking Your Current Dolibarr Version

Log in as an admin and go to Home > About Dolibarr. You’ll find the installed version and build details. Alternatively, check the top of the htdocs/filefunc.inc.php file for the $dolibarr_version variable.

5. Pre-Update Considerations

Before proceeding:

  • Review release notes to understand changes

  • List custom modules and overrides you’ve implemented

  • Confirm server requirements match the new version (PHP, MySQL, etc.)

  • Notify users about potential downtime

Treat updates with the same seriousness as system migrations.

6. Backing Up Your Installation

Always backup:

  • Database using mysqldump or your control panel

  • Files and directories, especially:

    • /htdocs/

    • /documents/

    • /conf/

Example command:

mysqldump -u root -p dolibarr_db > dolibarr_backup.sql
zip -r dolibarr_files.zip /var/www/html/dolibarr/

Store backups securely and verify they can be restored.

7. Evaluating Customizations and Compatibility

  • Review any modified files under /core/ or module folders

  • Test if custom modules are compatible with the new version

  • Consider using the /custom/ directory to avoid conflicts

  • Check community forums for known issues with third-party themes or modules

8. Preparing a Staging Environment

Best practice is to:

  • Clone your live site to a staging server

  • Perform the update there first

  • Validate all workflows and integrations

This minimizes risk and allows full testing before affecting production.

9. Choosing the Right Update Method

You can update Dolibarr via:

  • Manual file replacement (recommended for most users)

  • Git repository (for developers and contributors)

  • Softaculous/Installatron (if installed via cPanel)

The method depends on how you originally installed Dolibarr.

10. Method 1: Manual Update via File Replacement

  1. Download the latest stable version from www.dolibarr.org

  2. Extract the archive to a temporary folder

  3. Delete these folders in your old instance:

    • /htdocs

    • (except /documents and /conf)

  4. Copy the new /htdocs files over the old location

  5. Retain /documents/ and /conf/

  6. Browse to http://yourdomain/install/

Follow the wizard to complete the update.

11. Method 2: Using Git for Updates

If you cloned Dolibarr from GitHub:

cd /var/www/dolibarr
git pull origin develop

Then run:

php htdocs/install/upgrade.php

Ensure you switch to a tagged release or stable branch before deployment.

12. Method 3: Using Softaculous or Installer Tools

If Dolibarr was installed via Softaculous:

  1. Log into cPanel > Softaculous

  2. Locate Dolibarr and click Upgrade

  3. Follow the prompts

Note: Softaculous may delay support for the latest versions. Manual backups are still essential.

13. Running the Dolibarr Update Wizard

After file replacement:

  • Navigate to /install/

  • The update wizard will detect your previous version

  • Run the upgrade script step-by-step

  • Remove or rename the /install/ directory when finished

Monitor for any schema changes or alerts.

14. Common Errors During Update and How to Fix Them

Blank page after update:

  • Check file permissions

  • Clear cache/browser cookies

Access denied errors:

  • Verify conf.php and database credentials

Update wizard not launching:

  • Ensure /install/ folder is present

  • Check .htaccess rewrite rules

15. Verifying Database Schema and Integrity

Post-update, verify:

  • All modules are still active

  • Data tables exist and load properly

  • No duplicate or missing rows

Use phpMyAdmin or database admin tools to check table status.

16. Post-Update Configuration Steps

  • Check Setup > Modules to re-enable disabled modules

  • Test PDF generation, email sending, and external integrations

  • Confirm cron jobs are running (for recurring invoices, tasks)

  • Clear browser and Dolibarr caches

17. Updating Custom Modules and Themes

  • Copy updated templates to /custom/modules/

  • Review changes in core structure that might break themes

  • Test visual elements and layout on all devices

Some third-party modules may require new versions to be compatible.

18. Testing After the Update

Thoroughly test:

  • User logins and permissions

  • Invoice creation and payment recording

  • Product and stock management

  • Custom reports or dashboards

  • API endpoints and webhooks

Validate every core function and business-critical process.

19. Keeping Track of Future Updates

  • Subscribe to Dolibarr newsletters or RSS feeds

  • Follow GitHub releases and changelogs

  • Schedule quarterly review and update cycles

  • Assign update responsibility to an admin or IT team

Stay proactive to ensure performance and security.

20. Conclusion

Updating Dolibarr to its latest version is essential for maintaining a secure, stable, and feature-rich ERP/CRM environment. By following this comprehensive guide—backing up, testing, and verifying every step—you can execute a smooth upgrade that enhances system performance without disrupting your business.