Audit advanced Works with: Any AI

SharePoint Migration Readiness and Post-Migration Check

Table output Has example

• 🏢 SharePoint

Check a migration plan before and after the move.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.

Review our SharePoint migration. Plan and scope: [PLAN]. Inventory counts before: [BEFORE_COUNTS]. Results after the move: [AFTER_COUNTS]. Issues reported by users: [USER_ISSUES].

Split the answer into a readiness checklist before the move and a verification checklist after it. Readiness scoring (yes or no): inventory complete, owners agreed, permissions design approved, long file names checked, pilot done, communication sent, rollback planned, training scheduled, support rota set; proceed with the first wave only at nine of nine. After the move: reconcile counts by team in a table (120,000 files before and 119,640 after is 360 missing, 0.3 percent; 84.2 GB against 84.0 GB), find missing items and their cause, check permissions and links in key documents by sampling 20 files per team and saying how many failures trigger a wider check, and review user issues by type. For each check state the evidence needed and who signs it off. Do not switch off the old drive until owners sign off; give the criteria and a rollback plan. Plan a redirect or list of known changes because moves can break links and bookmarks [VERIFY]. Provide a message to users about known issues and a five-question survey after one week. Separate what the numbers show from assumptions.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Invented counts: before 120,000 files, 84.2 GB; after 119,640 files, 84.0 GB. Missing 360 files = 0.3 percent. Cause found for 300 of them: file names over the path limit. Fix: shorten names, re-migrate 300, investigate the remaining 60. Sample check: 20 files per team for 6 teams is 120 files; 117 opened correctly (97.5 percent); 3 had broken internal links. Permission check: 6 of 6 sampled folders had the expected groups. Decision: fix the links and repeat the sample for those two teams before switching the old drive to read-only. Sign-off by the data owners is recorded with the date.

• sharepoint