SharePoint List Schema Migrator

Move SharePoint list structures between tenants — without PowerShell, without manual re-creation, without losing your lookup relationships. If you've ever had to rebuild a SharePoint list's columns by hand in a different tenant — re-typing every column, guessing at internal names, and manually recreating lookup relationships — this extension does that work for you in a couple of clicks. Pick the lists you want from a live checklist of your source site, and the extension exports their full column and view definitions to a portable JSON file. Point it at a destination site and it recreates everything — including any lookup columns' parent lists, created automatically in the right order — or syncs missing columns into a list that already exists. ✅Key features ✅Visual list picker, not manual typing Load a live list of every list on your source site, filter by name, and select as many as you need with checkboxes. No need to know exact list names in advance or run one list at a time. ✅Automatic lookup dependency resolution If List A has a lookup column pointing to List B, List B is detected and exported automatically — and created on the destination before List A, so the lookup relationship is preserved. This works recursively (B can depend on C, which can depend on D) and de-duplicates shared dependencies across a multi-list export. ✅Internal (static) column names are preserved Column internal names — not just display names — are kept identical to the source, so existing Power Automate flows, PowerApps forms, and CAML queries that reference them by internal name keep working after migration. ✅Incremental sync for existing lists Running an import against a list that already exists on the destination doesn't recreate it — it only adds the columns that are missing. If a column exists but its data type doesn't match the source, it's flagged in the activity log rather than silently changed, since SharePoint's API can't safely convert a column's type without risking existing data. ✅Views included Optionally exports and recreates list views — including filters/sort (CAML query), column order, and row limits — alongside the columns. ✅Readable activity log with CSV export Every action is logged in plain language (list created, column added, type mismatch flagged, etc.) and can be downloaded as a CSV for record-keeping or troubleshooting. ✅Works entirely in your browser session No external server, no data leaves your machine except to the SharePoint sites you're already authenticated to. The extension uses your existing browser session on each site — it doesn't store, transmit, or have access to your credentials. 🚀How it works 1. Open the source SharePoint site in a browser tab. 2. Open the extension, enter (or auto-detect) the site URL, and click Load lists. 3. Check the lists you want to migrate and click Export — a JSON schema file downloads. 4. Open the destination site (can be a different tenant) in a browser tab. 5. Open the extension's Import tab, select the JSON file, and click Create / sync lists. 6. Review the activity log for anything that needs manual attention (see Limitations below). ❓❓Known limitations (by design, not bugs) 1. Column data type changes are never automatic. If a column already exists on the destination with a different type than the source, it's flagged for manual review rather than altered — SharePoint's API doesn't support safely changing a live column's type. 2. Cross-web (sub-site) lookups aren't auto-resolved, since that requires knowledge of a second site's context. 3. Circular lookup references (List A ↔ List B referencing each other) can't be fully auto-resolved in a single pass; one side is flagged for manual linking after both lists exist. 4. Content types, permissions, and workflows are not migrated — this tool is scoped to list/column/view schema only. 🔐🔐Permissions used (and why) 🔐activeTab / scripting — needed to read and write list schema on the SharePoint tab you have open, using your existing signed-in session. 🔐downloads — needed to save the exported JSON schema and CSV log files to your computer. 🔐Host access to *.sharepoint.com — needed to call the SharePoint REST API on the tenant(s) you're working with. The extension never contacts any domain outside sharepoint.com.