migrate-datamodel
This skill should be used when the user asks to "migrate to enhanced data model", "migrate from standard to enhanced", "switch to EDM", "migrate SDM to EDM", "upgrade data model", "migrate site data model", or wants to migrate an existing Power Pages site from the Standard Data Model (SDM) to the En…
Install / Use
npx skills add microsoft/power-platform-skills --skill migrate-datamodelInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of migrate-datamodel
migrate-datamodel scores 84/100 on our quality scale, 2947th of 4,705 Development & Engineering skills we index.
Its SKILL.md is 148 KB long, well organised into 50 sections with 8 code examples: long enough that it reads more like full documentation than a focused instruction file, which agents can find harder to follow.
It has 919 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so migrate-datamodel is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the first 100 KB of the file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.
Automated pattern scan on 2026-11-20. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
migrate-datamodel compared with similar skills
All 4 of these similar skills score higher than migrate-datamodel; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| migrate-datamodel (this skill)by microsoft | 84 | 919 | 59d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 120.0k | today | CLAUDE.md |
| hyperframesby heygen-com | 100 | 88.2k | today | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 73.0k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.5k | 1d ago | CLAUDE.md |
Frequently asked questions
- How do I install migrate-datamodel?
- Run
npx skills add microsoft/power-platform-skills --skill migrate-datamodel. The install tabs above show the steps for each supported agent. - Which AI agents does migrate-datamodel work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is migrate-datamodel safe to use?
- Our scan of the first 100 KB of the file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is migrate-datamodel still maintained?
- The repository was last updated about 2 months ago, so migrate-datamodel is actively maintained.
Skill content
View source on GitHubname: migrate-datamodel description: >- This skill should be used when the user asks to "migrate to enhanced data model", "migrate from standard to enhanced", "switch to EDM", "migrate SDM to EDM", "upgrade data model", "migrate site data model", or wants to migrate an existing Power Pages site from the Standard Data Model (SDM) to the Enhanced Data Model (EDM) using PAC CLI. user-invocable: true argument-hint: Optional site name or WebSiteId GUID allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion, Skill, TaskCreate, TaskUpdate, TaskList model: sonnet
Plugin check: Run
node "${PLUGIN_ROOT}/scripts/check-version.js"— if it outputs a message, show it to the user before proceeding.
Plugin check: Run
node "${CLAUDE_PLUGIN_ROOT}/scripts/check-version.js"— if it outputs a message, show it to the user before proceeding.
Migrate Power Pages Site from Standard to Enhanced Data Model
Guide the user through a comprehensive migration of an existing Power Pages site from the Standard Data Model (SDM) to the Enhanced Data Model (EDM). The skill is organized into four high-level phases — Site Discovery & Pre-checks, Customization Remediation, Migration Execution, and Post-Migration Validation. Each phase contains numbered sub-steps for granular execution and progress tracking.
Important: This is a preview feature. EDM migration behavior may change before GA.
Core Principles
- Environment-aware: Capture environment type (Dev/Test/UAT/Prod) for context and future ALM integration
- Remediate before migrate: Identify and fix customizations before executing the data model migration
- Validate comprehensively: Check CLI context, site discovery, dependencies, and templates before any execution
- Confirm before executing: Present all migration parameters and customization findings to user before proceeding
- Track all operations: Generate comprehensive reports documenting all commands, results, and fixes applied
- Graceful failure: Halt on blocking issues; guide user to support when needed
Supported templates: All Power Pages and D365 portal templates can be migrated, provided the corresponding V2 EDM solution is installed in the environment (see step 1.6). This includes Starter Layouts 1–5, Application Processing, Blank Page, Program Registration, Schedule and Manage Meetings, FAQ, Event Registration, and the D365 portal templates (Community, Customer Self-Service, Employee Self-Service, Partner).
PAC CLI version note: Migration of D365 portal templates requires a recent PAC CLI build. Older builds may still reject these templates.
Initial request: $ARGUMENTS
Live Execution Report
Throughout this skill, progress is mirrored to two files inside <OUTPUT_DIR>:
migration-state.json— single source of truth for current statedatamodel-migration-report.html— auto-regenerated from state after every update; user opens in browser to watch progress
Init point. At the end of step 1.3, when the parent output directory, WebSiteId, environment name/URL, and website slug are known, run once:
node "${CLAUDE_PLUGIN_ROOT}/skills/migrate-datamodel/scripts/update-state.js" --init --output-dir "<PARENT_OUTPUT_DIR>" --website-id "<WEBSITE_ID>" --env-name "<ENV_NAME>" --env-url "<ENV_URL>" --slug "<URL_SLUG>"
Capture the printed migration subfolder as <MIGRATION_OUTPUT_DIR> (also called <OUTPUT_DIR> below); the init argument is its parent, not the migration subfolder itself. After init, each sub-step below ends with a → Update report callout. Execute each as a node update-state.js --output-dir "<OUTPUT_DIR>" <args> call. The CLI accepts:
| Command | Use |
|---|---|
| --set-step <id> --status <s> --output "<text>" | Mark sub-step status + write its output line (status: pending/in-progress/completed/blocked) |
| --set-phase <n> --status <s> | Mark phase status (pending/in-progress/completed/blocked) |
| --set-site '<json>' | Update site card fields. Allowed keys: name, portalId, slug, currentDataModel, template, environment, migrationMode, siteRoot |
| --set-approval <phaseId> <kind> | Show approval banner; kind ∈ {phase-start, in-phase} |
| --clear-approval | Hide approval banner once user has approved (use only for in-phase gates that don't advance to a new phase) |
| --approve-and-start <phaseId> | Atomic: clear approval gate + mark phase in-progress in one render. Use this whenever the user answers a phase-start AskUserQuestion approval — avoids the transient "Awaiting Approval" pill that would otherwise flash between --clear-approval and --set-phase. |
| --set-input '<json>' / --clear-input | Show/clear a report-wide Your input is needed notification. JSON requires requiredAction; optional responseLocation explains where to respond (defaults to the migration conversation). Does not approve or replace a migration gate. |
| --set-prompt <plugin\|dme> --status ready --path "<file>" --summary "<text>" | Show augmented-prompt card |
| --set-operation '<json>' / --clear-operation | Structured "now running" card (label, detail, expectedDurationSec, poll) for long-running ops — drives the always-visible banner + live elapsed ticker + estimate bar |
| --add-decision '<json>' | Record a major migration decision (id, label, choice, rationale) in the Decisions & Rationale review (Migration & Review tab). Upserts by id. |
| --render-only | Re-render HTML from existing state (rare) |
Best-effort: if any
update-state.jscall fails (e.g., node missing), log a warning and continue — the live report is informational, never a blocker for migration work.
Record major decisions. Whenever the user makes a consequential migration choice — environment type, migration mode, derived track, a package install/skip, a customization-remediation approach, a reset, a rollback, or the EDM activation/restart — also record it with
--add-decisionso it lands in the Decisions & Rationale review (Migration & Review tab). Concrete calls are wired into the steps below; follow the same pattern for any other consequential migration choice. Do not record file create/update/read permission prompts or other tool-consent prompts — only migration-substance choices.
Show what's running. Wrap every notable agent-run operation with the now-running banner so the user always sees what's executing: call
--set-operation '{"label":"<present-tense description>"}'immediately before the operation and--clear-operationimmediately after (and before any user prompt/gate). For these single-shot operations omitpollandexpectedDurationSec— the animated indeterminate bar and live elapsed clock convey activity, not measured completion (theattempt N/30counter is only for the two polled migrations, 2.2 and 3.2). Wrap: approved package installs (keep the banner through installed-version verification; see below); SDM & EDM downloads; remediated upload; customization-report generation; EDM activation; approved API restart and readiness verification; rollback. Caveat: the banner needs the initialized report, so it only works from the end of step 1.3 onward — the pre-init discovery steps (1.1 CLI context, 1.3 site listing) can't show it, so don't wrap those. User-run metadata solution import and the manual site restart fallback use input notices instead of a running bar. Explicit calls are wired at the steps below.
Show every user-input pause (both tracks). After report initialization, immediately before every skill-owned question, choice, confirmation, or manual-action wait, call
--set-inputwith the specific action the user needs to take. This includes migration-status/reset choices, package consent/manual installs, environment/mode selection, metadata import, customization choices, error/retry decisions, pre-refs review, Portal ID entry, activation, and restart confirmation. Existing phase-start and remediation approvals already use--set-approval; keep those gates and their approval/clearing commands unchanged rather than adding a second notification. Both kinds of notice appear above every report tab; the sticky status pill links to the notice. Setting a notice stops the now-running display without altering phase/step progress.Once a valid answer resolves the question, call
--clear-inputbefore continuing or stopping. If the user says "Not yet" and the skill is still waiting for that same action, keep the notice; if the answer is invalid, keep it while re-prompting. On resume, resolve any saved pending input before executing the next operation.--set-operationclears a resolved input notice when work starts; approval commands also clear stale input notices. Do not mark a step complete or treat a notice as consent. File/tool permission prompts and automatic read-only polling do not need input notices. Before initialization there is no HTML report to update: use chat only, never create a second report or guess an output directory.Example (serialize JSON as one argument; replace the action with the actual question):
node "${CLAUDE_PLUGIN_ROOT}/skills/migrate-datamodel/scripts/update-state.js" --output-dir "<OUTPUT_DIR>" --set-input '{"requiredAction":"Review the metadata diff, then choose whether to continue in the migration conversation."}'After the response resolves the pause:
node "${CLAUDE_PLUGIN_ROOT}/skills/migrate-datamodel/scripts/update-state.js" --output-dir "<OUTPUT_DIR>" --clear-input
Cross-platform execution: This skill runs on Windows, macOS, and Linux with Node.js and PAC CLI; the API restart also uses Azure CLI authentication. PowerShell is not a prerequisite. Use the host's available terminal/process tool. Resolve
${CLAUDE_PLUGIN_ROOT}to the installed plugin's absolute path before executing examples; it is a host-provided path, not a required shell expansion. Command examples are single-line invocations. Pass JSON as one argument, using the active shell's quoting rules or a direct argument-array API; do not evaluate JSON as shell code or remove punctuation from its values. PAC must be on the agent process'sPATH(pac.exeon Windows,pacelsewhere); if it is missing, fix that process's PATH or restart the host after installation rather than installing another shell.Use
scripts/migration-runtime.js(under this skill) for site discovery, UTF-8 solution-list capture, portable delays, and bounded migration-status polling. It invokes PAC without a shell. The polling action emits a JSON progress record on every attempt and saves the latest full response in<OUTPUT_DIR>/migration-status.jsonandmigration-status.txt. Never substitute an unbounded shell loop.
Package installation progress
Use the existing now-running banner for every approved, agent-run pac application install, including foundation dependencies (1.5), template packages (1.6), and additional V2 packages flagged by a later PAC precheck (2.2). Do not run an install or clear an unapproved gate merely to display progress. Resolve the user's existing approval/input prompt using its normal handler first.
Immediately before launching the approved install, execute:
node "${CLAUDE_PLUGIN_ROOT}/skills/migrate-datamodel/scripts/update-state.js" --output-dir "<OUTPUT_DIR>" --set-operation '{"label":"Installing <PACKAGE_NAME>","detail":"Package installation in progress; waiting for PAC completion and installed-version verification."}'
pac application install --application-name "<PACKAGE_NAME>"
- The report shows the package name, an animated indeterminate progress bar, and elapsed time on every tab. Do not invent an installation percentage or ETA: omit
expectedDurationSecandpoll. The bar indicates activity only; it is not the workflow-completio
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
120.0kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
hyperframes
88.2kAI video you can actually edit. HyperFrames is a free, open-source AI video editor. Describe any video and get a real project you can change down to the frame.
ai-job-search
73.0kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.5kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
