Migrate Spreadsheets

From spreadsheets and email to apps on live data.

Many processes run on a spreadsheet and an email thread: a request in a workbook, a chain of replies, a final version typed into the ERP.

SPREADSHEET-AND-EMAIL PROCESSESSMARTAPPSAn extract pasted into a tabA data handler on the ERP object, read in placeA tab of calculationsA query handler or expressions on a screenThe grid people editA grid component with inline edit and validationAn email asking for approvalA level in an approval flow, with a clock and an alternateA reply with a decisionA logged step with the values shown and enteredTyping the result into the ERPA write-back through the released interface, acknowledgedVersion 14 of the workbookVersions of the app, and one instance per case
What each element of spreadsheet-and-email processes becomes in SmartApps.
7
elements mapped
this page
4
catalogue apps most often built on this path
catalogue
1 week
for the inventory
offer
10
apps in the first fixed-price conversion
offer
What you have

The typical inventory

ElementWhat it holds
Master workbooksone per process, with tabs per site or month
ExtractsERP downloads pasted in weekly
Formulas and macrosthe logic, often with links to other workbooks
Email threadsthe approvals and the escalations
Shared drives and attachmentsthe versions
Re-keyingthe final entry into the ERP by hand
What each becomes

The mapping, element by element

In spreadsheet-and-email processesIn SmartApps
An extract pasted into a tabA data handler on the ERP object, read in place
A tab of calculationsA query handler or expressions on a screen
The grid people editA grid component with inline edit and validation
An email asking for approvalA level in an approval flow, with a clock and an alternate
A reply with a decisionA logged step with the values shown and entered
Typing the result into the ERPA write-back through the released interface, acknowledged
Version 14 of the workbookVersions of the app, and one instance per case
Context

Spreadsheets stay for analysis; the move is for the processes that need an owner, a clock and a record.

The path

Five steps

InventoryOne week; every element above listed with its owner and its last change.
A move

Illustrative

A consumer-goods company ran its excess stock review on a 40-tab workbook refreshed on Mondays and 200 emails a month. The excess and obsolete inventory review app read the stock positions and the last movements live, opened one instance per position above 12 months of cover, and gave planners a grid they recognised. The Monday refresh disappeared, the reserve calculation ran from the same rows, and the controller's sign-off was one screen.

illustrative · figures for the shape of a typical move
Apps most often built on this path

Questions

What if an application has logic worth keeping?

It becomes a registered function the app's actions call by name, with its inputs and outputs logged.

Who owns the new apps?

The process owner, with the configurator role; the application team keeps the gates and the write-back switches.

What does it cost?

The inventory is fixed-scope; the first ten apps carry a fixed price written before the work; the platform is priced by capacity with apps included.

Start with a one-week inventory

We list the applications, the forms and the workflows you run today, group them by the app type they become, and write a fixed price for the first ten before any work begins.