The practical questions
Before you move.
What stays, what changes, and what needs a deliberate plan.
Does this move an entire CMS or application?
The workflow covers the whole application: pages, behavior, data, accounts and integrations. Your agent rebuilds the agreed scope; CMS plugins, publishing workflows and permissions need explicit replacements and checks.
Can this migrate a Node.js application too?
The downloadable skill currently targets PHP. A Node.js rebuild needs a separate assessment of server routes, npm dependencies, data, accounts and integrations. Your developer or coding agent can start with the official ICP skills ↗. A dedicated Node.js migration workflow is not included here.
Do these PHP exploits happen on Motoko?
The disclosed PHP engine flaws need the vulnerable PHP runtime. A complete replacement with Motoko removes that runtime from the migrated application. This doesn’t mean every exploit disappears: application bugs, stolen credentials, bad permissions, unsafe integrations, and insecure upgrades remain possible.
Can we keep our domain, content, and design?
Yes, subject to your approved migration plan. The inventory accounts for existing content, files, routes, redirects, design, search, and accessibility. A custom domain can point to the new ICP site after authorized DNS and registration work. Account migration and external services need their own explicit transition plans.
Can we keep our URLs and SEO setup?
Preserving established public URLs is the default. If a URL must change, the plan includes a redirect or a legacy-URL mapping appropriate to the hosting target. The agent verifies direct page loads, crawlable content, page titles, canonical tags, robots rules and the XML sitemap on the final domain. Search rankings cannot be guaranteed.
Will the agent change things immediately?
No. Start with a read-only inventory and a migration plan for your approval. After sign-off, the agent works through reversible steps. It asks again before freezing writes on the old site, changing DNS or decommissioning it.
Can Motoko run on our existing PHP host?
A normal PHP hosting plan is not a drop-in production runtime for Motoko canisters. The supported deployment described here runs the Motoko backend on the Internet Computer. You can keep a compatible static frontend on your current host and connect it to that backend, but frontend integrity still depends on that host.
What does our team still operate?
The Internet Computer provides execution and replication. Your team still owns application changes, access permissions, controller keys, cycles funding, integration health and recovery procedures. The migration handover should explain these responsibilities and the expected running costs.
Is this suitable for private or regulated data?
Assess the actual workload before choosing the architecture. Standard canister memory is not confidential from node operators. Data location, access, retention and encryption requirements belong in the plan; deploying on ICP does not by itself establish regulatory compliance. Read the platform security guidance ↗
Start with the inventory
Start with your
PHP project.
Open your codebase, copy the brief and review the migration plan.