[{"data":1,"prerenderedAt":746},["ShallowReactive",2],{"\u002Fblog\u002Fexcel-sharepoint-register-migration-reconciliation":3},{"id":4,"title":5,"author":6,"body":7,"category":724,"date":725,"description":726,"draft":727,"excerpt":728,"extension":729,"heroImage":728,"heroImageAlt":728,"meta":730,"navigation":731,"path":732,"seo":733,"seoTitle":734,"slug":735,"stem":736,"tags":737,"updated":728,"__hash__":745},"blog\u002Fblog\u002Fexcel-sharepoint-register-migration-reconciliation.md","Practical Data Migration Validation: Annex 11 and a SharePoint Example","QikSolve",{"type":8,"value":9,"toc":709},"minimark",[10,14,17,22,33,88,107,110,118,122,125,128,137,146,150,153,156,247,250,253,257,260,342,345,349,352,355,484,487,492,495,557,560,564,598,601,604,608,611,673,676,685,689,701],[11,12,13],"p",{},"Data migration validation asks whether a planned transfer preserves the data and meaning needed\nfor its intended use. As part of computerised system validation (CSV), define the source and target,\nassess the risks, approve the mapping, test the transfer process and reconcile the records before an authorised\ncutover. Matching row counts alone does not show that each record still means the same thing.",[11,15,16],{},"This guide relates that work to current and proposed Annex 11 provisions, then uses a realistic,\nfictional Excel-to-SharePoint quality-register migration to show the checks in practice. The data\nand decisions are illustrative: no customer migration, import or test was performed.",[18,19,21],"h2",{"id":20},"what-do-current-and-draft-annex-11-say-about-migration","What do current and draft Annex 11 say about migration?",[11,23,24,25,32],{},"For Australian medicinal-product GMP, the\n",[26,27,31],"a",{"href":28,"rel":29},"https:\u002F\u002Fwww.tga.gov.au\u002Fproducts\u002Fmedicines\u002Fmanufacturing\u002Fmanufacture-medicine\u002Fgood-manufacturing-practice-gmp\u002Fcomplying-pics-guide-good-manufacturing-practice-medicinal-products",[30],"nofollow","Therapeutic Goods Administration (TGA)","\nidentifies PIC\u002FS PE 009-17, dated 25 August 2023, as applying from 1 September 2025, except\nAnnexes 4, 5 and 14. Check the product, activity, exemptions and any transition provisions with a\nqualified reviewer; this article does not decide whether GMP applies to your register.",[34,35,36,52],"table",{},[37,38,39],"thead",{},[40,41,42,46,49],"tr",{},[43,44,45],"th",{},"Source and status",[43,47,48],{},"Migration provision",[43,50,51],{},"Practical question",[53,54,55,72],"tbody",{},[40,56,57,66,69],{},[58,59,60,65],"td",{},[26,61,64],{"href":62,"rel":63},"https:\u002F\u002Fwww.tga.gov.au\u002Fsites\u002Fdefault\u002Ffiles\u002F2026-10\u002Fpics-gmp-guide-annexes.pdf",[30],"Australian-adopted PIC\u002FS PE 009-17, Annex 11 section 4.8",", PDF page 177",[58,67,68],{},"Where data is transferred to another format or system, validation should include checks that its value and\u002For meaning are not altered during migration.",[58,70,71],{},"Can the team demonstrate that identifiers, critical values and relationships still mean what they did in the source?",[40,73,74,82,85],{},[58,75,76,81],{},[26,77,80],{"href":78,"rel":79},"https:\u002F\u002Fhealth.ec.europa.eu\u002Fdocument\u002Fdownload\u002F40231f18-e564-4043-94de-c031f813d38b_en?filename=mp_vol4_chap4_annex11_consultation_guideline_en.pdf",[30],"2025 joint PIC\u002FS–European Commission consultation draft, section 10.3",", PDF page 8",[58,83,84],{},"For an ad hoc migration of critical data or a whole database between systems, the draft proposes a validated process that considers, among other things, constraints on both the sending and receiving sides.",[58,86,87],{},"Has the team defined and tested the transfer process and understood what each side can represent?",[11,89,90,94,95,100,101,106],{},[91,92,93],"strong",{},"The consultation draft is a proposal, not a current Australian requirement."," The\n",[26,96,99],{"href":97,"rel":98},"https:\u002F\u002Fhealth.ec.europa.eu\u002Fconsultations\u002Fstakeholders-consultation-eudralex-volume-4-good-manufacturing-practice-guidelines-chapter-4-annex_en",[30],"European Commission consultation","\nclosed on 7 October 2025; its\n",[26,102,105],{"href":103,"rel":104},"https:\u002F\u002Fhealth.ec.europa.eu\u002Fmedicinal-products\u002Feudralex\u002Feudralex-volume-4_en",[30],"EU GMP index","\nlists the January 2011 revision of EU Annex 11. A newer PIC\u002FS publication or the EU draft does\nnot by itself change Australian adoption. These sources were checked on 17 November 2026; recheck\nstatus and applicability before relying on them.",[11,108,109],{},"The draft's glossary includes both raw data and metadata in its description of migration; its\ndefinition also covers format changes. Consider which source history and context need to remain\navailable, rather than assuming that a list of values alone captures the whole record.",[11,111,112,113,117],{},"The steps below are practical ways to plan and evidence a migration, not an exhaustive\ninterpretation of either text or proof of compliance. For the wider validation lifecycle, see\n",[26,114,116],{"href":115},"\u002Fblog\u002Fpractical-risk-based-computerised-system-validation\u002F","practical risk-based computerised system validation",".",[18,119,121],{"id":120},"a-practical-excel-to-sharepoint-migration-scenario","A practical Excel-to-SharePoint migration scenario",[11,123,124],{},"Imagine a quality team moving a deviation register from an Excel workbook to a SharePoint list.\nThe register points to controlled deviation records; it does not replace those records. A due date\nchanged by an ambiguous format, or a reference linked to the wrong record, could affect follow-up\neven if both systems contain the same number of rows. The process owner, migration owner and\nindependent reviewer agree which data and evidence are needed before cutover.",[11,126,127],{},"This is a fictional, illustrative worked example, not an observed customer case. It addresses a\none-off transfer, not routine synchronisation, SharePoint\nconfiguration or a finding that the target is suitable for regulated use.",[11,129,130,131,136],{},"For the platform responsibility boundary, see\n",[26,132,135],{"href":133,"rel":134},"https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fcompliance\u002Fregulatory\u002Foffering-gxp",[30],"Microsoft's guidance on GxP and its cloud services",".\nMicrosoft states that there is no GxP certification for cloud service providers and describes\nresponsibilities shared by Microsoft and its customers. Supplier evidence does not establish that\nyour configured SharePoint register or migration is validated for its intended use.",[11,138,139,140,145],{},"Where US FDA requirements are relevant, Microsoft's\n",[26,141,144],{"href":142,"rel":143},"https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fcompliance\u002Fregulatory\u002Foffering-fda-cfr-title-21-part-11",[30],"21 CFR Part 11 offering guidance","\nexplains how supplier audit reports can support a customer's own risk analysis and qualification.\nIt does not establish that the customer's application meets FDA requirements or replace the\nAustralian applicability assessment above.",[18,147,149],{"id":148},"_1-establish-the-source-baseline","1. Establish the source baseline",[11,151,152],{},"Before any transfer, identify the source workbook and version, the records in scope, the fields\nthat matter to the register's intended use, and the people who will approve the mapping and\ncutover. Preserve a controlled source snapshot and record how edits made after that snapshot will\nbe handled. Do not silently clean or reinterpret the source while profiling it.",[11,154,155],{},"For a small fictional deviation register, the agreed source baseline might be:",[34,157,158,174],{},[37,159,160],{},[40,161,162,165,168,171],{},[43,163,164],{},"Record ID",[43,166,167],{},"Status",[43,169,170],{},"Due date",[43,172,173],{},"Controlled-record reference",[53,175,176,190,203,217,233],{},[40,177,178,181,184,187],{},[58,179,180],{},"DEV-2026-0001",[58,182,183],{},"Open",[58,185,186],{},"2026-06-29",[58,188,189],{},"CR-0001",[40,191,192,195,197,200],{},[58,193,194],{},"DEV-2026-0002",[58,196,183],{},[58,198,199],{},"2026-07-03",[58,201,202],{},"CR-0002",[40,204,205,208,211,214],{},[58,206,207],{},"DEV-2026-0003",[58,209,210],{},"In progress",[58,212,213],{},"2026-07-10",[58,215,216],{},"CR-0003",[40,218,219,222,224,230],{},[58,220,221],{},"DEV-2026-0004",[58,223,183],{},[58,225,226],{},[227,228,229],"em",{},"(blank)",[58,231,232],{},"CR-0004",[40,234,235,238,241,244],{},[58,236,237],{},"DEV-2026-0005",[58,239,240],{},"Closed",[58,242,243],{},"2026-06-20",[58,245,246],{},"CR-0005",[11,248,249],{},"With 30 June 2026 as the example's fixed reporting date, the expected profile is five unique\nrecord IDs, four records not closed, one closed record, one overdue open record, one blank due\ndate, and five record references. These are expected counts for a synthetic fixture, not results\nfrom an import or a live register.",[11,251,252],{},"The baseline should also state what the counts include: the selected worksheet or table, filters,\nhidden rows, duplicate records, formulas or derived values, and any excluded data. Keep the\ndefinition stable so the source and destination are compared on the same basis.",[18,254,256],{"id":255},"_2-approve-the-mapping-before-transfer","2. Approve the mapping before transfer",[11,258,259],{},"For every field that affects identification, status, reporting or a link to a controlled record,\nwrite down the source, target, conversion rule and check. Confirm the meaning with the process\nowner; a technically accepted value can still be semantically wrong.",[34,261,262,275],{},[37,263,264],{},[40,265,266,269,272],{},[43,267,268],{},"Source content",[43,270,271],{},"Proposed target and rule",[43,273,274],{},"Reconciliation evidence",[53,276,277,294,305,318,331],{},[40,278,279,285,291],{},[58,280,281,282],{},"Record ID, such as ",[283,284,180],"code",{},[58,286,287,290],{},[283,288,289],{},"RecordID"," as text; preserve the complete identifier, including prefixes and leading zeroes",[58,292,293],{},"Compare each source ID with its destination value; list missing, duplicate or changed IDs",[40,295,296,299,302],{},[58,297,298],{},"Due date and blank cells",[58,300,301],{},"Agreed date field; define date interpretation and keep blanks distinct from placeholder dates",[58,303,304],{},"Compare each value after the approved conversion; resolve ambiguous dates before acceptance",[40,306,307,312,315],{},[58,308,309,310],{},"Status, such as ",[283,311,210],{},[58,313,314],{},"Agreed status value, using a documented mapping if labels differ",[58,316,317],{},"Compare source and destination status counts and each mapped value; do not map unknown labels to a default",[40,319,320,325,328],{},[58,321,322,323],{},"Controlled-record reference, such as ",[283,324,189],{},[58,326,327],{},"Agreed reference field or relationship",[58,329,330],{},"Check that each destination reference points to the same intended source record",[40,332,333,336,339],{},[58,334,335],{},"Historical author or entry date, if in scope",[58,337,338],{},"Separate provenance field with a defined source and format",[58,340,341],{},"Compare the retained source value; do not assume target-system created\u002Fmodified metadata represents the source history",[11,343,344],{},"Record whether a proposed mapping is approved, pending or excluded and why. If a target field\ncannot represent a required value or relationship, treat that as a decision to resolve, not a\nreason to discard the source detail without review.",[18,346,348],{"id":347},"_3-test-the-process-and-reconcile-beyond-row-counts","3. Test the process and reconcile beyond row counts",[11,350,351],{},"Before use, specify the transfer method, settings and expected results, then test with synthetic\nrecords, including invalid values and failures. Record who performed each check, actual outcomes,\ndeviations and any retest. Check the sending workbook and receiving list constraints; do not assume\nthat a successful import preserves original authorship, timestamps or history.",[11,353,354],{},"Use the same agreed scope and comparison rules on both sides. A reconciliation log can be copied\nand adapted for each migration:",[34,356,357,376],{},[37,358,359],{},[40,360,361,364,367,370,373],{},[43,362,363],{},"Check",[43,365,366],{},"Source baseline or rule",[43,368,369],{},"Destination result",[43,371,372],{},"Exception and disposition",[43,374,375],{},"Owner \u002F approval",[53,377,378,395,410,424,439,454,469],{},[40,379,380,383,386,389,392],{},[58,381,382],{},"Record population",[58,384,385],{},"Five in-scope records; scope and exclusions documented",[58,387,388],{},"Not executed",[58,390,391],{},"—",[58,393,394],{},"Process owner",[40,396,397,400,403,405,407],{},[58,398,399],{},"Stable identifiers",[58,401,402],{},"Five distinct IDs; exact text retained",[58,404,388],{},[58,406,391],{},[58,408,409],{},"Migration reviewer",[40,411,412,415,418,420,422],{},[58,413,414],{},"Critical values",[58,416,417],{},"Agreed fields and status mapping compared record by record",[58,419,388],{},[58,421,391],{},[58,423,394],{},[40,425,426,429,432,434,436],{},[58,427,428],{},"Record relationships",[58,430,431],{},"Five references resolve to the intended controlled records",[58,433,388],{},[58,435,391],{},[58,437,438],{},"Record owner",[40,440,441,444,447,449,451],{},[58,442,443],{},"Transformations and blanks",[58,445,446],{},"Approved conversion rules applied; blanks and rejected values accounted for",[58,448,388],{},[58,450,391],{},[58,452,453],{},"Migration owner",[40,455,456,459,462,464,466],{},[58,457,458],{},"Exceptions",[58,460,461],{},"Each mismatch is assigned, assessed and dispositioned; affected checks are repeated",[58,463,388],{},[58,465,391],{},[58,467,468],{},"Named exception owner",[40,470,471,474,477,479,481],{},[58,472,473],{},"Cutover and rollback",[58,475,476],{},"Acceptance authority, timing, rollback trigger and source retention agreed",[58,478,388],{},[58,480,391],{},[58,482,483],{},"Authorised decision-maker",[11,485,486],{},"The “Not executed” entries are intentional: this is a planning example, not evidence that a\nmigration passed.",[488,489,491],"h3",{"id":490},"try-the-checks-with-separate-synthetic-exceptions","Try the checks with separate synthetic exceptions",[11,493,494],{},"Keep invalid fixtures separate from the five-row baseline so they do not change the expected\nproduction population.",[34,496,497,510],{},[37,498,499],{},[40,500,501,504,507],{},[43,502,503],{},"Synthetic fixture",[43,505,506],{},"Expected check result",[43,508,509],{},"Actual result",[53,511,512,524,537,547],{},[40,513,514,519,522],{},[58,515,516,517],{},"Add a sixth row with duplicate ID ",[283,518,180],{},[58,520,521],{},"Isolate the duplicate; no silent overwrite or unexplained extra accepted record",[58,523,388],{},[40,525,526,532,535],{},[58,527,528,529],{},"Use the ambiguous source date ",[283,530,531],{},"03\u002F04\u002F2026",[58,533,534],{},"Confirm its intended meaning before conversion; do not guess a locale",[58,536,388],{},[40,538,539,542,545],{},[58,540,541],{},"Supply a status with no approved mapping",[58,543,544],{},"Flag it for an authorised decision instead of substituting a default",[58,546,388],{},[40,548,549,552,555],{},[58,550,551],{},"Change a controlled-record reference to a plausible but incorrect ID",[58,553,554],{},"Detect and resolve the relationship mismatch, not just the nonblank value",[58,556,388],{},[11,558,559],{},"An exception is not resolved by editing the destination until it agrees with an assumption. Record\nthe source value, observed destination value, decision-maker, rationale and controlled correction\nor disposition. Repeat the affected comparison after any approved correction.",[18,561,563],{"id":562},"_4-decide-whether-cutover-is-ready","4. Decide whether cutover is ready",[565,566,567,574,580,586,592],"ol",{},[568,569,570,573],"li",{},[91,571,572],{},"Control the source snapshot."," Identify the exact workbook and data range, capture the\nbaseline, and agree how later source changes will be handled.",[568,575,576,579],{},[91,577,578],{},"Profile and map."," Identify duplicates, blanks, ambiguous formats and relationships. Obtain\napproval for transformations and exclusions before the transfer.",[568,581,582,585],{},[91,583,584],{},"Run a trial with synthetic records."," Record the selected method, settings, rejected values\nand transfer identity. Do not use production records to discover how a method behaves.",[568,587,588,591],{},[91,589,590],{},"Reconcile the agreed fields."," Compare identifiers, critical values, status totals,\nrelationships, blanks and reporting outputs relevant to the register's use. Record exceptions\nand rerun affected checks after disposition.",[568,593,594,597],{},[91,595,596],{},"Obtain an explicit cutover decision."," The authorised owner decides whether evidence is\nsufficient, which source is authoritative after cutover, how a final change set is handled, and\nwhat condition triggers rollback.",[11,599,600],{},"Unexplained missing or extra records, mismatched critical values, unresolved references, or\nunapproved transformations are reasons to pause the decision and refer the exception to its\nowner. Do not run two competing copies without an agreed source-of-truth and reconciliation plan.\nRetain the source and relevant history until the authorised owner decides how they should be\nhandled under the applicable procedure.",[11,602,603],{},"The checks here are recommendations to adapt to the intended use; they are not a universal\nregulatory checklist, a fixed sampling rule, or proof of compliance. A qualified reviewer should\nassess applicability, evidence sufficiency and retention against the relevant requirements and\nprocedures.",[18,605,607],{"id":606},"bring-the-evidence-together-for-the-cutover-decision","Bring the evidence together for the cutover decision",[11,609,610],{},"For this register example, organise the outputs into a review pack that lets the authorised owner\ntrace each acceptance decision back to its evidence. Agree its contents before execution; a useful\nstarting point is:",[34,612,613,623],{},[37,614,615],{},[40,616,617,620],{},[43,618,619],{},"Decision to support",[43,621,622],{},"Evidence to bring together",[53,624,625,633,641,649,657,665],{},[40,626,627,630],{},[58,628,629],{},"What was meant to move?",[58,631,632],{},"Identified source snapshot, in-scope records, exclusions and approved field mappings",[40,634,635,638],{},[58,636,637],{},"What would count as acceptable?",[58,639,640],{},"Agreed acceptance criteria, comparison rules, test cases and named reviewers",[40,642,643,646],{},[58,644,645],{},"What actually happened?",[58,647,648],{},"Transfer log, rejected records, completed reconciliation and retained test evidence",[40,650,651,654],{},[58,652,653],{},"What still needs a decision?",[58,655,656],{},"Exception log, impact assessments, approved corrections and affected retest results",[40,658,659,662],{},[58,660,661],{},"Can the team change over safely?",[58,663,664],{},"Final source-change reconciliation, cutover approval and tested rollback arrangements",[40,666,667,670],{},[58,668,669],{},"How will the old information remain available?",[58,671,672],{},"Source-retention decision, responsible owner and evidence that required history can be retrieved",[11,674,675],{},"If work continues in the source after the trial, identify and reconcile those later changes before\nthe final decision. For rollback, agree how records created or changed in SharePoint after cutover\nwould be recovered and reconciled, rather than assuming that reopening the workbook is sufficient.\nApproval to use the target does not itself authorise deleting the source or its history; record\nthose retention and disposal decisions separately under the applicable procedure.",[11,677,678,679,684],{},"This is a suggested review structure, not an executed evidence pack or a regulator-issued template.\nFor a broader discussion, see\n",[26,680,683],{"href":681,"rel":682},"https:\u002F\u002Fintuitionlabs.ai\u002Farticles\u002Fgxp-data-migration-validation-evidence-pack",[30],"IntuitionLabs' cutover evidence-pack approach to GxP data migration validation",".\nIt is third-party implementation commentary, not the authority for Australian requirements.",[18,686,688],{"id":687},"choose-the-next-step","Choose the next step",[11,690,691,692,696,697,117],{},"For the register's field dictionary and data checks, see\n",[26,693,695],{"href":694},"\u002Fblog\u002Fsharepoint-register-fields-and-data-checks\u002F","SharePoint Register Validation: A Worked Example of Field Settings and Tests",".\nFor the wider question of record purpose and system use, read\n",[26,698,700],{"href":699},"\u002Fblog\u002Fvalidating-a-sharepoint-quality-register\u002F","Validating a SharePoint Quality Register",[11,702,703,704,708],{},"If you are assessing a suitable one-register move, the ",[26,705,707],{"href":706},"\u002Fsolutions\u002Fexcel-register-to-sharepoint\u002F","Excel register migration and validation\nsign-off pack"," is the relevant QikSolve service pathway.\nStart by confirming fit, mapping, evidence scope and authorised review; migration is not the\nautomatic answer for every register.",{"title":710,"searchDepth":711,"depth":711,"links":712},"",2,[713,714,715,716,717,721,722,723],{"id":20,"depth":711,"text":21},{"id":120,"depth":711,"text":121},{"id":148,"depth":711,"text":149},{"id":255,"depth":711,"text":256},{"id":347,"depth":711,"text":348,"children":718},[719],{"id":490,"depth":720,"text":491},3,{"id":562,"depth":711,"text":563},{"id":606,"depth":711,"text":607},{"id":687,"depth":711,"text":688},"Compliance","2026-11-17","Plan data migration validation with mapping, reconciliation and cutover checks. Compare current and draft Annex 11 through a fictional SharePoint register example.",false,null,"md",{},true,"\u002Fblog\u002Fexcel-sharepoint-register-migration-reconciliation",{"title":5,"description":726},"Data Migration Validation: Annex 11 and SharePoint","excel-sharepoint-register-migration-reconciliation","blog\u002Fexcel-sharepoint-register-migration-reconciliation",[738,739,740,741,742,743,744],"excel","sharepoint","data-migration","reconciliation","quality-register","computerised-system-validation","annex-11","Uu7MXZFc1Uiy0oQHEhxo2qRWrdboxs5dYFXJg50AKgs",1795045275802]