How to export excel to json for crm and erp data migration
- Step 1Audit the spreadsheet before converting — Remove formula columns, subtotal rows, and merged header cells that would produce malformed JSON keys. Leave only raw data rows and a single clean header row per sheet.
- Step 2Convert one sheet at a time — If the workbook has multiple tabs — contacts, accounts, deals — use the sheet selector to convert each tab separately into its own named JSON file.
- Step 3Validate the JSON before import — Paste the output into the JSON Validator tool to catch any truncated strings, encoding issues, or type mismatches before submitting to the target system's import API.
- Step 4Upload to the target CRM or ETL stage — Use the target system's import API or file upload — Salesforce Data Import Wizard accepts JSON, HubSpot's import accepts CSV-converted output, and Snowflake COPY INTO accepts JSON in a staged S3 or Azure Blob file.
Frequently asked questions
How do I handle Excel columns with mixed data types?+
Mixed columns — where some cells are numbers and others are text strings — are emitted as strings to avoid type ambiguity. Clean the source column in Excel first (make all cells the same format), or use the string output and cast the field in your ETL transformation layer.
My migration sheet has 80,000 rows. Will the browser handle it?+
Most modern browsers process 80–100k rows without issue for an average column count. If the tab freezes during conversion, split the sheet into 25,000-row chunks before uploading. The JSON Merger tool can recombine the resulting JSON files if you need a single output.
Is migration data — customer records, financials — safe in the browser?+
Yes. The entire conversion runs locally using the xlsx library. Employee records, customer data, and financial figures in the spreadsheet are never transmitted to or stored by JAD Apps servers.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.