Switching from Conga Grid
Install Rowhouse beside Conga Grid, rebuild the grids people use most, run both, and let the Conga license lapse at renewal for the people who no longer need it.
- Your team launches Conga Composer or Conga Batch from grid rows. That integration is the product, and Rowhouse has no equivalent.
- The reading pane is load-bearing: record detail, Chatter, charts and related lists beside the grid.
- You need grid graphs, the approval center or drill up and drill down.
Where Conga Grid keeps your grids
As records on sixteen packaged custom objects — views, conditional formatting, formula columns, custom actions, reading-pane layouts — plus a generated Visualforce page for each grid tab, wired into your page layouts, tabs, list-view buttons and search layouts. None of it is Salesforce metadata, so none of it carries across: each grid is rebuilt.
Conga Grid’s concepts, in Rowhouse
| In Conga Grid | In Rowhouse |
|---|---|
| A view (object, columns, filters, sort) | A Grid Configuration and its Grid Columns |
| Conditional formatting | Display rules — sixteen looks, explained in a Display Key |
| Formula columns | Formula columns in Salesforce’s own formula syntax, up to ten per grid |
| Filters set by the admin | Grid Filters, shown to users as locked chips |
| Custom actions and batch actions | Grid Actions: a screen flow, an autolaunched flow, invocable Apex or a quick action |
| Parent fields edited from a child grid | A related record’s field as a column, such as Account.Industry, edited in place |
| Related lists in the reading pane | Child tables under each row, up to three levels, each a full grid |
| A grid tab (generated Visualforce page) | The Rowhouse grid component on an App, Record or Home page |
What you rebuild
- Every saved view, with its filters, Boolean filter logic, formatting rules and formula columns.
- Every page layout, tab, list-view button and search layout that points at a generated Conga Grid page.
- Who may do what: Conga’s feature-security matrix of about sixty features becomes Rowhouse’s three permission sets plus each grid’s own switches for editing, import, export, delete and logging.
What you lose, for now
- Experience Cloud (Conga Grid offers part of it)Coming soon
- Conga Grid’s ten-user minimum makes coexistence cheap: keep the minimum for the people who need the reading pane and Composer, and move everyone else.
- 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 Conga Grid, 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 Conga Grid when its license comes up, not before.
Start with the grids people use most
Most orgs have a few Conga Grid views that everyone opens every day and a long tail nobody remembers building. Rebuild the daily ones first, put each beside the Conga version on the same page, and ask the people who use it to try both for a week. Whatever nobody misses after a month does not need rebuilding at all.
Conga Grid facts checked 2026-10-07, from its vendor’s own published documentation.
Switching from Conga Grid: questions
Can I import my Conga Grid views into Rowhouse?
No. Conga keeps views as records in its own objects, in its own format, and there is no importer. Each grid is rebuilt on Rowhouse’s Grid Admin tab, which checks every setting as you type.
Do I have to uninstall Conga Grid first?
No. The two run side by side with separate configuration. Remove Conga Grid when its license comes up for renewal, once the people who used it have switched.
What happens to records edited in Conga Grid?
Nothing. Both grids edit the same Salesforce records through the same object, field and sharing security. Only the grid configuration has to be rebuilt; your data does not move.
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.