Assess the source before you process it
Check the delimiter, header row, approximate file size, column count, and available disk space. Ten million rows is a useful warning sign, not a complete performance measurement: quoted text, wide rows, storage speed, and the operation you choose all affect the workflow.
Preview first
Open the dataset and inspect columns, row samples, dates, IDs, and missing values before deciding how to clean or transform it. Start with one concrete question rather than trying to load every field into a spreadsheet.
Reduce rows and columns early
Narrow millions of rows by date, status, category, number range, or text pattern. Keep only the columns needed for the next decision so the result is smaller, easier to review, and safer to share.
Split when the destination has a limit
If another system has a row, size, or upload limit, split the source by a stable rule such as a row count or a meaningful column value. Keep the header in each output and retain the original source unchanged.
Validate before handoff
Compare output row counts, expected columns, and a sample of records with the source before sending a derived CSV to a teammate, spreadsheet, or import process. This turns a large-file task into a repeatable workflow rather than a one-off guess.
Export only what matters
Create smaller CSV outputs from selected rows or columns for reporting, review, sharing, or downstream processing. Keep the raw source local and export the focused result that the next tool can handle.