Excel Salesforce Integration: 6 Ways to Connect, Refresh and Update Data (2026)

What an Excel Salesforce integration should do

People search for “Excel Salesforce integration” with three different jobs in mind. Mixing them up is how teams end up with ten versions of the same pipeline file.

• Get data out once. A list for a mailing, a snapshot for a meeting, a backup before a cleanup.
• Keep a workbook fresh. A forecast model, a commission sheet or a board report that should show today’s Salesforce numbers when someone clicks Refresh.
• Push changes back. Mass-update territories, fix phone formats, import a trade-show list, close out stale opportunities.

The first two are reads. The third is a write, and writes are where the damage happens. Decide which job you have before you pick a tool.

Six ways to connect Excel and Salesforce

The options come from three places: Salesforce itself (report export, Data Import Wizard, Data Loader), Microsoft (Power Query, Power Automate) and third parties (Excel add-ins). Custom code on the Salesforce APIs covers the rest.

If your team works in Google Sheets rather than Excel, the Salesforce Google Sheets integration guide covers that side.

1. Export a report to Excel

The fastest route. Run a report, open the menu next to Edit, choose Export, and pick a view:

• Formatted Report keeps the report header, groupings and layout in an .xlsx file. Good for sharing a report as it looks.
• Details Only exports plain rows as .xlsx or .csv. According to Salesforce’s Trailhead, it drops formatting, groupings and subtotals, which is exactly what you want for pivot tables and lookups.

Formatted exports have row and column caps that are tightest for matrix reports, so use Details Only for anything large. Exporting is a user permission your admin can grant or withhold, and it should be withheld from most users (see security below). The file is dead the moment it lands: nothing refreshes.

2. Power Query: Get Data from Salesforce Objects or Reports

Excel’s Power Query has two Salesforce connectors, both generally available according to Microsoft Learn as of October 2026:

• Salesforce Objects loads whole objects (Account, Opportunity, custom objects) as tables, with an option to include relationship columns.
• Salesforce Reports loads the output of saved reports. Microsoft notes that Salesforce limits it to 2,000 rows, so for anything bigger, use Objects and rebuild the report in Power Query.

Availability is narrower than most people assume. Microsoft’s support table lists both connectors for Excel for the web and for Excel for Windows in two editions: Microsoft 365 Apps for enterprise and the Professional Plus editions of Office 2016 and 2019. They are not listed for Microsoft 365 Business, Home or Personal plans on Windows, or for Excel for Mac. Check your edition before you plan a rollout.

Power Query reads only. It is the right tool for a workbook that refreshes, not for updating Salesforce.

3. Data Import Wizard and Data Loader (CSV)

Both are Salesforce tools that load CSV files, so the Excel step is “Save As CSV.” According to Salesforce’s Data Loader Guide (Winter ’27):

• Data Import Wizard runs in Setup in the browser. Use it for fewer than 50,000 records, objects it supports, targets with fewer than 50 fields and simple mappings. It can prevent duplicates by matching account name and site, contact email or lead email.
• Data Loader is a desktop app for macOS and Windows (it needs Java 17 or later). It inserts, updates, upserts, deletes and exports any object, and handles up to 150 million records with Bulk API 2.0. It writes success and error files, and on Windows can run from the command line on a schedule. It is available in Enterprise, Performance, Unlimited and Developer editions, and the user needs the API Enabled permission.

4. Excel add-ins

Third-party add-ins put a Salesforce panel inside Excel: log in, pull records or reports with filters, edit cells, push changes back. XL-Connector from Xappex is a long-standing example, with a Windows desktop edition and an XL-Connector 365 edition for Mac, Windows and the web. Devart, CData and others sell similar tools.

Compare them on what you need: writeback and mass delete, scheduled refresh, Mac support, report and SOQL support, how they handle API limits, and the per-user price. Many are listed on AppExchange (now AgentExchange) or Microsoft Marketplace (formerly AppSource), so your security team can review the listing before anyone installs one.

5. Power Automate

Microsoft’s Salesforce connector for Power Automate can trigger a flow when a record is created or modified. It can also get, create, update and upsert records, run SOQL and run bulk jobs.

Pair it with the Excel Online (Business) connector, which works with files on OneDrive for Business and SharePoint, to keep a table in a shared workbook in step with Salesforce.

As of October 2026, Microsoft lists the Salesforce connector as Premium in Power Automate, so flows that use it need a premium Power Automate license. The Excel side has its own limits:

• files up to 25 MB;
• 256 rows per “List rows” call unless pagination is on;
• a file can stay locked for up to six minutes after the connector last used it.

That is fine for hundreds of rows a day, not for big syncs.

6. Custom integration on the Salesforce APIs

When the spreadsheet is really an input to a process (pricing files from finance, partner lead lists, inventory from a warehouse), code does it better. A small service picks up the file from SharePoint, OneDrive or an SFTP folder, validates it, and writes to Salesforce through the REST API, or Bulk API 2.0 for big loads. Salesforce’s Bulk API documentation suggests Bulk API 2.0 for operations with more than 2,000 records.

The Salesforce API integration guide covers the APIs in more depth, and the Salesforce data integration guide covers warehouses and ETL if Excel is really a stand-in for one.

Which option fits you?

Which Excel your users run matters as much as the job itself, because Power Query isn’t in every edition. Five questions cover both and suggest a route.

How the data flows

Treat Salesforce as the system of record and every workbook as a read-only copy that refreshes. Changes go back only through a controlled load, keyed on record IDs, never by pasting edited cells into a form.

Set up a refreshable workbook with Power Query

Most reporting workbooks are built this way. The steps below cover the decisions; Microsoft Learn shows the connector screens, which move between Excel builds.

1. Check your Excel editionExcel for Windows from Microsoft 365 Apps for enterprise or Office Professional Plus 2016 or 2019, or Excel for the web. If you don’t see Salesforce under Get Data, your edition probably doesn’t include it.
2. Check the Salesforce sideYour user needs the API Enabled permission (trial orgs have no API access). Microsoft also notes that the session setting “Lock sessions to the IP address from which they originated” blocks the connector.
3. ConnectOn the Data tab, open Get Data and choose Salesforce Objects. Pick Production, or Custom with your My Domain URL on salesforce.com; Microsoft notes Lightning URLs aren’t supported. Then sign in and allow access.
4. Pick objects and fieldsSelect the objects in the Navigator and choose Transform Data, not Load. Remove every column you don’t need. Wide queries can fail with “too many fields,” and narrow ones refresh faster.
5. Filter earlyFilter in Power Query (for example, open opportunities, this fiscal year) so only the rows you need come down. Merge Account into Opportunity on AccountId instead of pulling report output.
6. Keep the ID columnKeep the 18-character record ID on every table. It is your join key and the key for any later update.
7. Load and buildLoad to a table or the Data Model, then build PivotTables and formulas on top. Never type into the query table; edits disappear on refresh.
8. Refresh and share safelyRefresh on demand, and decide where the file lives. Anyone who opens a saved workbook sees the data in it, whatever their Salesforce access.

Update Salesforce from Excel with Data Loader

For mass updates, the safe pattern is the same whatever the tool:

1. Export with IDsExport the records you plan to change, including the Id column. This is also your backup.
2. Build a change sheetKeep only Id and the fields you are changing. Every extra column is a field you might overwrite by accident.
3. Fix Excel’s damageFormat ID, zip code and phone columns as text so Excel doesn’t strip leading zeros or turn values into dates or scientific notation. Use real picklist values and Salesforce date formats.
4. Save as CSV, UTF-8Save as CSV UTF-8 and turn on Data Loader’s UTF-8 setting so accented names survive.
5. Test in a sandboxRun the same file against a sandbox, and check what triggers, flows and validation rules did.
6. Run in production and keep the logsRun the update, then read the error file, fix those rows and rerun only them. Store the success and error files with the backup.

Column mapping: Excel to Salesforce

Most failed loads come from a handful of column types. Map these deliberately.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Refresh vs writeback

A refresh replaces what Excel shows with what Salesforce holds. It is safe because Salesforce stays the truth. Writeback is the opposite: Excel becomes, for a moment, the source of truth for whatever columns you load. Treat it as a change to production.

• Refresh suits reporting, models and reconciliation. Problems are mild: a stale number, a slow query.
• Writeback suits planned changes: territory moves, cleanups, imports. Problems are serious: overwritten fields, triggered automations, emails sent to customers, records you can’t easily restore.

Keep the two apart. A workbook that refreshes from Salesforce should not also be the file you load back. Build a separate change sheet with only IDs and changed fields.

Security and data volumes

Every Excel copy of Salesforce data sits outside Salesforce sharing rules, field-level security and audit trail. A pipeline file emailed to a partner is a data leak with good intentions.

• Limit export. Grant report export only to roles that need it, and review who has API Enabled, because API access is what Power Query, add-ins and Data Loader use.
• Store files in governed places such as SharePoint or OneDrive with access controls, not desktops and inboxes. The Salesforce SharePoint integration guide covers linking documents to records.
• Use a dedicated user for automation. Scheduled Data Loader jobs, flows and custom services should run as an integration user with only the permissions they need, not as an admin’s login. A limited number of Salesforce Integration user licenses come free with supported editions; the Salesforce integration user guide explains the setup.
• Leave sensitive fields out of queries and exports: personal data, health or financial fields, internal notes.

On volume, three limits matter:

• An Excel worksheet holds 1,048,576 rows, according to Microsoft.
• The Power Query Reports connector stops at 2,000 rows.
• Every API-based route (Power Query, add-ins, Data Loader, flows) draws on your org’s shared daily API allocation.

Salesforce’s limits reference gives the example of an Enterprise Edition org with 15 Salesforce licenses getting 115,000 requests per 24 hours, shared by every integration. A dozen analysts refreshing wide workbooks every few minutes can eat into it.

Pitfalls and how to fix them

When custom integration makes sense

Excel is a great working tool and a poor integration layer. Move to Power Automate or a custom build when:

• The same file is loaded every day or week, by hand, with the same mapping.
• The data comes from another system (ERP, billing, a partner portal) and Excel is just the carrier. Connect the systems directly; the Salesforce integration guide covers the patterns.
• Loads need validation, approvals or an audit trail that a person with a CSV can’t provide.
• Volumes or frequency start to strain API limits or add-in licensing.

A typical build is small. Files arrive in a watched folder or through an upload page, and a service validates and maps the rows. It writes with Bulk API 2.0 or the REST API, sends an error report back to the sender and alerts on failures.

The figures are taken from our API integration cost guide. Use it to judge where a file-based build with validation and error reports would land.

Go-live checklist

Before a workbook or a recurring load goes to the whole team, check off what is in place. Unchecked items are where Excel files usually leak data or overwrite records.

FAQ

Where Gilzor fits

If your team trades Excel files with Salesforce every week, the first step is an honest look at which of those exchanges should stay manual. Building and maintaining Salesforce integrations is part of what Gilzor does as a software development company; our engineers work from Poland and Cyprus. We can review how the two exchange data today and set up refreshable workbooks or safe load processes.

Where a spreadsheet load keeps coming back, we replace it with a Power Automate flow or a custom integration on the Salesforce APIs, and support it after launch. The Salesforce integration services page covers how we scope it.