SERVICES · MIGRATION
Our own migration engines do the heavy lifting, and our engineers finish every project with you, from the first conversation to the switch. Any site is welcome, priced by its scope.
01What a Praxis migration gives you
Your pages, posts, media, menus, redirects, search settings and custom fields become native Praxis content. Pages built with Elementor or the WordPress block editor become native sections your team edits in the Composer. The old code is not pasted across: a part that cannot be rebuilt without losing words is kept as it was and held for a person's review. What other builders bring is set out, builder by builder, on our what-converts page.
Our promise, printed on our sign-up form and in every site's Migration room: "The migration is the site: plugin data is absorbed natively, plugin software does not come, and no loss is silent." Before you switch, we show you, page by page, what moved and what did not.
What your plugins held comes across as native content wherever the engine can carry it: forms, search settings, custom fields and store data among them. The plugin software stays behind, and anything that cannot be carried is named.
Our engineers compare every page with the original, in the same browser at the same size, and finish what needs a human hand. You see the before and after yourself, and you approve the switch.
The engines only read from your current site, and it stays live until you approve the switch.
Your domain moves with one record at your DNS provider. A domain that already serves a site is proven first, then moved with one switch, so the old site keeps answering until the moment it moves. Your registrar, DNS and email stay yours, and we never ask for a DNS password or token.
02Any site is welcome
Any site is welcome
Our engines are built for WordPress, and they know sites built with Elementor or the WordPress block editor best. Those convert most completely and need the least hand work, so they are priced lower. Sites made with other WordPress builders move too: our engineers carry what the engines leave to a human hand, as part of the scope we agree with you. Sites that are not on WordPress, very large sites and unusual ones are welcome too: each is scoped and priced as its own project.
03How a migration runs
We look at your site with you and agree what moves, how, and for what price. The engine's scan gives our engineers a first read of the site's complexity; it is a guide for the conversation, not a promise.
An export file, the site's public interface, an application password, or our read-only exporter plugin. Each way in reaches different parts of the site, and the engine tells you, part by part, what the way you chose cannot see.
The engines rebuild your pages as native sections, and your pages and posts arrive as drafts on your new Praxis site.
Our engineers work through every finding the engine raised: what it can fix natively, what needs your call, and what someone has to look at by hand.
You compare each page with the original, side by side at the same size, and we fix what you point at.
You accept the migration against a cutover receipt of eleven checks, as of October 2026. "Safe to turn off the source" appears only when every class of loss stands at zero.
You approve, and your domain moves with one record.
04For agencies
For agencies
Subcontract your clients' migrations to us at partner rates. We do the work under your relationship, our engineers answer to you, and your client stays your client.
05For Lighthouse customers
We migrate one site for each Lighthouse customer, or a sample of it first, at no charge, so you can see your own site working on Praxis before you decide. Very large sites are scoped with you.
06See the engine
At migrate.amadalis.ai, you can explore what each way in reaches. Our engineers run every migration with you.
See the engine07Questions
Our engineers compare every page with the original, in the same browser at the same size, and finish what needs a human hand. Pages built with Elementor or the WordPress block editor come across most completely. For other builders, our engineers rebuild by hand what the engines leave to them, within the scope we agree. You see every page side by side, and nothing moves to your domain until you approve.
It depends on the site. We give you a schedule when we scope it.
They arrive ready for each person to claim. Passwords, sessions and payment credentials never move, by design.
Their software stays behind. Your design is rebuilt as a native Praxis theme: the engine measures your live pages' colours, fonts, sizes and widths, and our engineers finish it. What your plugins held comes across as native content wherever it can be carried, and anything that cannot be carried is named before you switch.
Each form comes across as a native Praxis form with its notifications; what cannot come is named.
Yes. Products, variations, categories, coupons, tax and shipping settings come across as native data, and past orders arrive as history. A moved store runs on Praxis's own checkout, through Stripe. Our engineers scope and test every store move with you.
Translation groups from WPML or Polylang come across for posts, and pages can carry English and Spanish versions. We scope every multilingual site with you.
Each site of the network becomes its own Praxis site, with its own database, and we scope them together.
Yes. Our engines are built for WordPress; for any other platform, our engineers scope the move with you and price it as its own project.
Yes. You can explore it at migrate.amadalis.ai, and our engineers run every migration with you.
We only read from it. It keeps running until you approve the switch.