Export Salesforce data to Excel on Mac.

The Salesforce-to-Excel pain on Mac

Salesforce's native export options on Mac: Reports → Export → Salesforce caps result sets at 2K-50K rows depending on context, formatting can be inconsistent, and the workflow requires manually navigating the UI for each export. Data Loader exports work but require the Java-based Apex Data Loader. Inspector exports work for inline data but require switching browsers. None of these is a clean Mac workflow for repeated Salesforce-to-Excel exports.

QueryFlow's Salesforce export workflow

Connect Salesforce once via OAuth. Write a SOQL query in the editor (or have Claude AI write one based on your description). Run the query. Export results to CSV with one click — the CSV opens cleanly in Excel for Mac with proper column types, no character encoding issues, no row limits beyond what Salesforce returns. Or export directly to a Google Sheets tab for shared access.

Schedule recurring exports

For exports needed regularly (weekly opportunity report, monthly contact list, daily new leads), schedule the query: pick a trigger (daily 8 AM, weekly Monday morning, monthly 1st), pick a destination (CSV to local folder, CSV via email, Google Sheets tab). The schedule runs locally via macOS SMAppService. Failed exports surface in the Observatory dashboard.

Bulk exports beyond row limits

Salesforce's standard API has a 50K row limit per query. For larger exports, QueryFlow automatically uses Bulk API v2 — the same async bulk operations API Salesforce recommends for big datasets. Export 500K rows of historical opportunities: works without intervention. The result still arrives as a single CSV ready for Excel.

Excel compatibility considerations

Excel for Mac handles CSV well but has some specific quirks: prefers UTF-8 with BOM for non-ASCII characters, treats leading zeros as numbers (problematic for Salesforce IDs), date format detection can be unreliable. QueryFlow's CSV export accounts for these: UTF-8 BOM included, all IDs prefixed appropriately (or written as text), dates formatted in ISO 8601 for predictable parsing. The result opens correctly in Excel on first attempt.

When Google Sheets is the better destination

For data that needs to be accessed by team members beyond yourself, exporting to Google Sheets via QueryFlow's Sheets destination is usually better than CSV-to-Excel. Reasons: Sheets refreshes automatically with scheduling, multiple people access the same data without sharing files, formulas in Sheets can reference the refreshed data dynamically. Reserve CSV-to-Excel for cases where the data goes into an existing Excel workbook or where Excel-specific features are required.

SOQL with Claude AI for non-SOQL users

Many people exporting Salesforce data aren't fluent SOQL writers. Claude AI integration in QueryFlow lets you describe what you want in English ('all closed-won opportunities last quarter with their account names and owner emails') and Claude generates the SOQL with your actual object and field names. Review, run, export.