ShopiChain platform guide
Migration.
Changing the site that displays a product is one decision. Moving the system that takes its next payment is another. See which parts of your store can move between WordPress, EmDash and Winkdom CMS.
Platform support
Choose a home for your store.
ShopiChain available
WordPress
ShopiChain eCommerce is the native engine. WooCommerce and FluentCart have storefront adapters. The SureCart adapter detects installations, with catalog and checkout support in development.
Commerce integration in development
EmDash
An open-source CMS built on Astro. Its WordPress importer provides a path for editorial content and media. ShopiChain licensing work is an early step toward native commerce support.
Planned CMS
Winkdom CMS
The planned independent CMS uses Go services and PostgreSQL. The design pairs scalable request handling with transactions for related records such as orders and stock adjustments. Serverless deployment is part of the roadmap.
Migration routes
Where are you
moving from?
Choose your current platform to see what each destination can receive.
From WordPress
Documented content import
To EmDash
Use a WordPress WXR export or the EmDash Exporter to bring across supported posts, pages and media. Preview the field mappings, inspect imported images and adapt the theme. Product variants, orders, billing and entitlements need their own migration workflow.
Planned route
To Winkdom CMS
The roadmap includes bringing WordPress content and supported ShopiChain store data into the Go and PostgreSQL platform. The import format, supported record types and release date are still open.
From EmDash
Selected returns tested
To WordPress
Selected Winkdom Builder pages have returned to WordPress as new drafts in local tests. Selected private Winkdom Docs articles have also completed a reviewed round trip. An editor can inspect those results before publication. A complete ShopiChain store return remains on the roadmap.
Planned route
To Winkdom CMS
The intended route will need mappings for content collections, media references and store records. Availability depends on a matching importer in Winkdom CMS.
From Winkdom CMS
Planned route
To WordPress
A return path is planned for supported content and commerce records. The chosen WordPress engine will determine how it can represent variants, order history and customer access.
Planned route
To EmDash
The proposed export will need to map pages and assets into EmDash collections. Commerce records will also need a compatible native module at the destination. Both the export and its receiving workflow are planned.
Store data
Follow the records behind a sale.
Start with a real order. Follow its product, payment and delivery records back to the systems that own them.
- Pages & guides
- Check the title, URL, publication state, layout and links. A product guide can move while its buy button still points to the original checkout.
- Media & downloads
- Verify the files themselves, image references and alternative text. Keep paid downloads behind the same purchase checks.
- Products & stock
- Match each SKU and variant to its price, currency, inventory and fulfillment rules. A shirt with three sizes needs three working stock records.
- Orders & refunds
- Reconcile totals, tax, shipping and refunds against the original orders. Preserve payment and shipment references for support enquiries.
- Recurring billing
- Identify which provider schedules the next charge. Verify renewal dates, cancellations and who will initiate billing after the switch.
- Software licenses
- Match a purchase to its entitlement, activation limit and renewal state. Test an existing customer’s download and activation.
- Customers & member access
- Match customer identities and verify their order history, roles and private purchases with an authorized test account.
Tested Builder workflow
Return a product guide to WordPress.
This scoped return was tested with a Winkdom Builder page and its supported assets. The merchant’s orders and billing stay with their existing engine.
Preview the return
Review the EmDash return archive against the WordPress destination. Inspect page relationships, referenced images and anything held for review.
Validate a draft copy
The reviewed import creates a new WordPress draft. Check its layout, images, links and buy button alongside the current published guide.
Choose the publication point
After editorial review, choose which page will serve the public URL. Keep the previous version and check that existing customer links resolve.
Keep a usable return point
The tested rollback checks whether the imported copies have changed or gained references. If the live store has accepted new orders, reconcile those separately before restoring any commerce data.
Plan your store move.
Tell us your current CMS, commerce engine and the records your customers rely on. We can help identify the right starting point.