Switching from Mashmatrix Sheet
Move any in-sheet data into real Salesforce fields, install Rowhouse beside Mashmatrix Sheet, rebuild the sheets people open every day, run both, and keep Mashmatrix seats for the people who load data for a living.
- You want the product and its documentation in Japanese. Mashmatrix has both; Rowhouse is in English, with no translation.
- Loading data by key is the main job: pasting from Excel into upsert mode, matched on any unique field, such as an email address. Rowhouse imports files too, but matches by record Id or an External Id, up to 10,000 rows at a time.
- People rely on its discontiguous paste: Ctrl-click several separate ranges and paste into all of them at once. A Rowhouse range is one rectangle.
- Forecasts or project effort are entered across columns in its time-series matrix. Rowhouse has nothing like it.
Where Mashmatrix Sheet keeps your grids
Books, sheets, views, columns, formats, action buttons and formulas are records in sixteen packaged custom objects, with no documented export. In-sheet data columns and scratch data sheets hold values with no Salesforce field behind them: move them into real fields before you uninstall, or they go with the package.
Mashmatrix Sheet’s concepts, in Rowhouse
| In Mashmatrix Sheet | In Rowhouse |
|---|---|
| A Sheet: a list over one object | A Grid Configuration and its Grid Columns |
| A Book of sheets, shared through folders | Separate grids, each placed with the Rowhouse grid component on an App, Record or Home page |
| Related Sheets in a split screen | Child tables under each row, up to three levels, linked by a lookup or master-detail field |
| Conditional styling and format settings | Display rules — sixteen looks, explained in a Display Key |
| The summary row | A Subtotal on a column and a Total row, worked out over every matching record |
| Action buttons that launch a Flow, Apex or a Visualforce page | Grid Actions: a screen flow, an autolaunched flow, invocable Apex or a quick action |
| Upsert mode | Import from CSV or Excel, matching by record Id or an External Id, with a preview and Undo import |
What you rebuild
- In-sheet data columns and scratch data sheets, before anything else. Create the Salesforce fields they need, move the values into them, and check the result while Mashmatrix is still installed.
- Every book and sheet, by hand, with no export to work from: columns, formats, action buttons, formulas and views.
- Any relationship that exists only as a custom related sheet or a Union Sheet. A Rowhouse child table follows a lookup or master-detail field, so a join on matching values needs a real relationship first.
- The access layer: MsmxPerm_ custom permissions, object-level access control and folder sharing become Rowhouse’s three permission sets plus each grid’s own switches for editing, import, export, delete and logging.
What you lose, for now
- Flow screen componentComing soon
- Experience CloudComing soon
- AI featuresComing soon
- Mashmatrix accepts license reductions at renewal, so finish moving people before your renewal date and reduce the count then.
- Keep licensed seats for the people who load data by key every day, and move the people who review and correct a list now and then.
- Rowhouse grids are metadata, so you can rebuild once in a sandbox and deploy to production in a change set.
The Grid Admin tab
Every grid in the org, on one page
Rebuilt grids appear here with their object and columns, counted by object, ready to edit, clone or archive.
One editor for each grid
Columns, display rules, filters, actions and child tables on six tabs, checked as you type with the same code the grid uses.
Seven steps, and nothing removed until step seven
Inventory
List every grid built in Mashmatrix Sheet, who uses it and which page it sits on.
Install alongside
Rowhouse installs next to the grid you have. Nothing is removed, and nobody loses a grid while you work.
Rebuild each grid
On the Grid Admin tab, one grid at a time, mapping each concept as the table above shows.
Test, then deploy
Build in a sandbox and move the grids to production in a change set, because they are metadata.
Run both
Put the Rowhouse grid beside the old one until the people who use it are sure.
Re-point pages
Swap the old component for the Rowhouse grid on each Lightning page.
Remove at renewal
Uninstall Mashmatrix Sheet when its license comes up, not before.
Move the in-sheet data first
Before you rebuild a single sheet, find every in-sheet data column and scratch data sheet, and ask who relies on what they hold. Those values are stored in Mashmatrix’s objects, not on your records, so they leave with the package. Create the fields they need on the real objects, move the values across, and check them while both products are installed. Then rebuild the sheets people open every day, beginning with the ones that need no new relationship in your data model.
Mashmatrix Sheet facts checked 2026-10-07, from its vendor’s own published documentation.
Switching from Mashmatrix Sheet: questions
Will I lose data when I uninstall Mashmatrix Sheet?
You can. Values in in-sheet data columns and scratch data sheets live in Mashmatrix’s own objects, with no Salesforce field behind them, so they go with the package. Create real fields and move those values before you uninstall.
Can I export my books and sheets into Rowhouse?
No. Mashmatrix documents no export of its configuration, and Rowhouse has no importer. Each sheet is rebuilt as a grid on Rowhouse’s Grid Admin tab, which checks every setting as you type.
Can our data team keep Mashmatrix Sheet while everyone else moves?
Yes. The two are separate packages with separate configuration, and both edit the same Salesforce records. Keep Mashmatrix seats for the people who load data by key, and move the rest.
Three things you can verify without asking us
Install it alongside. Nothing to remove until you are sure.
Rebuild one grid, run both, and switch when the new one has earned it.