E-commerce

PrestaShop Data Extractor

Vern's PrestaShop extractor imports a new merchant's store data — customers, orders, contacts, and products — into your product as structured, ready-to-use tables. It's built for teams onboarding sellers off PrestaShop, so a new store's full history is in your app the moment they sign up.

Start migration

Browse all extractors

PrestaShop

SaaS API (REST)

Managed auth, retries, and throttling

Normalized JSON, CSV, and DB-ready output

Cleaned JSON, CSV, and DB-ready output

Export coverage

Know exactly what Vern pulls before you migrate.

Objects Vern extracts

Vern extracts the full set of queryable PrestaShop objects (56 total), including: Addresses, Carriers, Cart Rules, Carts, Categories, Combinations, Configurations, Contacts, Content Management System, Countries, Currencies, Customer Messages, Customer Threads, Customers, Deliveries, Employees, Groups, Guests, Image Types, Languages, Manufacturers, Messages, Order Carriers, Order Details, Order Histories, Order Invoices, Order Payments, Order Slip, Order States, Orders, Price Ranges, Product Customization Fields, Product Feature Values, Product Features, Product Option Values, Product Options, Product Suppliers, Products, Shop Groups, Shop Urls, Shops, Specific Price Rules, Specific Prices, States, Stock Availables, Stock Movement Reasons, Stock Movements, Stores, Suppliers, Tags, Tax Rule Groups, Tax Rules, Taxes, Translated Configurations, Weight Ranges, and Zones. 23 of these support incremental change tracking, so syncs pull only what changed.

Output schema

Normalized JSON per object with referential keys preserved, so the relationships between your user's records survive the import. Timestamps are returned in ISO 8601. Delivered as JSON or CSV, or loaded straight into your own application database or pushed to your API — whatever your product expects.

Where it can land

Your own application database (Postgres, MySQL), a direct push to your API or webhook, or JSON/CSV files, plus another e-commerce system (Adobe Commerce (Magento), Akeneo, Amazon Seller Partner) when a user is switching tools.

Source details

Built for the source type shown above, with extractor content refreshed from the collection record.

Managed by Vern

The details you normally have to build yourself.

Authentication

API key / access token. Your user pastes their PrestaShop API key once when they sign up; Vern stores it encrypted and attaches it to every request, handling header signing and retries so you never touch the raw credential.

Pagination

Vern detects and handles PrestaShop's paging model (cursor, page-number, or offset) internally and returns one consistent, de-duplicated result set — so you import a user's complete data without ever managing page tokens.

Rate limits and gotchas

PrestaShop enforces its own API rate limits. Vern queues and throttles requests internally so importing a new user's data never trips a 429 — even on a large account.

API-key sources rarely surface their true rate ceilings until you hit a 429 mid-import, and many silently cap page size. Vern throttles to stay under the limit and normalizes paging so a partial pull never lands a user in your product with missing data.

API quickstart

1. Create a migration for PrestaShop
curl -X POST https://app.vern.so/api/v1/migrations \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "PrestaShop → Postgres", "source": "PrestaShop" }'
→ { "migration_id": "mig_..." }
2. Generate the extraction recipe (pulls live via the PrestaShop API)
curl -X POST https://app.vern.so/api/v1/migrations/$MIGRATION_ID/runs \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "kind": "generate", "extract_via_api": true }'
3. Run the approved extraction
curl -X POST https://app.vern.so/api/v1/migrations/$MIGRATION_ID/runs \
  -H "x-api-key: $VERN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "kind": "execute" }'
4. Download the normalized CSV export
curl https://app.vern.so/api/v1/migrations/$MIGRATION_ID/exports/{template} \
  -H "x-api-key: $VERN_API_KEY" -o prestashop_export.csv

A cleaner way to extract without rebuilding source-specific plumbing.

View docs

Common questions

Can I keep a user's PrestaShop data in sync after the first import? Yes — 23 PrestaShop objects support incremental change tracking, so after the first full import Vern pulls only what changed on re-run.

Can I move a user from PrestaShop to Adobe Commerce (Magento)? Yes — Vern normalizes the PrestaShop data model into typed tables that map cleanly onto Adobe Commerce (Magento) and into your own product.

What does it cost to read the PrestaShop API? PrestaShop's own API access follows PrestaShop's pricing/plan; Vern is billed separately per import. Check PrestaShop's developer docs for their current limits.