Automation & workspaceUSDeals, payments and stock from the CRM land in the Excel workbook your team already lives in, and rows added in Excel come back into the CRM.
Half of the companies we meet keep the real numbers in Excel: a price list the owner edits by hand, a payment log the accountant trusts more than any system, a weekly report the director wants as a workbook. We do not fight that. The connection keeps the workbook in OneDrive or SharePoint in step with the CRM: a closed deal becomes a row, a changed price in the sheet updates the product in the CRM, and the report the director opens on Monday is already filled in.
Before every Friday the sales lead spends two hours copying deals from the CRM into the director's workbook, and the numbers are already stale by Monday.
After the CRM writes every closed deal, its amount and its manager into the report sheet as it happens; the formulas and charts on the summary tab work on live rows, and Friday evening belongs to the sales lead again.
Before the owner updates prices in a workbook, then someone retypes them into the CRM, and for a week managers quote from two different lists.
After the owner keeps editing the same workbook; the connection reads the changed rows and updates the products in the CRM, so every new quote uses today's price and nobody retypes anything.
Before the accountant records incoming payments in a workbook, the manager marks deals as paid in the CRM from memory, and at month end the two lists disagree.
After a payment row entered in the workbook finds its deal in the CRM by invoice number and marks it paid; a deal marked paid in the CRM appears in the log with the date and amount, and the month closes without a reconciliation evening.
Before the warehouse keeps stock in a workbook, and a manager promises a client goods that were sold yesterday.
After the connection reads the stock sheet several times an hour and shows the current quantity next to the product in the CRM; when stock hits zero the product is hidden from new quotes until the warehouse updates the row.
For those who want to check: each point links to the official documentation page it comes from.
Microsoft's own interface lets an application read and change Excel workbooks that are stored in OneDrive or SharePoint — the same files people open in Excel on their desktop.
Source: learn.microsoft.com ↗ checked 2026-09-28Microsoft describes Excel as a data store inside Microsoft 365: whatever is in a workbook is available to any application connected to Microsoft 365, and such applications can use Excel to keep their data.
Source: learn.microsoft.com ↗ checked 2026-09-28The connection works with the parts of a workbook people actually use — tables, ranges of cells and charts — and can create, read, update and delete them.
Source: learn.microsoft.com ↗ checked 2026-09-28When an application makes more than one or two changes to a workbook, Microsoft recommends opening a working session with it; in a persistent session every change is saved into the workbook itself, and this is the most efficient way to work.
Source: learn.microsoft.com ↗ checked 2026-09-28There is also a draft mode: changes are not written to the original file but kept in a temporary copy on Microsoft's side until the session ends — useful for 'what if' calculations that must not touch the real workbook.
Source: learn.microsoft.com ↗ checked 2026-09-28The connection reads only workbooks in the modern .xlsx format; old .xls files are not supported and have to be re-saved first. The workbook must live in OneDrive or SharePoint — a file on a manager's local disk or on a shared network folder is out of reach, so that is the first question we ask. Every operation opens a working session with the workbook; in the draft mode the changes are lost when the session expires, which is why we use it only for calculations and never for the payment log. Working without a session is possible but slow, so bulk imports are done in batches inside one session. Excel is a file, not a database: two people editing the same row at the same moment is resolved by the rule we agree during setup, not by Excel.
Three steps from a first message to work on your project.
Describe the task in the form — in text or by voice. Budget and timing are optional.
A developer studies the brief, asks about anything unclear and sends an estimate.
Once scope and price are agreed, the work begins.
or write to info@coreviaflow.space
Describe the task in text or a voice message. We look at your setup and reply with a plan.
Four services people come to us for most often. Each page explains what we do, how the work goes and where to start.
Choose the system, set up the pipeline, migrate data, train the team.
Learn more →Accounting, telephony, website, payments and messengers feed the CRM on their own.
Learn more →Orders, requests and answers around the clock, straight into your CRM.
Learn more →Flows between CRM, email, spreadsheets, payments and AI, on your own server.
Learn more →
Automation & workspaceUSThe spreadsheet your team already lives in: leads flow from a Google Sheet into your CRM, reports flow back into the sheet, and nobody copies rows by hand
See scenarios →
Automation & workspaceUSClient letters from Outlook land in the CRM deal card, meetings from the Outlook calendar appear in the CRM, and replies go out from the manager's own address.
See scenarios →
CRMUAUkrainian CRM that pulls orders from your site, marketplaces and chat apps into one pipeline
See scenarios →
CRMUADeals, calls and documents move through Bitrix24 on their own, tracked step by step
See scenarios →
Automation & workspaceUSZapier links your services without code: we set up the links, or replace them with our own code when there are too many steps
See scenarios →
Automation & workspaceEUVisual scenario builder: we build the links in your Make, plug in what it can't reach, and replace it with code when it gets crowded
See scenarios →Implementation · Development · Integrations →
Microsoft Excel is a trademark of its owner. CoreviaFlow is not affiliated with it unless stated otherwise. Screenshots are taken from public vendor materials; the source is shown under each one.
