EspoCRM had no office editor. Now it has ours.

Neither of the usual office servers ships an EspoCRM connector — we looked. So we wrote one: an extension that makes EspoCRM itself a WOPI host and hands the file to SumSheet or SumDoc. The workbook attached to an account or an opportunity opens, is edited in the browser and comes back with its macros. Measured on EspoCRM 9.2.4.

What the extension does

Where you click	A button on the file of a Document record — where your people already keep the price list and the calculation.
What it adds	WOPI routes inside EspoCRM, signed access tokens, and signature verification on every request.
Measured	A macro workbook and a document with five pictures: opened, edited, saved back. VBA byte for byte, five pictures byte for byte, the edit in place.
What this does not say	The round used a fixture workbook from our corpus that asks Microsoft Excel to repair it on its own, before any round. No silent-Excel claim here; see Nextcloud and Seafile, measured on real workbooks.

Setting it up

# the editors, behind your TLS address
git clone https://github.com/SumOfficeApp/sumoffice-docker && cd sumoffice-docker/nextcloud
cp env.example .env    # PUBLIC_URL=https://office.example.com
docker compose up -d

# the extension: sumoffice-docker, branch integrations, folder integrations/espocrm
# install it in EspoCRM, then set the editor address in its settings

Evaluation is free with no time limit; production is the per-application license. The other systems we measured →

Then

Check my Excel file — what your workbooks rely on, in seconds.
Tell us your EspoCRM version — 9.2 is measured.