Older records, software and legacy reports can still refer to ANZSIC 1993. Current reference work is usually based on ANZSIC 2006 Revision 2.0, so a migration step is often needed.
Historical reports, internal systems and archived datasets often retain the earlier classification because changing industry structures in legacy systems can be expensive.
That means modern teams still need a clean bridge from 1993 labels to the 2006 hierarchy.
Some mappings are straightforward. Others split, merge or move across neighbouring categories. A historical code may therefore need interpretation rather than blind replacement.
Use the correspondence page as a lookup tool, then validate the result against the destination class descriptions.
Once a likely 2006 code is identified, open the class page and verify the definition, primary activities and exclusions.
That extra step is what prevents a historical mapping from becoming a current misclassification.
These guides are editorial support content. They explain how the classification systems are commonly used in practice, but they do not replace the official ABS, ATO or government process that controls the final decision.
No. Some correspondences are not a simple one-to-one swap and should be checked against the destination class wording.
New classification work should use the current ANZSIC 2006 Revision 2.0 reference unless an official workflow explicitly requires a legacy version.
They reduce the risk of guessing when an old code appears in a report, dataset or internal business system.
This guide is an independent editorial reference. Verify tax, visa, registration, licensing and compliance decisions with the relevant official authority.
Please verify critical classification decisions with the official authority before using them for tax, payroll, licensing, immigration or compliance work.