Data Migration Validations

[vishnup0422]

'BC0694820','BC0694866','BC0695388',

'BC0695471','BC0695508','BC0695616',

'BC0695710','BC0696149','BC0696558','BC0696847','BC0696872','BC0697068'
please do your checks on these businesses lmk if you see any error

also see if you can double check if business summary is accurate and they should show involutary dissolution on business summary

[vishnup0422]

QA Validations :

the SYSDF_NULL fix itself worked correctly for all 12

All 12 pass on the involuntary dissolution check. Every one has a migrated dissolution / involuntary filing whose timestamp matches the COLIN SYSDF event exactly, immediately followed by a restoration / fullRestoration filing — matching the COLIN-side pattern you already confirmed:

corp_num dissolution (involuntary) restoration Current LEAR state
BC0694820 2012-01-17 2012-09-14 ACTIVE
BC0694866 2008-12-09 2009-01-20 ACTIVE
BC0695388 2008-03-18 2008-05-23 see below
BC0695471 2007-04-10 2007-06-07 ACTIVE
BC0695508 2007-10-23 2009-04-20 ACTIVE
BC0695616 2015-11-03 2019-07-10 ACTIVE
BC0695710 2010-01-12 2010-07-29 ACTIVE
BC0696149 2007-10-23 2008-12-22 ACTIVE
BC0696558 2012-07-31 2012-09-07 ACTIVE
BC0696847 2007-04-10 2008-04-25 ACTIVE
BC0696872 2007-04-10 2007-08-29 ACTIVE
BC0697068 2007-04-10 2010-08-24 ACTIVE

BC0695388 — not a migration defect. Its dissolution/involuntary (2008-03-18) and restoration/fullRestoration (2008-05-23) filings migrated correctly, same as the other 11. What flipped it to HISTORICAL is a separate, later filing: dissolution / administrative, filed 2026-09-21 21:10:22 — about 1.5 hours after its lear_tombstone migration marker (19:42:41). That's a new, post-migration event in LEAR (not backfilled from COLIN — colin_only = false), unrelated to SYSDF_NULL.