CRM, HRIS, ecommerce, and finance tools often export CSV—not XLSX. Drop the CSV and your PDF template, map columns once, preview free, then export one PDF per row, a ZIP, or one merged review file.
Keep one header row and one record per row. UTF-8 CSV from Google Sheets or modern CRMs works best.
For CRM and ops exports that land as CSV


If the data already left the system as CSV, do not force a detour through Word or manual copy-paste.
Vendors, attendees, orders, and contractors often arrive as CSV downloads.
Bind headers to AcroForm fields or place values on flat PDFs—CSV is just another spreadsheet input.
Name outputs from InvoiceID, Email, or FullName so the ZIP stays organized.
CSV rows are processed in the browser and are not stored as account data by default.
Keep the approved PDF; use the CSV as the data feed.
Prefer CSV when the upstream system cannot give a live Google Sheet link.
Weekly vendor, student, or order exports that land as CSV.
Teams that already have a branded PDF and only need data filled in.
Live collaborative editing inside Google Sheets with frequent cell changes mid-batch—use the Sheets path on the hub instead.
Sending each PDF with tracked e-sign envelopes (DocuSign-class workflows).
Header row + one record per row. Map once. Preview. Export.
One header row, UTF-8 if you have accents, no merged cells. Delete blank trailing rows.
Fillable forms can auto-detect fields; flat PDFs use visual placement—see [non-fillable guide](/fill-non-fillable-pdf-from-excel).
Check long values and empty optionals on a few rows before the full run.
One PDF per CSV row, optional merged review file, filenames from columns. Details: [one PDF per row](/one-pdf-per-row-from-excel).
Practical questions before you run a real batch.
If you couldn't find the answer you're looking for, please feel free to ask us!
Upload CSV + template, map once, preview free, then export when filenames and layout look right.