"Finance_FINAL.xlsx", "Finance copy.xlsx", a draft nobody approved. gridmap replaces the pile with one governed registry, with version history and access control.
When a report or pipeline reads from a mapping file, one wrong cell can spread to every report that uses it. Changes should be validated and tracked automatically.
"Budget_Codes_FINAL_v3_UPDATED.xlsx". When reference data lives in several places, finding the latest version takes more effort than it should.
Shared folders make it hard to control who can edit what. A purpose-built system gives you granular access and an audit trail from the start.
When something looks off, seeing exactly what changed, when and by whom turns a long hunt into a quick check.
Typed columns (text, numbers, dates, true/false, dropdowns) and required fields, so a date column only holds dates.
Upload CSV or Excel directly. Primary-key upsert merges updates without creating duplicates.
Every change is tracked: who, when, and the previous value. Deleted rows can be restored until an admin removes them for good.
Finance sees finance codes, operations sees operations codes, enforced automatically.
Connect to Snowflake, SQL Server, BigQuery or another supported database, and keep reference data in sync on a schedule.
Your BI tools, ETL pipelines and applications read the current mappings over a REST API.
No more "FINAL_v3". There is one registry, and it is the source of truth.
Bring your existing spreadsheets in as they are, then govern them from there.
Your data is never locked in: export to Excel or read it from the API.
Consider the time your team spends today: searching shared drives for the right file, checking hardcoded values in SQL, restarting reports that failed on a mapping issue, or tracing a wrong number back through sheets, rows and cells. Even a few hours a month adds up fast. Structured data, automatic version tracking and clear access control give that time back from day one.
Excel works for personal analysis, but breaks down as a shared, governed registry. There is no change history, access control stops at who has the file, there is no API for downstream systems, and one bad edit can break every report that depends on it. gridmap keeps the familiar table and adds typed columns, version history, access control and an API.
Yes. Upload CSV or Excel files directly into gridmap. Rows are matched on the primary key, so updates merge into existing rows instead of creating duplicates.
Every change to a registry row is tracked automatically: who made the change, when, and what the previous value was. You can view the full history of any row and restore an earlier version. Deleted rows are kept and can be restored, unless an admin deletes them permanently.
Deleting a row is a soft delete: the row is marked as deleted but kept, and can be restored from the "Show deleted" filter. Only an admin can delete rows permanently, which also removes their history. The audit log shows who deleted a row and when.
Row-level security lets you restrict which rows each user or group can see and edit within the same registry. Finance sees finance cost center codes, operations sees product codes. Access is enforced automatically, so there are no separate files or tabs to fall out of sync.
No. gridmap works alongside your data warehouse. It connects to PostgreSQL, SQL Server, Snowflake, BigQuery and Microsoft Fabric to read source values and pick up changes. Mappings and reference data are served over a REST API to your BI tools, ETL pipelines and applications.
One file is one import: upload it, match the columns, and the rows are in a registry with version history from then on. Larger migrations with many files can be done one file at a time. Registries are included from the Basic plan; contact us and we will set you up.
gridmap is live. Ask for a free license that never expires, or talk to us about a plan with registries.