PrestaShop data extractor

Import a new customer’s PrestaShop data — addresses, carriers, cart rules, and carts, and 52 more object types — into your product as normalised, relational tables. Vern handles PrestaShop’s auth, pagination and rate limits, so onboarding a customer off PrestaShop doesn’t mean building and maintaining that plumbing yourself.

Start a migration Browse all extractors

Objects extracted: 56
Incremental: 23
Authentication: Managed by Vern

Export coverage

What Vern pulls from PrestaShop

Know exactly what comes across before you migrate. Every object below is normalised into typed tables with referential keys preserved, so the relationships between a customer's records survive the import.

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
Zones

Managed by Vern

The parts you'd otherwise build yourself

Authentication

Vern collects whatever this source needs to authenticate, stores it encrypted in a vault, and attaches it to every request. Credentials never enter the agent transcript.

Pagination

Vern detects and handles PrestaShop's paging model — cursor, page number or offset — internally, and returns one consistent, de-duplicated result set. You import a customer's complete data without ever managing a page token.

Rate limits

API sources rarely publish their real rate ceiling until you hit a 429 mid-import, and many silently cap page size. Vern queues and throttles requests to stay under the limit, so a partial pull never lands a customer in your product with missing data.

Output shape

Normalised JSON per object with referential keys preserved and timestamps in ISO 8601. Delivered as JSON or CSV, pushed to your API or webhook, or loaded straight into your application database.

Schema drift

If PrestaShop changes what it returns between migrations, the agent notices the difference against what it recorded last time and raises it, rather than importing a customer with a column quietly missing.

What it learns

Everything Vern works out about PrestaShop's quirks — field formats, enum values, ID and date patterns — is written down against the source and applied automatically to every customer you migrate off it afterwards.

What your customer provides

Access Key
Start date
Shop URL

Collected once, stored encrypted in a vault, and attached to every request. Credentials are never written into the agent transcript.

API quickstart

Run a PrestaShop migration from your own product

Create the migration, let the agent extract and map, then pull the result out — without your customer ever seeing a Vern dashboard.

app.vern.so/api/v1

API=https://app.vern.so/api/v1
KEY="x-api-key: $VERN_API_KEY"
JSON="Content-Type: application/json"

# 1 — create a migration against PrestaShop
ID=$(curl -sX POST $API/migrations -H "$KEY" -H "$JSON" \
  -d '{"name":"Acme onboarding","source":"PrestaShop"}' \
  | jq -r .migration.id)

# 2 — hand over the customer's credentials for this run
curl -X POST $API/migrations/$ID/source-connection -H "$KEY" -H "$JSON" \
  -d '{"credentials": { ... }}'

# 3 — the agent extracts, maps and previews, stopping before it writes
curl -X POST $API/migrations/$ID/runs -H "$KEY" -H "$JSON" \
  -d '{"kind":"generate"}'

curl $API/migrations/$ID/preview -H "$KEY"

# 4 — approve, then pull the normalised rows back out
curl -X POST $API/migrations/$ID/runs -H "$KEY" -H "$JSON" \
  -d '{"kind":"execute"}'

curl -X POST $API/migrations/$ID/exports -H "$KEY" -H "$JSON" \
  -d '{"slugs":["customers","invoices"]}'

The Migration API runs the whole lifecycle over HTTP with an organisation-scoped key. The agent conversation can be streamed into your own UI, and the preview lets you check exactly what an import will produce before a single row is written.

Read the API reference

PrestaShop references

Onboarding a customer off PrestaShop?

Bring a real PrestaShop export and we'll show you what lands in your product.

Request demo Start with free credits