01
Inventory what exists
Website, PDF, pCon Catalog, OFML, Access exports, spreadsheets, images, CAD, and existing customer data.
Solution · Catalog onboarding
Turn legacy product knowledge into a reviewed ConfigAI workspace.
Catalog onboarding is not a one-time data dump. ConfigAI is designed to preserve source identity, evidence, product relationships, existing supplier structures, and the decisions required to turn old catalog data into a maintainable product system.
02
Choose the right import path
Structured supplier sources stay deterministic; ambiguous web and document sources use bounded agent research.
03
Review before migration
Preview create, reuse, update, and semantic field changes before the new product model is applied.
Source inventory
Do not flatten every old system into the same importer.
The migration path depends on the authority and structure of the source. A deterministic pCon model list, an OFML rule structure, and a public website are different evidence classes and should remain different.
Deterministic
pCon Catalog
Import product identities, article numbers, images, provider hierarchy, and available CAD directly when the provider already exposes them.
Supplier source
pCon / OFML
Preserve supplier and Gatekeeper-authorised identities, configuration structures, assets, and relationships without forcing them into a flat product list.
Agent-assisted
Website / PDF
Use bounded research and evidence capture where product structure must be interpreted from human-facing content.
Migration
Legacy exports
Map existing customer identifiers, properties, images, and 3D references into ConfigAI semantics before destructive migration decisions.
Migration workflow
Map first. Apply second.
A customer migration should produce a reviewed target product model before it changes the active catalog.
01Discover source identitiesRecord catalog, family, series, product, property, asset, and external IDs before normalization.
02Build target Product TypesCreate stable semantic fields and relationships that can support both imported legacy products and new products created later.
03Preview create / reuse / updateShow which ConfigAI records will be created, reused, revised, or left unresolved.Human review
04Apply in batchesWrite idempotent product/profile revisions while preserving source bindings and restart-safe progress.
Old and new together
Imported OFML products and new ConfigAI products should coexist.
The target architecture should not force every future manufacturer to adopt an OFML-shaped model, and it should not discard useful OFML structure from customers who already have it.
Source adapters
OFML, pCon, website, PDF, ERP exports, and manual input retain source-specific capture logic.
Common product language
Product Types, fields, components, relations, assets, and revisions form the ConfigAI domain model.
Rule-ready semantics
Stable field identities let imported and native products share rules without sharing an old file format.
Applications & agents
Configurator UI, 3D Studio, MCP, and agent tools consume the reviewed ConfigAI model.
ConfigAI
Migrate the catalog without inheriting every old limitation.
ConfigAI keeps the valuable source relationships while giving new products a more flexible, versioned product model.