System Migrator
Bring the existing company with you.
The System Migrator on 2finity.dev moves a legacy system into CORE in five stages, then generates the website, applications and agents on top. WordPress and WooCommerce first.
Process
Legacy system to CORE
Discover, extract, understand, map, build. The first three stages read the legacy system without modifying it; the fourth assigns every record type to a CORE layer; the fifth generates interfaces that read and write through the CoreClient.
Each stage produces an artifact you can inspect before the next one starts: an inventory, the raw records, a documented model, a mapping and finally the interfaces.
The System Migrator reads WordPress and WooCommerce today; Shopify, Magento, ERP systems, CRM systems, Custom PHP and Node applications, Spreadsheets and Legacy databases are planned. It runs these stages in order:
- Discover: Crawl and inventory the legacy system: pages, products, users, forms, integrations. Output: Inventory.
- Extract: Read data through a read-only connector. Nothing is modified at the source. Output: Raw records and media.
- Understand: Classify what the records mean: content, catalog, customers, roles, processes. Output: Documented model.
- Map to CORE: Assign every record type to a CORE layer and the capabilities that act on it. Output: CORE mapping.
- Build interfaces: Generate the website, applications and agents that read and write through CoreClient. Output: Interfaces on CORE.
The result is a CORE with Website, Applications and Agents built on top of it.
Mapping
What goes where
A WordPress or WooCommerce installation already contains most of the ten layers in disguise. Pages are Knowledge, products and orders are Commerce, customers are People, user accounts are Identity and their roles are Relationships, forms are Data.
| Source | CORE layer | Note |
|---|---|---|
| Pages and posts | Knowledge | Published content becomes versioned pages. |
| Media library | Knowledge | Files attached to the content that uses them. |
| Products, categories, variations | Commerce | Catalog entries with variants and prices. |
| Orders | Commerce | Order history keeps its customers. |
| Customers | People | One person per customer, linked to orders. |
| Users | Identity | Accounts become identities. |
| Roles | Relationships | Roles become editor, administrator and owner relationships. |
| Forms and submissions | Data | Submissions become records with events. |
| Invoices and payments | Finance | Finance records linked to the orders they settle. |
| Menus and settings | Knowledge | Site structure as a collection. |
Sources
Supported now, planned next
The Migrator reads WordPress and WooCommerce today, behind the 2finity.dev operator login while it is in development. Shopify, Magento, ERP and CRM systems, custom PHP and Node applications, spreadsheets and legacy databases are planned, each with a read-only connector.
Now
- WordPress
- WooCommerce
LaterPlanned
- Shopify
- Magento
- ERP systems
- CRM systems
- Custom PHP and Node applications
- Spreadsheets
- Legacy databases
Outcome
Not just a website
The output of a migration is not a redesigned website. It is a company system on CORE: the website, the internal applications and the agents that act on the same records, with identity, permissions and history from the first day.
The old site keeps running until the new interfaces are approved. Nothing at the source is modified during extraction.