# PHP to Motoko > Keep the service. Replace the PHP. Evaluate a rebuild of the agreed website or application with a Motoko backend on the Internet Computer (ICP), and a frontend on ICP or the current host. Begin with a read-only application inventory and a migration proposal that the owner approves before implementation. This site hosts the migrating-php-apps agent skill and an evaluation brief for public-sector, technology and engineering teams. ## Skill - [migrating-php-apps](/skills/migrating-php-apps/SKILL.md): the migration workflow, phases, rules and pitfalls. Read it before writing code. - [Download as zip](/skills/migrating-php-apps.zip): the skill folder, to add to a coding agent. - References: [inventory script](/skills/migrating-php-apps/references/inventory.md), [data import](/skills/migrating-php-apps/references/data-import.md), [backend example](/skills/migrating-php-apps/references/backend-example.md), [old URLs](/skills/migrating-php-apps/references/old-urls.md), [platform notes](/skills/migrating-php-apps/references/frameworks.md). - [Evaluation brief](/migration-evaluation-brief.pdf): printable questions covering application fit, data/residency, identity, continuity, costs and approvals. ## Scope and responsibilities The target Motoko backend runs without a PHP runtime. This does not establish regulatory compliance or eliminate application vulnerabilities. Assess dependencies and integrations, authentication/authorization, data location/confidentiality, operating costs and recovery before approving production use. Preserve critical journeys through explicit mapping and validation; do not assume plugins, passwords or third-party integrations transfer automatically. Agree on handover evidence: scope and architecture, reconciled data and files, verified critical journeys, and source/build/deployment/operating instructions. Assign owners for monitoring, cycle funding, upgrades and recovery. ## Load alongside - [ICP skills](https://skills.internetcomputer.org/llms.txt): writing-motoko, migrating-motoko-actors, mops-cli, icp-cli, static-site, internet-identity, canister-security, https-outcalls, custom-domains, cycles-management. ## Prompt for a coding agent Load the migrating-php-apps skill from https://kwnju-pyaaa-aaaao-qqkta-cai.icp.net/skills/migrating-php-apps/SKILL.md and the ICP skills listed at https://skills.internetcomputer.org/llms.txt. Start with a read-only inventory of this PHP application. Assess a Motoko backend on the Internet Computer, with the frontend on ICP. Map routes, data, users, dependencies and integrations. Review data handling, identity, deployment location and operational ownership. Propose a phased migration plan with validation, rollback, cost assumptions and approval gates. Report incompatibilities and open questions. Do not modify the application or deploy before I approve the plan.