Switching from Grid Mate
Install Rowhouse beside Grid Mate, rebuild the grids people use most, run both, and keep Grid Mate for the calendars, boards and charts that a grid was never meant to replace.
- You use the rest of the suite: Gantt, kanban, calendars, maps, the pivot grid or File Explorer. Rowhouse is a grid and nothing else, on purpose.
- You still run Salesforce Classic. Grid Mate documents a Classic path; Rowhouse runs in Lightning Experience and not in Classic.
- You put grids inside Flow screens with Grid Mate’s Flow View Grid and Flow Edit Grid. Rowhouse has no Flow screen component.
Where Grid Mate keeps your grids
Spread across your org: 31 packaged custom objects, custom metadata and custom settings in Grid Mate’s namespace, plus JSON pasted into Lightning App Builder properties on every page that carries a grid. The Admin Cockpit exports User Grids as JSON, but in Grid Mate’s own schema, which nothing else imports, so each grid is rebuilt.
Grid Mate’s concepts, in Rowhouse
| In Grid Mate | In Rowhouse |
|---|---|
| A User Grid, built in the configuration wizard | A Grid Configuration and its Grid Columns, built on the Grid Admin tab |
| A Related List Grid on a record page | A grid with a Record Page Field: an editable related list of that record’s children |
| The Filter property (admin JSON) | Grid Filters, shown to users as locked chips |
| Cell Coloring rules, with labels for the legend | Display rules — sixteen looks, explained in a Display Key |
| Group By and Aggregate properties | Grouping up to three levels, with subtotals and a Total row |
| Actions in JSON: a quick action, screen flow, autolaunched flow or Visualforce page | Grid Actions: a screen flow, an autolaunched flow, invocable Apex or a quick action. A Visualforce page has no equivalent |
| Record Related Components: child grids under each row | Child tables under each row, up to three levels, each a full grid |
What you rebuild
- Every User Grid, and every smart grid’s JSON in each page’s component properties: filters, aggregates, cell coloring, actions and related-record grids.
- Apex written against Grid Mate’s interfaces: Save Hooks and the data-grid, lookup, pasted-value and default-value providers. Each class is global in your own org, so decide what it did and remove it with care.
- Users’ saved and shared filters. Rowhouse keeps each user’s layout, but has no named, shared views, and a user’s column filters last for the visit.
What you lose, for now
- Flow screen componentComing soon
- Experience CloudComing soon
- The Admin Cockpit exports User Grids as JSON. Nothing imports it, but it is a ready list of the User Grids to rebuild.
- Grid Mate bills monthly at the annual rate, with no published term commitment, so there is no multi-year contract to wait out.
- Both are separate packages placed through Lightning App Builder, so a Grid Mate calendar and a Rowhouse grid can share a record page.
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 Grid Mate, 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 Grid Mate when its license comes up, not before.
Build the inventory from two places
Start by exporting the User Grids from the Admin Cockpit: that file lists every User Grid and its settings. The smart grids are not in it. A Related List, List View or FieldSet Grid keeps its behavior in its component’s properties on each page, so open every Lightning page that carries a Grid Mate grid and copy those properties into the same inventory. Then rebuild the grids people open every day, put each beside its Grid Mate version, and leave the calendars, boards and maps where they are.
Grid Mate facts checked 2026-10-07, from its vendor’s own published documentation.
Switching from Grid Mate: questions
Can I import the JSON from Grid Mate’s Admin Cockpit?
No. That export is in Grid Mate’s own schema and Rowhouse has no importer. Use it as a checklist, and rebuild each User Grid on Rowhouse’s Grid Admin tab, which checks every setting as you type.
Do I have to give up Grid Mate’s calendars and Gantt chart?
No. The two packages run side by side with separate configuration. Move the grids, and keep Grid Mate seats for the people who use its other components.
What happens to records edited in Grid Mate?
Nothing. Both grids edit the same Salesforce records in your org. Your data does not move; the grid configuration is what you rebuild.
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.