# Webpart Mapping Reference > Supplementary reference for PnP selector functions, Community Script Editor, Quick Links layouts, and JavaScript alternatives. Read on-demand for deeper migration details. - Skill: `pnp/webpart-mapping-reference` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add pnp/webpart-mapping-reference` - Raw SKILL.md: https://api.skillmd.com/api/skills/pnp/webpart-mapping-reference/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: pnp (https://skillmd.com/u/pnp) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/pnp/webpart-mapping-reference --- # Web Part Mapping Reference (Supplementary) Companion reference for the migration pipeline skills. It contains the authoritative mapping tables, CIM schema details, and zone-aware rules used during extraction (Phase 1) and transformation (Phase 2). **For programmatic suggestions with confidence scores, always call `get_webpart_mapping_hints` first.** Use the tables below when AI judgment or exact property details are still needed. --- ## CIM Schema Specification ```json { "schemaVersion": "1.0", "extractedAt": "", "source": { "siteUrl": "", "pageUrl": "", "pageName": "", "pageType": "wiki|webpart|publishing", "title": "" }, "metadata": { "author": {}, "created": "", "modified": "", "modifiedBy": "", "contentTypeId": "", "uniqueId": "" }, "publishingLayout": { ... }, "content": { "title": "", "publishingFields": { ... }, "webParts": [ ... ], "wikiZones": [ ... ] }, "transformationHints": { ... } } ``` ### Publishing fields format Each field in `content.publishingFields` has a `type` discriminator: | Field Type | Properties | Transform Action | |------------|------------|------------------| | `image` | `html`, `imageUrl`, `altText` | `build_text_webpart(html)` without sourceUrl (cross-site) | | `richHtml` | `html`, `plainText` | `build_text_webpart(html, sourceUrl)` | | `text` | `value` | `build_text_webpart(

{value}

)` | | `dateTime` | `value`, `isoDate` | `build_text_webpart(

{value}

)` | ### Web part `modernMapping` Each entry in `content.webParts` should include a `modernMapping` object: ```json { "id": "...", "typeName": "Microsoft.SharePoint.WebPartPages.XsltListViewWebPart", "title": "Pages", "listId": "...", "listUrl": "/sites/pub1/Pages", "modernMapping": { "modernType": "List", "webPartId": "f92bf067-bc19-489e-a556-7fe95f508720", "builderTool": "build_any_webpart", "properties": { "selectedListId": "...", "listTitle": "Pages", "selectedListUrl": "..." }, "crossSiteNote": "For cross-site migration, resolve the destination site's equivalent library and update properties accordingly." } } ``` **Property validation at transform time is mandatory:** 1. call `get_modern_webpart_catalog()` to get the real property schema 2. keep only schema-valid properties 3. populate every **required** property, using `resolve_list_info` for destination-site list/view GUIDs as needed 4. use the catalog `dataVersion` example (typically `"1.0"`) instead of guessing --- ## Zone-Aware Processing Classic wiki and publishing pages can embed web parts inline with `
` markers. `extract_classic_page` splits these into `wikiZones`. ### Extract phase (Phase 1) When building the CIM: 1. consult `get_webpart_mapping_hints` for each web part 2. populate `modernMapping` on `content.webParts` 3. add a `transformationHints.note` that names the concrete strategy, not “render as placeholder” ### Transform phase (Phase 2) When processing `wikiZones`: - **HTML zone** (`webPartIds` empty): `build_text_webpart(zone.html, sourceUrl)` - **Web-part zone** (`webPartIds` non-empty): match by **position index**, then: 1. if `resolvedHtml` exists, use `build_text_webpart` or classify it into a richer web part such as Quick Links or Image 2. if `modernMapping` exists, validate it against the catalog schema, then use `modernMapping.builderTool` with `modernMapping.webPartId` and only schema-valid properties; for cross-site list web parts, call `resolve_list_info` to resolve destination-site equivalents 3. only if neither exists and the type is truly unknown, create a yellow-highlighted text fallback naming the classic type and the recommended modern alternative Never silently skip embedded web parts. For every explanatory fallback, wrap the entire notice in `...`. `build_text_webpart` converts this to SharePoint's native yellow `highlightColorYellow`. Do not highlight ordinary migrated content. --- ## Classic-to-Modern Type Mapping | Classic Web Part | Primary Modern Equivalent | Builder Tool | Fallback | Notes | |---|---|---|---|---| | ContentEditorWebPart | *Varies by content* | See CEWP Classification below | `build_text_webpart` | AI adds the most value here | | ImageWebPart | Image | `build_image_webpart` | — | Direct 1:1 mapping | | XsltListViewWebPart | List | `build_any_webpart` | `build_text_webpart` (link to list) | May need beta API | | ListViewWebPart | List | `build_any_webpart` | `build_text_webpart` (link to list) | Same as XsltListView | | PageViewerWebPart | DocumentEmbed or Embed | `build_any_webpart` / `build_embed_webpart` | — | DocumentEmbed for docs, Embed for URLs | | ScriptEditorWebPart | Embed (no scripts) or Text (with scripts) | `build_embed_webpart` / `build_text_webpart` | — | Scripts cannot run in modern pages | | SummaryLinkWebPart | Quick Links | `build_quick_links_webpart` | — | Natural mapping | | ContentByQueryWebPart | Highlighted Content | `build_any_webpart` | `build_text_webpart` | Complex queries may need manual config | | TitleBarWebPart | Text | `build_text_webpart` | — | Simple heading/caption | | Unknown types | Text + Any | `build_text_webpart` / `build_any_webpart` | — | Analyze content directly | --- ## CEWP Content Classification | Pattern | Signals | Action | |---|---|---| | Navigation / Link Lists | `