Check files before a support-data import with Python

Work on a bounded copy

Copy a small authorised export to a test directory and retain the original. Decide the expected encoding, columns and required keys before running a validator. Large or hostile files can consume memory even when the script makes no changes.

Check syntax and structure separately

Valid JSON can still contain duplicate keys or the wrong business fields. A CSV can have a header but contain rows of different widths. Run the relevant checks separately so the reported failure tells you which assumption needs attention.

Protect what the report reveals

Prefer row numbers and counts over customer values. Formula-like cells need particular care before opening an export in a spreadsheet. Passing these checks does not authorise the import: validate the target schema and test a small transaction first.

Related tasks in the library

Two designated scripts per desk are included with a free account. Other scripts are preview listings while membership is coming soon.

• Find ragged rows before a CSV import
• Detect silently overwritten JSON keys
• Locate spreadsheet formula injection candidates

Reference documentation

• csv documentation
• json documentation

Written by Tradescore Labs. These are diagnostic starting points, not a guarantee of compatibility or a replacement for your change-control process.