How to Migrate an AppSheet App to NocoBase in One Session — Without Losing Your Google Sheets Data
by BAMFLOW • • 4 min read
Migrate an AppSheet app to NocoBase in one session: export your Google Sheets data, rebuild the data model and screens, run both in parallel, lose nothing.
How to Migrate an AppSheet App to NocoBase in One Session — Without Losing Your Google Sheets Data
Quick summary: Migrating from AppSheet to NocoBase does not mean rebuilding your app from scratch. Your data already lives in Google Sheets, and it exports intact. One focused session is enough to clean and export the data, rebuild the data model in NocoBase, recreate the screens and formulas, and then run both systems in parallel for a few days before switching for good.
Here is the good news most businesses miss: with AppSheet, the valuable part — your data — is not locked inside AppSheet. It sits in your own Google Sheets files. AppSheet is only the interface and logic layer on top. When you move to NocoBase, you carry all the "furniture" (the data) with you and only rebuild the "frame" (screens, formulas, permissions). And because NocoBase is stronger on role-based permissions, multi-level approvals and charges nothing per user, the new frame is usually better than the old one. New to the platform? Start with What is NocoBase, and see the head-to-head AppSheet vs NocoBase comparison for the full picture.
Step 1: Clean and export your Google Sheets data
Years of AppSheet use leave behind unused columns, duplicate records and "temporary" notes columns that quietly became real data. Migration is the best excuse to clean house once:
- List the sheets you actually need — each one becomes a table. Skip report/summary sheets; you will rebuild them as charts.
- Give every table a stable ID column (customer code, order code). If the old app relied on row numbers, add real codes now — this prevents most relationship errors later.
- Normalize formats: one date format, plain numbers for money, one agreed set of status values.
- Export each sheet as its own CSV/XLSX file, and keep the original Sheets file untouched as your backup and reconciliation source.
Step 2: Rebuild the data model — tables, fields, relationships
This is the biggest mindset shift. AppSheet lets you draw the app first; NocoBase asks you to design the data model first: tables, correctly typed fields, and relationships — one Customer has many Orders (1-to-many), one Order has many line items, each line item belongs to one Product.
Create the tables, import in parent-to-child order (Customers and Products first, then Orders, then line items), and verify with three numbers: record counts per table, total order value per month, and the count of orphaned line items. If all three match the source, your data has landed correctly. AI assistance now makes this step much lighter — but the principle stands: get the model right and everything after it is easy.
Step 3: Recreate screens and money formulas
Screens in NocoBase are blocks placed on top of your tables: a Table block for lists, a Form for data entry, Details for a single record. The same Orders table can serve sales staff as a list, coordinators as a drag-and-drop Kanban by status, and the director as a revenue chart — no separate apps needed.
Formulas need honest attention, because AppSheet expressions do not run on NocoBase:
- Same-row calculations (amount = quantity × price, discounts, VAT): rebuild them as formula fields — different syntax, same logic. Verify against a few sample rows.
- Cross-table lookups: mostly disappear, because relationships now do that work for you.
- Event logic (deduct stock on order creation, notify accounting after approval): becomes NocoBase Workflows — usually the biggest upgrade of the whole migration, since multi-level approval is where AppSheet struggles most.
Step 4: Run both in parallel for 3 days before switching
The most expensive mistake is turning off the old app the moment the new one "seems to work". Run both in parallel for three working days: staff keep working in the old app, and each evening you sync the day's new data into NocoBase and reconcile order counts, totals and closing stock. Three matching days in a row means the new system is trustworthy. On day four, move everyone over and keep the old app read-only for two more weeks as a fallback.
Watch out for the classic pitfalls: copying the giant all-in-one spreadsheet structure into the new system instead of splitting it into proper tables, forgetting hidden "config" sheets with price lists, reconciling "by eye" instead of by numbers, and scheduling the cut-over at peak hours instead of end of day.
About BAMFLOW — BAMFLOW is the official NocoBase partner in Vietnam, specializing in AppSheet, NocoBase and AI implementation and training for businesses (300+ apps, 150+ business clients, 1000+ learners).
- Want to build your own system? Register for the NocoBase AI Builder course (12 sessions) and learn to build real systems on your own data.
- Want it implemented for you? Message BAMFLOW via bamflow.vn for advice tailored to your workflows.