Bring your whole store onto one platform.
Hand over a GitHub repo, a URL, or a Figma file. Mtrix moves the store — pages, products, orders, customers — and has it live within a week. Guaranteed, even for the most complex stores, with no migration fee. Or keep the store you have and run Mtrix on top.
One month free, no credit card. Migration included.
Your platform has already put a date on it.
On a custom build?
No deadline — just a standing bill for every change. Mtrix imports straight from the repo.
Build it, test it, and see the revenue in one place.
The builder edits any page with no developer and publishes to the edge. Experiments run on every page with no cap on how many. Session replay, analytics, heatmaps, error tracking and real-user performance ride on the same script — so when a number moves, you open the sessions behind it instead of opening four tabs. Revenue per visitor is a first-class metric, not an export.
It's a conversation, not a rip-and-replace.
Hand something over.
A GitHub repo is the preferred route. No repo? Mtrix's own scrapers pull the site from its URL. Starting fresh? Import the design from Figma.
The import does the heavy lifting.
Pages, products, variants, inventory, past orders and customer records come across. Most stores complete without the Mtrix team touching them at all.
A human finishes it with you.
Setup is completed rather than handed over half-built — and your app stack is mapped on the call before you commit to anything.
Live within a week. Guaranteed.
Even the most complex stores. Custom domain and SSL included, and you review everything on staging before DNS moves.
Keep your store. Keep your checkout. Switch the rest.
Not ready to move the storefront? Mtrix installs on the store you already have — an npm package or one CDN script — and gives you experiments, session replay, analytics, error tracking and real-user performance monitoring right there. First test live in about five minutes. The builder, price testing and the native checkout come with the platform when you move; the measurement doesn't make you wait.
$ npm i @novustech/mtrix
Your history doesn't disappear when you switch.
-
Orders and customers — both transfer. Past orders and customer records are imported into Mtrix during setup. Day one on the new platform starts with your history, not a blank chart.
-
Products, variants and inventory are modelled natively in Mtrix — not synced from the platform you left.
-
Your design comes from the repo or the live site, and a human finishes what the import starts.
-
Your SEO survives the move. Meta titles and descriptions, canonicals, redirects, structured data and the sitemap are all user-editable — redirects are set up so rankings follow the store.
-
The jobs your apps do — subscriptions, loyalty, reviews — are supported natively, and your specific stack is mapped one-for-one on the migration call before you commit.
-
And the exit stays open. Code export is supported. If you ever leave, you leave with your site.
The questions every switcher asks.
-
What does the migration cost?
Nothing on top of the subscription — the move and the human-finished setup are included. Platform pricing is flat across tiers and not metered on sessions, orders or profiles; talk to us for a number. The first month is free, no credit card.
-
How long does it take?
Within one week, guaranteed — that's the outside case, for the most complex stores. Most imports complete without the Mtrix team involved at all.
-
Do we lose our history?
No. Past orders and customer records both transfer during setup, and events and purchases are kept for three years once you're live.
-
What about our apps?
The jobs they do — subscriptions, loyalty, reviews — are supported natively in Mtrix. Your specific stack is mapped on the migration call before you commit, so you know what maps to what before anything moves.
-
Are we locked in?
No. Code export is supported — you can leave with your site. Contracts are monthly or annual, your choice.
-
Do we have to move at all?
No. Mtrix runs on the store you already have via npm or a CDN script — experiments, session replay, analytics, error tracking and real-user performance monitoring, without touching the platform underneath.