Skip to contentv0.1.0
PIMgate
FEATURE · VERSIONING & MIGRATION BRIDGELIVE

Change your PIM. Not your channels.

PIM Gate keeps every version of your product data and lets you run your old and new PIM side by side behind the gate. Switch one attribute group at a time, compare the results, roll back if something isn't right — while portals, shops and feeds keep receiving the same clean records.

Talk to an architectBook a demo
OLD + NEW IN PARALLELCUTOVER PER ATTRIBUTE GROUPROLLBACK
The migration bridge: switch attribute groups, not channels.An old and a new PIM feed the gate at the same time; attribute groups are switched over one at a time and can be rolled back, while the channels downstream never change.Sources · in parallelOld PIMLegacy export · read-onlyNew PIMViamedici · Akeneo · Pimcore · StiboPIM / GateSource per attribute groupCore dataold → NEWTechnical attributesold → NEWMedia & documentsOLD → newPricing & logisticsOLD → newRollback · per groupChannels · unchangedShop / DXPPortalsFeedsPrint / PDFNo channel rework · no downstream changeSwitch one attribute group at a time · roll back the same way

ILLUSTRATIVE · ANY SUPPORTED SOURCE

01 · What it does

Every state kept. Every change traceable. Every migration reversible.

Versioned exports

Each export is stored as a numbered version. Compare any two points in time side by side and see exactly which fields changed.

Delta sync

Consumers receive only the fields that changed since their last sync — about 95% smaller payloads than full exports.

Migration bridge

Old and new PIM feed the gate in parallel. Cut over per attribute group, roll back per attribute group, without touching a channel.

02 · Versioned exports

Compare any two points in time.

Every export PIM Gate produces is stored as a version. Pick any two — yesterday and today, before and after a supplier import, last quarter and now — and see side by side what changed, down to the field. When a customer asks which price or specification they received on a given date, you have the answer, not a guess.

  • Every export stored and numberedLIVE
  • Side-by-side compare of any two versions, at field levelLIVE
  • Created, changed and removed products summarised per comparison
  • The basis for audit questions and safe rollbacks

Versioned exports

Compare any two points in time.

03 · Delta sync

Consumers receive what changed. Nothing else.

Because every version is kept, PIM Gate knows the difference between any two states at field level. Consumers use it through the delta endpoint /v1/sync/diff?since= or via webhooks that point to it. A price update on twelve products is a message about twelve prices, not a new 18 MB catalog — about 95% smaller payloads, shorter sync windows and fewer re-processed records downstream.

  • Field-level change tracking on every source runLIVE
  • Delta endpoint /v1/sync/diff?since=LIVE
  • Signed webhooks pointing to the deltaLIVE
  • About 95% smaller payloads than full exports
  • Full API detail → API, feeds & delivery

Delta sync

Consumers receive what changed. Nothing else.

04 · Migration bridge

Run old and new side by side. Switch when the data is ready.

A PIM migration is usually a big-bang weekend: export, import, pray, then fix portals and feeds for weeks. With PIM Gate in between, both PIMs feed the gate at the same time. You decide per attribute group which source is authoritative — identifiers and texts from the new PIM, technical attributes still from the old one — and compare the results before a channel sees them. If a group isn't right, switch it back. Channels keep receiving the same canonical records throughout; they never learn that the PIM underneath changed.

  • Old and new PIM in parallel behind the gateLIVE
  • Source selection per attribute groupLIVE
  • Rollback per attribute groupLIVE
  • Self-service cutover in the mapping UI2026
  • Also for consolidation: several PIMs (brands, countries) into one

Until the mapping UI is released, cutovers are carried out together with our team as part of the PIM migration service (on request).

Migration bridge

Run old and new side by side. Switch when the data is ready.

05 · Stage & test

Try the cutover before production does.

A separate stage/test tenant runs on the same platform as production, with its own data, users and tokens. Rehearse a migration step, test new validation rules or a new consumer integration there first, then repeat the proven configuration in production. It's available together with a production subscription, in two sizes.

  • Separate, isolated stage/test tenant on the same platform2026
  • Half capacity at 25% of the production price
  • Full (1:1) capacity at 50% of the production price
  • Bookable only with a production subscription

Stage & test

Try the cutover before production does.

06 · Specifications

Versioning & migration at a glance.

Versioning & migration at a glance.
SpecValueStatus
Versioned exportsEVERY EXPORT STORED · NUMBEREDLIVE
CompareANY TWO VERSIONS · FIELD LEVELLIVE
Delta syncFIELD LEVEL · ~95% SMALLERLIVE
Delta endpointGET /v1/sync/diff?since=LIVE
Migration bridgeOLD + NEW PIM IN PARALLELLIVE
Cutover granularityPER ATTRIBUTE GROUPLIVE
RollbackPER ATTRIBUTE GROUPLIVE
Self-service cutover (mapping UI)—2026
Stage/test tenant50% CAP. @ 25% · 1:1 @ 50%2026
AuditAPPEND-ONLY LOG—
PIM migration serviceon request—

07 · Works with

Typical migration paths.

Viamedici EPIM → AkeneoViamedici EPIM → PimcorePimcore → AkeneoSeveral country PIMs → one group PIMCustom source → any supported PIM

Any combination of supported sources works; these are examples, not references.

Put a gate between your catalog and chaos.

Book a demoTalk to an architect