Move the catalog.
Every SKU. Every variant.
Migrate multi-brand catalogs between Shopify, Salesforce Commerce, Magento, and headless PIMs without breaking SKU↔asset relationships, variant trees, alt text, or schema.org markup. One product arrives as one product — hero shots, swatches, lifestyle, video, AR, every regional crop.
- JPEG · WebP · AVIF
- schema.org/Product
- Open Graph · Twitter Cards
- sRGB · Display P3
- USDZ · glTF
- Akeneo · Salsify · Pimcore
Source SKU
SKU-A4290
Linen Blazer · oversized
12 colors · 6 sizes
hero_front_4k.webp
Primary listing image
hero_back_4k.webp
Alt view
swatch_stone.png
Color: Stone
swatch_olive.png
Color: Olive
lifestyle_01.jpg
On-model · campaign Q3
mobile_crop_1x1.webp
PDP mobile crop
model.usdz
AR / 3D viewer
demo.mp4
15s product video
Why commerce is different
File migration tools don't understand catalogs.
Four constraints make a commerce migration fundamentally different from moving a folder of images. Univaultport is built around all four — and the cutover playbook reflects them.
- Bindings get severed
SKU ↔ asset relationships
A product is not a file. It is a SKU bound to a hero shot, alt views, swatches, lifestyle photography, video, AR — plus the alt text, the schema.org markup, the OG tags, the review images. Move any one of them without preserving the binding and the PDP breaks.
- Tooling melts at scale
Variant explosion
12 colors × 8 sizes × 3 crops × 4 locales is 1,152 physical files for one logical product. Multiply by 20,000 SKUs and you have a 23-million-asset migration. Generic tools cannot index that, let alone keep it consistent.
- Cross-region fallbacks misfire
Locale-specific imagery
Models, packaging, regulatory copy, on-image text — all of it changes per region. A Japanese PDP cannot fall back to the US hero shot. The localized variants have to migrate alongside the master and stay bound to the right SKU per locale.
- Live catalog drifts
PIM reconciliation during cutover
You cannot freeze a catalog for the duration of the move. Pricing changes daily, new SKUs ship weekly, seasonal campaigns rotate. The migration has to run alongside live commerce, reconcile against the source PIM continuously, and not lose a single update.
What travels with the SKU
Nine artifact categories. All bound to the product record.
Univaultport treats a SKU as the migration unit — every binary, every metadata field, every relationship to other products moves with it. Cutover day, the PDPs render identically on the destination.
Hero shots & alt views
Front · back · side · detail crops. Per-SKU primary image flag survives. Every angle stays bound to the same product record on the destination.
Color & material swatches
sRGB and Display P3 swatches per variant. Pantone references where supplied. Color naming preserved verbatim across destinations.
Aspect-ratio crops
PDP, PLP, mobile (1:1, 4:5, 3:4), tablet (16:9), social (story, reel). Crop coordinates round-trip — no re-cropping needed on the destination.
Lifestyle & campaign imagery
On-model, in-context, seasonal campaign shots. Campaign tags, scheduling windows, and on-image text variants all carry over.
3D · AR · spin
USDZ for AR Quick Look, GLB / glTF for the web viewer, 360° spin frame sets. All variant views bound to the same SKU.
Localized variants
Per-locale hero shots, regional models, language-specific on-image copy. Falls-back hierarchy preserved (en-US → en-GB → en) so PDPs never render blank.
SEO metadata
Alt text per language, image title, schema.org/Product markup, Open Graph + Twitter Card refs. Indexable on day one of cutover.
Approval & workflow state
Asset status (draft · review · approved · published), reviewer history, scheduled go-live timestamps, retirement dates.
PIM bindings & relationships
SKU ↔ asset bindings, variant tree (color × size), bundle composition, swap-with refs, and cross-sells. Catalog relationships intact.
Inside the catalog move
Five stages, one cutover, no broken PDPs.
The ingest console shows where every SKU is in real time — and the reconciliation step guarantees the destination matches the source PIM at cutover, even though the catalog kept changing the whole way.
Scan
Catalog + PIM bindings
Map
SKU ↔ variant tree
Transform
Render any missing crops
Land
Push to destination commerce
Reconcile
Diff against source PIM
Format support
Every format your storefront actually serves, plus the structured data behind it.
Image binaries pass through byte-for-byte; we only re-encode when you explicitly ask us to (e.g. to add an AVIF variant in flight). Structured-data markers travel with the asset so SEO doesn't regress on day one of cutover.
Image formats
- JPEG · MozJPEG
- PNG · APNG
- WebP · animated
- AVIF
- JPEG XL
- HEIC · HEIF
- SVG · EPS
Video & motion
- MP4 · H.264 / H.265
- WebM · VP9 / AV1
- GIF · animated PNG
- HLS · 360° spin sets
3D · AR · spin
- USDZ· Apple AR Quick Look
- glTF · GLB· web 3D viewer
- FBX · OBJ· source meshes
- Spin · 36 frames· turntable
Structured data
- schema.org/Product
- schema.org/Offer
- schema.org/AggregateRating
- Open Graph · og:image
- Twitter Cards · summary_large_image
- JSON-LD · RDFa
Color & ICC
- sRGB IEC61966-2.1
- Display P3
- Adobe RGB
- ICC profile preservation
- Color name + Pantone refs
Catalog exchange
- Akeneo CSV / XLSX
- Salsify exports
- Pimcore PIM XML
- Shopify CSV / GraphQL
- Magento CSV / REST
- GS1 ICECat
- PIES · ACES (auto)
Ecosystem
Talks to the commerce stack you already run.
Commerce platforms, PIMs, brand DAMs, imaging CDNs, and ERP / back-office systems. Native connectors for the widely-deployed platforms; custom connectors for headless, marketplace, and in-house systems.
Custom commerce connectors
Headless storefronts, marketplace platforms, B2B portals, in-house PIMs. Share the API contract — we ship a production connector in 2–4 weeks with the same observability as our native ones.
Commerce platforms
Shopify Plus
● native
BigCommerce
● native
Salesforce Commerce Cloud
● native
Adobe Commerce · Magento
● native
commercetools
● native
Spryker
● custom
Mirakl marketplace
● custom
PIM systems
Akeneo
● native
Salsify
● native
Pimcore
● native
Plytix
● native
inriver
● custom
Riversand · Syndigo
● custom
DAMs & brand portals
Cloudinary
● native
Bynder
● native
Brandfolder
● native
Widen
● native
Frontify
● custom
AEM Assets
● native
Imaging & CDN
Imgix
● native
Cloudinary delivery
● native
Akamai Image Manager
● native
Fastly · Image Optimizer
● native
AWS CloudFront
● native
Storage & ERP back-office
Amazon S3
● native
Azure Blob
● native
Google Cloud Storage
● native
NetSuite
● custom
SAP Hybris
● custom
MS Dynamics 365
● custom
Reference scenario
A multi-brand retailer's 12-brand consolidation.
Representative shape. Numbers below match the median of multi-brand retailer engagements we've sized; the narrative is a composite, not a specific customer.
“The reconciliation report is what got us through Black Friday. We cut over 11 weeks before peak — knowing every SKU on the new storefront matched the source PIM down to the variant level.”
VP of Digital Commerce · Multi-brand retailer · North America
0 brands
consolidated into one DAM
0+
SKUs migrated
0 locales
PDPs live on day one
0%
SKU-level parity
Cutover window
11 weeks
rolling, with parallel ingest from week 3
SKU bindings
0 lost
every variant tree, every bundle, every cross-sell intact
Schema.org markup
preserved
rich-result coverage maintained day one of cutover
Black Friday risk
cleared
reconciliation guaranteed parity 6 weeks before peak
Frequently asked
What commerce ops teams always ask first.
Book a commerce migration call
Map your catalog with a commerce solutions architect.
30 minutes. We sketch your source → engine → destination flow on the call, pick the right reconciliation strategy for your PIM, and you leave with a written architecture either way.
- Connector compatibility map for your commerce + PIM stack
- Commerce playbook + reconciliation strategy emailed after the call
- Variant tree complexity assessment
- Honest fit assessment — we say no if we are not the right tool
Move the catalog.
Keep the SKUs.
A 30-minute call with a commerce solutions architect. Bring your catalog spec; leave with a written migration plan you can hand to your VP of Digital.
Univaultport for E-commerce · SKU-bound. PIM-reconciled.