This page explains the source files, parsing rules, legacy conversion logic and cross-classifier limits behind nic-india.com.
Every page on this site traces back to a specific row in the MoSPI NIC 2025 Excel file or its companion PDF. The build pipeline parses those files, extracts Section through Sub-class records, attaches class-level notes from the official description column, and generates one page per code.
The main dataset is NIC_2025.xlsx. Sections, Divisions, Groups, Classes and Sub-classes are parsed directly from the official workbook structure. Class notes are attached from the official description rows.
NIC 2008 remains a legacy lookup layer. Old-to-new suggestions are heuristic matches based on title similarity and hierarchy prefix overlap. They are useful for migration discovery, never for direct legal substitution.
The /legacy/ hub exposes only crosswalk layers that exist in the local source-backed site: NIC 2008 to NIC 2025 and NCO 2004 to NCO-2015. The /concordance/ page tracks official historical source requirements for HSN/HS, SAC/CPC and InSCED/ISCED. HSN, SAC and InSCED historical-version pages are not generated until official concordance files are loaded locally. This prevents unsupported old-to-current equivalence claims.
Related classifier links are navigation aids, not legal equivalence claims. NIC leaf pages can link to NCO professions, HSN goods, SAC services and InSCED education fields when source-backed or deterministic semantic rules provide a useful path. Official concordance is handled separately and must expose its source file.
English and Hindi are exposed as separate route layers. Official code titles and direct source citations are preserved in source form, while UI labels, explanatory copy and trust pages are localized. As of April 21, 2026, this project did not find an official MoSPI NIC 2025 Hindi XLSX, so the Hindi layer runs on the official English NIC 2025 dataset.