No products
* Prices may vary depending on your country.
* An additional contribution can be added at the time of payment.
New products
mp2d20260713104543
New
Command-line tools for migrating data from a PrestaShop store—categories, customers, products, downloadable files, and orders—to Dolibarr using the Webservice API and staging tables.
|
|
![]() |
📌 Module version: 1.0.0 📅 Last updated on: 07/13/2026 👤 Publisher/License: Philippe GRAND / Atoo-Net / GNU GPL v3+ 🌍 Interface languages: 📧 Support: email at contact@atoo-net.com ✅ Dolibarr compatibility: Dolibarr 24.0 or higher ✅ PrestaShop compatibility: PrestaShop 1.6 to 9.x ✅ PHP requirement: PHP 8.1 or higher 💡 Free updates for 1 year for the same version, then 50% discount on the next version. |
![]() |
The psimport module provides a complete set of migration tools for transferring data from an existing PrestaShop store to Dolibarr ERP/CRM.
It can retrieve and import your categories, customers, addresses, products, product images, downloadable files and orders.
The migration uses the standard PrestaShop REST Webservice API. No direct access to the PrestaShop MySQL database is normally required.
Instead of immediately creating records in Dolibarr, psimport first stores the retrieved information in intermediate staging tables. This allows you to inspect the data, identify errors and correct problems before performing the final import.
The staging mechanism also makes it possible to restart only failed imports without downloading all the data from PrestaShop again.
| ✅ Product categories | ✅ Customers and third parties |
| ✅ Customer addresses | ✅ Countries and address information |
| ✅ Products and services | ✅ Product prices and VAT rates |
| ✅ Product cover images | ✅ Complete product image galleries |
| ✅ Downloadable product files | ✅ Virtual product attachments |
| ✅ Customer orders | ✅ Order lines and totals |
Each migration operation is divided into two separate steps:
Fetch: data is retrieved from PrestaShop through the Webservice API and stored in psimport staging tables.
Import: checked and validated staging records are converted into Dolibarr objects.
This separation provides better control than a direct migration because you can verify the retrieved data before it modifies your Dolibarr database.
psimport uses dedicated tables whose names begin with:
llx_psimport_*
These tables store the information retrieved from PrestaShop before the final Dolibarr import.
For each resource, the module displays:
| In staging | Total number of records retrieved from PrestaShop |
| Pending | Records waiting to be imported |
| Imported | Records successfully created or matched in Dolibarr |
| Errors | Records that could not be imported and require attention |
| Last fetch | Date and time of the most recent retrieval operation |
The Import management tab provides a centralized overview of all migration operations.
From this interface, you can:
Retrieve data from PrestaShop using the Fetch action
Import staging data into Dolibarr using the Import action
View the number of pending, successfully imported and failed records
Reset failed records so that only these records are processed again
Empty a staging table before performing a new migration test
Check the date of the most recent data retrieval
Each staging record has an import status:
| 0 — Pending | The record is waiting to be imported |
| 1 — Imported | The record was successfully imported into Dolibarr |
| 2 — Error | The import failed and the error details were recorded |
After correcting the cause of an error, use the Reset errors action to return failed rows to the pending status.
You can then run the corresponding import again. Successfully imported records are not processed a second time.
This avoids restarting the entire migration because of a small number of invalid or incomplete records.
psimport imports PrestaShop products into Dolibarr with their main commercial and tax information.
The product migration includes:
Product reference
Product name and description
Prices excluding and including tax
VAT rate resolution through PrestaShop tax rule groups
Association with imported categories
Product cover image
Complete product image gallery
Downloadable files attached to virtual products
The target Dolibarr object type can be selected in the module configuration.
For software modules, licenses, documents and other digital items, importing PrestaShop products as Dolibarr services is recommended.
PrestaShop does not always expose the final VAT percentage directly on the product resource.
psimport resolves the applicable rate by reading the PrestaShop tax configuration through the following Webservice resources:
tax_rule_groups
tax_rules
taxes
This allows product prices and VAT rates to be transferred more accurately to Dolibarr.
VAT results should nevertheless be checked in the staging data and on a sample of Dolibarr product cards before importing the complete catalogue.
psimport can retrieve both the product cover image and the complete image gallery associated with each PrestaShop product.
The gallery is retrieved through the PrestaShop product image endpoint and stored in a dedicated staging table before being imported into Dolibarr.
The module:
Retrieves all images associated with each product
Preserves the image order returned by PrestaShop whenever possible
Detects and ignores exact duplicates between the cover image and the gallery
Reports images that could not be downloaded or imported
Because the exact API response may vary between PrestaShop versions, it is recommended to perform an initial test on a small number of products before importing the complete catalogue.
The standard PrestaShop Webservice API does not expose the downloadable files attached to virtual products.
To handle this limitation, psimport includes the optional Psimport Bridge module for PrestaShop.
Once installed on the source store, the bridge allows psimport to retrieve files already referenced in the PrestaShop product download table.
The bridge:
Uses the same PrestaShop Webservice API key as psimport
Operates in read-only mode
Does not modify the PrestaShop database
Does not modify files stored on the PrestaShop server
Only provides access to files already registered as downloadable product files
Can be removed after the migration has been completed
An alternative manual migration is also possible by exporting the PrestaShop product download table and copying the source store's download directory.
psimport retrieves customers and their addresses from PrestaShop before creating the corresponding third parties in Dolibarr.
The migration can include:
Customer identity
Company name, when available
Email address
Phone numbers
Postal address
Postal code and city
Country information
Associated delivery and billing addresses
Customers and addresses are handled together to preserve the relationship between each customer and their address information.
psimport can retrieve and import PrestaShop customer orders and their order lines.
The order migration includes:
PrestaShop order reference
Associated customer
Order date
Products and services ordered
Quantities and unit prices
VAT rates
Order totals
Payment method mapping
Filtering according to selected PrestaShop order statuses
Before importing orders, the accepted PrestaShop order status identifiers and payment method mappings must be reviewed according to the configuration of the source store.
Products and customers should be imported before orders so that order lines can be linked to the correct Dolibarr objects.
To preserve relationships between the imported objects, the recommended execution order is:
Categories
Customers and addresses
Products or services
Downloadable product files
Complete product image galleries
Orders and order lines
Each step should be checked before continuing to the next one.
Compare the number of records in PrestaShop, the staging tables and Dolibarr
Inspect pending and failed staging records
Check the imported category hierarchy
Verify customer names, email addresses and postal addresses
Check product references, descriptions and category associations
Verify prices excluding tax, prices including tax and VAT rates
Open a sample of product images and downloadable files
Check customer and product associations on imported orders
Compare order lines and totals between PrestaShop and Dolibarr
The PrestaShop Webservice must be enabled from:
Advanced Parameters → Webservice → Enable PrestaShop's Webservice
A Webservice API key must then be created with read permissions on the required resources:
categories, customers, addresses, countries, products, images, tax_rule_groups, tax_rules, taxes, orders, order_details
Only GET permissions are required because psimport reads data from PrestaShop and does not write data back to the source store.
The following standard Dolibarr modules should be enabled before running the migration:
| ✅ Third Parties | ✅ Products |
| ✅ Services | ✅ Categories |
| ✅ Customer Orders | ✅ Customer Invoices |
Activating psimport automatically creates the required staging tables. No manual SQL import is required during the standard installation.
The connection is configured from the psimport module setup page in Dolibarr.
| PrestaShop store API URL | Base URL of the PrestaShop Webservice, for example https://www.example.com/api |
| PrestaShop Webservice API key | Read-only API key created in the PrestaShop back office |
| PrestaShop cookie_key | Optional value used only by features that may require it |
| Dolibarr target object type | Defines whether imported catalogue entries are created as products or services |
A connection test is available to verify the API URL and Webservice key before starting the migration.
psimport is designed to read information from PrestaShop without modifying the source store.
The PrestaShop Webservice key only requires GET permissions
The migration writes data only to the Dolibarr database and document directories
The optional Psimport Bridge operates in read-only mode
The bridge only exposes downloadable files already registered by PrestaShop
No order, customer or product is modified in PrestaShop
A complete backup of both applications and their documents is nevertheless strongly recommended before any migration operation.
If the API connection works in a browser but psimport receives an HTTP 403 Forbidden response with an empty body, the request may be blocked by a firewall or bot-protection service before it reaches PrestaShop.
This can notably occur when the source store is protected by Cloudflare Bot Fight Mode, ModSecurity or another Web Application Firewall.
For Cloudflare, check:
Security → Analytics → Events
If the request is shown as a managed challenge generated by Bot Fight Mode, temporarily disable the protection while running the migration, or create an appropriate exclusion rule when the Cloudflare plan supports it.
The security protection can be enabled again after the migration.
Before running a complete migration, it is strongly recommended to test each resource with a small record limit.
This allows you to:
Validate the API connection
Check the structure of the retrieved data
Confirm VAT rate resolution
Verify product and customer matching
Check image and file download permissions
Confirm order status and payment method mappings
Identify compatibility differences between PrestaShop versions
Once the sample has been validated, the same process can be run without a limit to migrate the complete dataset.
Replace a PrestaShop store with a Dolibarr marketplace: retrieve the existing catalogue, customers and order history before switching platforms.
Centralize commercial data: bring PrestaShop customers, products and orders into the company's Dolibarr ERP/CRM.
Migrate a software module store: transfer virtual products, module archives, documentation files and product images into Dolibarr.
Prepare a controlled migration: check and correct the staging data before records are created in Dolibarr.
Resume an interrupted migration: restart only failed records without downloading or importing successful records again.
Preserve historical orders: retrieve previous customer orders and their lines for consultation and commercial tracking in Dolibarr.
Is direct access to the PrestaShop MySQL database required?
No. The standard migration uses the PrestaShop REST Webservice API. A manual database export is only an optional alternative for retrieving downloadable files when the Psimport Bridge cannot be installed.
Which PrestaShop versions are supported?
psimport supports PrestaShop 1.6 to 9.x through the standard PrestaShop Webservice API.
Which Dolibarr version is required?
The module requires Dolibarr 24.0 or higher.
Which PHP version is required?
PHP 8.1 or higher is required.
Does psimport modify data in PrestaShop?
No. The PrestaShop API is used with GET permissions only. Data is read from PrestaShop and created in Dolibarr.
Does the Psimport Bridge modify PrestaShop?
No. The bridge operates in read-only mode and only provides access to files already registered as downloadable products.
Can failed records be imported again?
Yes. Correct the data or configuration, reset the failed records and run only the affected import again.
Are successfully imported records duplicated when an import is restarted?
No. The staging status identifies records that have already been successfully imported.
Can I inspect the information before it is imported?
Yes. All retrieved data is first stored in staging tables so it can be checked before the final import.
Why does the API test return HTTP 403?
The request may be blocked by Cloudflare Bot Fight Mode, ModSecurity or another firewall located in front of the PrestaShop store.
Should I test the migration before importing everything?
Yes. Always test each resource on a limited sample and verify the result before launching the complete migration.
Migrate a PrestaShop store without developing custom SQL conversion scripts
Use the standard PrestaShop Webservice API instead of requiring direct database access
Inspect and correct data before creating objects in Dolibarr
Import categories, customers, addresses, products, images, files and orders
Retrieve downloadable files associated with virtual products
Resolve VAT rates using the PrestaShop tax configuration
Track pending, successful and failed imports from a centralized interface
Restart only failed records instead of repeating the complete migration
Keep the source PrestaShop store unchanged during migration
Prepare a controlled transition from PrestaShop to a Dolibarr-based store
A data migration should always be tested on a separate Dolibarr instance before being performed on a production environment.
Before starting, create a complete backup of:
The PrestaShop database
The PrestaShop files and download directory
The Dolibarr database
The Dolibarr documents directory
After each migration stage, compare the source and target record counts and manually check a representative sample of the imported data.
The complete module documentation is available on the official Dolibarr wiki:
👉 Dolibarr Wiki – psimport Module (EN)
French documentation:
👉 Dolibarr Wiki – Module psimport (FR)