INTEGRATIONS · EXPERTINI ATS

Microsoft Excel Export

One click turns candidates, jobs, applications, reports, or clients into a real .xlsx workbook in your OneDrive — through the Microsoft connection you already have.

2 min read · Updated July 2026 · Expertini Editorial

Every hiring team lives partly in spreadsheets — board packs, agency reports, offer approvals, headcount reconciliations. The question is how the data gets there. The Excel export gives every list in Expertini ATS a one-click path to a genuine .xlsx workbook, created in your own OneDrive under an "Expertini ATS" folder and opened in Excel exactly as Excel expects: real columns, real rows, no CSV encoding surprises, no download-then-reupload shuffle.

It rides the Microsoft connection your organisation has already made for sign-in, Outlook calendar, Teams meetings, and OneDrive backup — no new permission, no separate app. Excel, OneDrive, and Microsoft 365 are trademarks of Microsoft Corporation; the export uses Microsoft's official Graph API against your own account, and the files it creates are yours, in your storage, under your organisation's own retention rules.

▶ Watch the 30-second overview — no sign-up needed

01How to use it

Wherever you see the Excel button — the Export Center, the candidate database, reports — click it and the ATS builds the workbook server-side and writes it to OneDrive → Expertini ATS. The response links you straight to the file, already shareable with your team through Microsoft's own sharing. If Microsoft isn't connected yet, the button routes you to the Connectors page first — the guided flow tells you what's missing instead of failing quietly.

02What exports today

Candidates (with current title, location, source, and consent state), the reports overview, and the Export Center's list views all ship with Excel buttons alongside their Google Sheets equivalents — the two ecosystems get equal treatment. Each export is a fresh snapshot at the moment you click, which makes it a clean audit artefact: the file says what the system said, when.

03Built without add-ins or macros

The workbooks are plain, standards-compliant Office Open XML — no macros, no add-ins, no external references — so they open cleanly in Excel on the web, desktop Excel, and anything else that reads .xlsx. Security-conscious IT teams can treat them as inert data files, because that's what they are.

04Excel or Sheets — or both

Organisations rarely live in one ecosystem. Every export surface offers Google Sheets and Excel side by side, so the recruiter chooses per file, not per policy. Connect either or both; nothing about the ATS assumes which office suite you standardised on.

Engineering notes

Platform architecture & operations

A1Connection architecture

The connection model for this integration is stated honestly on its card: where a public API exists it is used with your own account and consent, and where a vendor requires a partner agreement the page says so instead of showing a Connect button that cannot work.

Once available, credentials follow the platform standard: encrypted at rest, presence-flag display, immediate removal on disconnect.

A2Write semantics and data flow

Every data movement is an explicit action with a logged result. Writes happen on your click — or automatically only where you enabled a rule (auto-push on hire is off by default, per-provider). Reads — imports of people, accounts, or files — run when you press Import, deduplicate against what you already have (clients by name, people by email), skip rather than overwrite, and report created-versus-skipped honestly, which is why re-running any import is safe by design.

Each action writes a row to the app-activity journal (ats_app_activity): what ran, when, for which record, and the outcome — including the vendor's own error text verbatim when something fails. Usage reporting inside the ATS aggregates that same journal, so integration reporting and integration reality cannot diverge.

Anything that leaves the request path — notification fan-out, webhook delivery, activity journalling, mail — runs in fire-and-forget background threads. A slow external endpoint can never make the interface hang, and a failed side effect is logged rather than silently retried into inconsistency.

A3Operational considerations

Connections are organisation-level and gated to owner and admin roles; recruiters use the features a connection powers but cannot connect, disconnect, or reconfigure. Disconnecting removes stored credentials immediately and stops the dependent features visibly, not silently. Data already imported stays yours and editable.

Imported people arrive marked as imported with conservative privacy defaults — no consent is assumed for anyone who never filled in your application form, and retention defaults apply. Everything written is yours to take: CSV exports and the Data Export app cover the same stores the product itself reads. The exit is as open as the entrance — by design, not concession.

A4Placement in the integration topology

This integration is live in the registry today. One connection per provider unlocks every feature it powers, and the topology grid below shows the neighbouring connectors in the same capability area — statuses come from the same registry that drives the in-app hub, so this page can never claim more than the product does. For anything the catalogue does not cover, Webhooks and Zapier are the generic, documented escape hatch.

Dependency map

Connection typestated per-vendor on the card

Secrets at restencrypted; UI shows presence flags, never values

Action journalats_app_activity — one row per action, vendor errors verbatim

Auto-push rulesoff by default, per-provider, every run logged

Registry statuslive

Interface blueprint

Structural schematic of the surface — panels, hierarchy, and interaction affordances. A contract, not a screenshot.

Connection card

● connected — presence flag

scopes: minimum required disconnect

Actions

push — explicit clickimport — deduplicated

Activity journal

Fig. 1 — Microsoft Excel Export: structural interface schematic. Panels and states are the contract; data shown is placeholder.

Interaction flow — states, validations, feedback

Every state below is enforced server-side; the interface reports it, it doesn't decide it.

Connectowner/admin clicks Connect on the Connectors page

Vendor consentthe vendor's own screen lists the exact scopes

Token exchangeserver-side callback; secrets never touch the browser

Connectedencrypted store; card flips with presence flag

Explicit actionspush / import / schedule — each one journalled

Consent denied → the vendor's error code surfaces in a toast, namedPlatform keys missing → honest setup pointer, not a silent bounceToken expired → automatic refresh at the chokepointRefresh rejected → visible reconnect prompt, features never break silentlyPlan below minimum → lock card names the exact plan

Fig. 2 — interaction flow: navy = states, gold = server-enforced gates, green = confirmed outcomes; tags list the edge cases and their feedback.

Neighbouring connectors — Documents

Google Sheetslive Google Docslive Microsoft Excelthis page Microsoft Wordlive

Statuses come from the live registry — browse the full catalogue →

Frequently asked questions

Where do the files go?⌄

Into an "Expertini ATS" folder in the OneDrive of the connected Microsoft account, created automatically on first export. Sharing and retention follow your own Microsoft 365 policies.

Do I need a new Microsoft permission?⌄

No. The export uses the file permission your existing Microsoft connection already granted for OneDrive features — one connection covers sign-in, calendar, Teams, OneDrive backup, and these exports.

Are the files real Excel workbooks or renamed CSVs?⌄

Real .xlsx workbooks — proper worksheets with typed cells, generated server-side in the standard Office Open XML format, no macros.

Is Expertini affiliated with Microsoft?⌄

No. Microsoft, Excel, and OneDrive are trademarks of Microsoft Corporation. The integration uses Microsoft's official Graph API with your own account.

Does it cost extra?⌄

No — included in the plan, with no per-export fees. See pricing.

At a glance

Real .xlsx workbooks, not renamed CSVs
Created directly in your OneDrive "Expertini ATS" folder
Candidates, reports, and Export Center lists covered
Same one-click pattern as Google Sheets — both ecosystems equal
No macros or add-ins — clean, standards-compliant files
Uses your existing Microsoft connection, no new permissions

See microsoft excel export on your own hiring.

Bring a real job description to a 30-minute demo — free trial included.

Book a demo