Fragile spreadsheets, moved into a real database.
Key business tools lived in Google Sheets and AppSheet. I moved them into a Postgres database behind the staff portal, with proper access control.
Languages
Tools & platforms
AI & LLM
Skills
The thinking behind it
- 01 · What I noticed
The tools worked, but the foundation didn't: shared sheets break when anyone edits them.
- 02 · What I decided
Move one tool at a time into real database tables with access by role, without stopping daily work.
- 03 · What I delivered
About five tools moved onto a database that holds up.
Old system vs new system
- Edit a shared sheet
- A formula breaks
- Find who changed it
- Fix it by hand
- Data in real tables
- Access by role
- Changes logged
- Tools rebuilt as modules
Watch it run
Click through the four steps. In step 3, click any box to see what it does.
Moving the foundation while people still stand on it.
The spreadsheet tools were in daily use, so they could not simply be switched off. Each tool was mapped to real tables and moved one at a time, with access by role from day one.
Why it's built this way
One tool at a time
Each move is small enough to check and roll back.
Access rules from day one
Every table protected by role, not by who has the link.
Rebuild as portal modules
Migrated tools land inside the staff platform, not as new islands.
What made it work
- 01
Map before you move
Understanding the old sheet saves weeks of surprises.
- 02
Small moves beat big launches
One tool at a time keeps daily work running.
- 03
Permissions are part of the data
Moving data without access rules just moves the risk.
Have a similar mess? Tell me the step you hate.