Migration Dolibarr
- Inventory the Dolibarr, PHP and database versions.
- Inventory standard, external and custom modules.
- Look for any core modifications.
- Check the SQL backup and documents.
- Check paths, permissions and configuration files.
- Check scheduled tasks, email, APIs and payment methods.
- Freeze data entry on the old instance.
- Copy, upgrade and apply the required corrections.
- Test users, documents, modules and essential workflows.
- Validate before returning to production.
Dolibarr migration process
During the migration
Once the migration backup has been created, the old instance must no longer be used. Data entered after that backup is not transferred automatically.
Limits to report before the work starts
- corrupted database;
- missing files or documents;
- outdated third-party module;
- core modification;
- incompatible PHP version;
- undocumented cron task;
- external API;
- PayPal or Stripe;
- email configuration;
- inconsistent data.
Frequently asked questions
Frequently asked questions about Dolibarr migration
Are documents included in the migration?
Yes, when the documents are present in the backup and accessible.
Can the old Dolibarr remain in use during migration?
No, not after the backup selected for the switch.
Are third-party modules always compatible?
No. Their compatibility with the target version must be checked.
Is PayPal or Stripe payment restored automatically?
No. Credentials, return URLs, test modes and production settings must be checked separately.
