RenewalDocs guide
Renewal Spreadsheet Migration: Check Dates, IDs and Totals
Move renewal records out of a spreadsheet with checks for date formats, leading zeros, attachments and record totals. A practical guide for GCC admin teams.
Start with an agreed source, not the newest file name
Moving a renewal spreadsheet into a shared workspace is a data-checking exercise before it is a data-entry exercise. Agree which workbook, sheets and entities are in scope, who owns the transfer and who can approve corrections. Keep an unchanged reference copy in an authorised location, labelled with the review date. Record any changes made while the transfer is underway so urgent renewal work can continue without disappearing between versions. This guide suggests an internal process for GCC operations, admin and PRO teams, not a legal retention schedule or a promise of automatic migration.
Map the meaning of each column
Create a small mapping sheet with the source column, its meaning, the destination field and any unresolved question. An Owner column might mean the responsible colleague or the person named on a document; do not treat those as interchangeable. Distinguish expiry dates from issue dates and internal follow-up dates. Assign each source row a stable reference that stays with it if the sheet is sorted. In RenewalDocs, the document record includes company, title, license or ID number, category, owner and expiry date. Check the destination form before transferring information; keep unsupported context in your approved working records.
Treat document numbers as identifiers
Microsoft's guidance on leading zeros explains that Excel can remove initial zeros when it converts text to numbers, and that numeric precision is limited to 15 significant digits. Treat license and reference numbers as text, using the appropriate text-column setting before entry or conversion from the original source. A fictional identifier such as 0074826 must not silently become 74826. Changing the display after information has been lost is not proof that the identifier is restored. Check suspect values against the authorised source document rather than padding every short number with zeros or guessing missing digits.
Resolve ambiguous dates before standardising them
Microsoft's date-format guidance explains that Excel's default date display follows regional settings. A value such as 03/04/2027 is therefore a poor handover reference without a known convention: it might be intended as 3 April or 4 March. Ask the record owner to confirm the date against the source, not just the workbook's appearance. If the checked source says 3 April 2027, your mapping sheet can record 2027-04-03 alongside that written-out date. Use the destination form's accepted format, then reopen the saved record and confirm the same day, month and year. Leave unresolved dates flagged for investigation.
Test a small set, including attachments
Try a small authorised set before transferring the whole register. Include records with leading zeros, a long identifier, an ambiguous date and similar company names so the trial tests likely failure points. Reopen each saved record and compare it with the checked source. Follow attachment references too: a spreadsheet hyperlink is not evidence that the file has been transferred or that another colleague can open it. Verify the intended company and document, not merely that a PDF opens. Preserve required older evidence through the organisation's retention process instead of assuming that a new attachment replaces every historical need.
Reconcile rows with explicit outcomes
In a hypothetical transfer, 24 source rows are reviewed. Two refer to records already present in the destination and five are held for verification, leaving 17 new records ready to create: 24 minus 2 minus 5 equals 17. If only 16 are confirmed saved, one remains unresolved. Account for all 24 rows as 2 existing matches, 5 held, 16 newly saved and 1 unresolved. Before retrying that last row, check whether it saved despite a lost response; a blind retry could create a duplicate. Once its save is confirmed, the outcome becomes 2 existing, 5 held and 17 newly saved.
Agree when the new register becomes authoritative
Choose a clear handover point for routine updates and reconcile changes made since the reference copy was taken. Tell authorised colleagues where to make future corrections, and avoid leaving two competing live registers without a named reconciliation owner. Check reminder dates and recipients through the supported workflow before relying on the new setup. Do not silently stop existing follow-ups while held or unresolved records still need attention. This checklist applies to a supported transfer process, including manual entry; it does not imply that RenewalDocs provides a spreadsheet importer, automatic field mapping or automatic correction of dates and identifiers.
Use a final acceptance checklist
Can every source row be traced to a saved record, an existing match or a documented unresolved item? Do company names, identifiers and verified dates match the checked sources? Can an authorised colleague open the right attachments? Are held items assigned to someone with a follow-up date? Have changes made during transfer been reconciled, and does the team know which register to update? Keep the mapping and acceptance notes in an approved location, following internal retention rules. A transfer is ready for routine use when the records and outstanding work are accounted for, not merely when data entry has finished.