[{"data":1,"prerenderedAt":237},["ShallowReactive",2],{"seo-verification":3,"blog-migrate-undb-to-teable-vps-en":6},{"google":4,"bing":5},"EycwPY2XMyTkVzas3n1ygeNJFGAH513qrMjfDljzsMQ","",{"key":7,"data":8},"blog-migrate-undb-to-teable-vps-en",{"id":9,"slug":10,"slugs":11,"title":15,"excerpt":16,"readTime":17,"views":18,"isPinned":19,"publishedAt":20,"updatedAt":21,"category":22,"categories":28,"featuredImage":30,"bgImage":31,"posterImage":32,"relatedSolution":33,"intro":36,"sections":37,"ctaTitle":155,"ctaBody":156,"ctaButton":157,"ctaUrl":158,"relatedPosts":159},402,"migrate-undb-to-teable-vps",{"fr":12,"en":10,"ar":13,"es":14},"migrer-undb-vers-teable-vps","undb-teable-vps","migrar-undb-a-teable-vps","Migrating from undb to Teable on a ServOrbit VPS","Migrate from undb to Teable on a VPS: Rust-powered NoCode database, Airtable-compatible API, full Docker Compose guide and data import steps.",11,0,false,"2026-10-01T00:00:00+00:00","2026-10-02T14:03:19+00:00",{"id":23,"name":24,"slug":25,"color":26,"icon":27},6,"Databases","bases-de-donnees","bg-teal-500\u002F10 text-teal-400","database",[29],{"id":23,"name":24,"slug":25,"color":26,"icon":27},null,"\u002Fblog\u002Fcovers\u002Fbg.svg","\u002Fblog\u002Fcovers\u002Fmigrer-undb-vers-teable-vps-poster.svg",{"categorySlug":34,"appSlug":35},"databases","teable","NoCode databases have changed how technical teams manage data without writing raw SQL. undb was one of the first serious open source tools in this space: clean interface, simple Docker deployment, permissive license. For two years it held its ground.\n\nBy late 2025, the signals shifted. The GitHub repository had not seen a new release in over sixty days. Issues were piling up — import bugs, crashes on larger datasets, incompatibilities with recent Node.js versions — without any maintainer response. Community pull requests sat without review. This is not yet formally abandoned, but a JavaScript project that stops moving eventually breaks.\n\nTeable emerged as the natural alternative: a NoCode database written in Rust, AGPL-3.0 licensed, with documented Airtable-compatible API, over 12,000 GitHub stars by autumn 2026, and a consistent release cadence. Its Rust architecture gives it a significantly lower memory footprint than undb for equivalent workloads — relevant on an entry-level VPS.\n\nThis guide covers the complete migration: exporting from undb, installing Teable on a ServOrbit VPS via Docker Compose, importing your data, and verifying integrity. The procedure is tested on a 1 vCPU \u002F 2 GB RAM VPS — the ServOrbit entry-level plan at €3.99\u002Fmonth is sufficient for a team of fewer than ten people.",[38,42,52,55,90,93,109,112,133,136,151],{"type":39,"title":40,"body":41},"h2","The problem with undb in 2025–2026","An open source project is not condemned simply because it slows down. Some reach stable maturity and no longer need much change. undb does not fit that profile: it is a young tool in a fast-moving category, with short-lived JavaScript dependencies.\n\nThe warning signs that accumulated by late 2025 are specific. The last published tag was more than sixty days old by year end. The number of open issues without a maintainer comment exceeded thirty. Several reported regressions on core features — formulas, filtered views, CSV import — without acknowledgment. The last npm dependency update was months old, leaving known CVEs unpatched in the dependency chain.\n\nThe concern is not only technical. A database tool holds operational data. When maintenance weakens, the question shifts from 'does it work today' to 'will it work in six months, and will my data be accessible if it does not.' With undb in its current state, that answer is uncertain.",{"type":43,"title":44,"items":45},"ul","Why migrate now rather than in six months",[46,47,48,49,50,51],"Active security risk: unmaintained npm dependencies accumulate known CVEs; an undb instance exposed to the internet without a hardened reverse proxy is an expanding attack surface.","Unpatched production bugs: regressions in CSV import and formulas reported in late 2025 have no fix; if your usage touches these features, the situation only worsens.","Frozen dependencies: Node.js LTS advances, Docker base images change; a project without maintenance eventually fails to build, blocking host security updates.","Community moving on: discussions in self-hosted forums (Reddit r\u002Fselfhosted, awesome-selfhosted) show a clear migration trend toward Teable, NocoDB, and Grist; staying on undb means losing access to active integrations and community scripts.","Orphaned data: the longer you wait, the higher the probability of an undocumented internal schema change; exporting now, while the output format is known and stable, is safer than waiting for a future incompatibility.","A clean migration window: your data is fresh and consistent now; a forced migration — because the instance fails to start after a Docker update — always happens under worse conditions.",{"type":39,"title":53,"body":54},"Teable: the actively maintained Rust NoCode database","Teable positions itself as a self-hosted Airtable alternative, but the technical positioning is more precise. The backend is written in Rust with NestJS for the API layer, and the frontend is a React application. This yields a backend binary consuming roughly 150–200 MB of RAM at idle, compared to 400–600 MB for undb on a comparable instance.\n\nThe REST API is documented and designed to be compatible with Airtable patterns: same core concepts (tables, views, fields, records), same HTTP verbs, similar JSON structures. If you have scripts that queried undb via its API, adapting them to Teable amounts to a handful of route and field name adjustments.\n\nThe AGPL-3.0 license restricts redistribution of modified Teable builds, but imposes no restrictions on internal use or deploying Teable for your own clients on your own infrastructure — the standard regime for serious self-hosted tools.\n\nThe release cadence is the most important factor for a production tool: weekly to biweekly releases with detailed changelogs, critical bugs addressed within 72 hours, and a public roadmap that is kept current. This is the level of maintenance expected of a tool trusted with operational data.",{"type":56,"title":57,"headers":58,"rows":62},"comparison","undb vs Teable: technical comparison",[59,60,61],"Criterion","undb","Teable",[63,67,70,74,78,82,86],[64,65,66],"Backend language","TypeScript (Node.js)","Rust + NestJS",[68,69,69],"License","AGPL-3.0",[71,72,73],"RAM at idle (Docker)","~400–600 MB","~150–200 MB",[75,76,77],"Airtable-compatible API","Partial, undocumented","Yes, documented",[79,80,81],"CSV\u002FJSON import","Yes (regressions reported late 2025)","Yes, stable",[83,84,85],"GitHub stars (autumn 2026)","~3,500","~12,000+",[87,88,89],"Maintenance activity","Stalled (>60 days without release, late 2025)","Active (weekly releases)",{"type":39,"title":91,"body":92},"Preparing the migration: exporting from undb","Before installing anything, export your undb data from a still-functioning instance. Do not defer this until after Teable is installed: if something goes wrong between the two steps, you want your data already in hand.",{"type":94,"title":95,"steps":96},"steps","Exporting your data from undb",[97,100,103,106],{"title":98,"body":99},"Access the export interface","In undb, open each table you want to migrate. The table context menu (the '…' icon or right-click on the tab) exposes an 'Export' option. undb offers two formats: CSV and JSON. Choose JSON for tables with relation or formula fields — CSV flattens relations into strings, complicating remapping. For simple tables (no relations), CSV is sufficient.",{"title":101,"body":102},"Export table by table","undb does not offer a global database export at this version. Each table must be exported separately. Organize your files in a folder named after the database: for example `export-undb-crm\u002F` or `export-undb-projects\u002F`. Note the import order for later: tables referenced by others must be imported into Teable first.",{"title":104,"body":105},"Verify export integrity","For each exported JSON file, verify it is not truncated: open it in an editor or run `python3 -m json.tool my-export.json > \u002Fdev\u002Fnull` — no output means valid JSON. For CSV files, count lines with `wc -l export.csv` and compare against the record count displayed in undb. A discrepancy of more than a few lines (headers, trailing blank line) warrants investigation before proceeding.",{"title":107,"body":108},"Keep an archive copy","Before continuing, archive everything: `tar czf undb-export-$(date +%Y%m%d).tar.gz export-undb-*\u002F`. Keep this archive for thirty days after the migration. If Teable reveals a data inconsistency two weeks after import, the original undb export is your ground truth.",{"type":39,"title":110,"body":111},"Installing Teable on a ServOrbit VPS","ServOrbit offers a Teable template in its marketplace at `\u002Fmarketplace\u002Fbases-de-donnees\u002Fteable`. The template automatically configures Docker Compose, base environment variables, and the reverse proxy. For a fully manual install that keeps you in control, the steps below cover the complete procedure on Debian 12 or Ubuntu 22.04.",{"type":94,"title":113,"steps":114},"Install Teable via Docker Compose",[115,118,121,124,127,130],{"title":116,"body":117},"Create the working directory","Connect via SSH to your VPS. Create a dedicated directory and navigate into it:\n```\nmkdir -p \u002Fopt\u002Fteable && cd \u002Fopt\u002Fteable\n```\nDownload the official Compose file from the Teable repository:\n```\ncurl -O https:\u002F\u002Fraw.githubusercontent.com\u002Fteableio\u002Fteable\u002Fmain\u002Fdockers\u002Fdocker-compose.yml\n```",{"title":119,"body":120},"Configure environment variables","Create a `.env` file in `\u002Fopt\u002Fteable\u002F`. The minimum required variables are:\n```\nPOSTGRES_PASSWORD=change-me-strong\nTEABLE_SECRET_KEY=a-random-32-character-string\nPUBLIC_ORIGIN=https:\u002F\u002Fteable.your-domain.tld\n```\nGenerate the secret key with `openssl rand -hex 16`. Do not reuse the PostgreSQL password from another instance.",{"title":122,"body":123},"Start the services","Start the stack in the background:\n```\ndocker compose up -d\n```\nWait thirty seconds, then verify all containers are `healthy`:\n```\ndocker compose ps\n```\nThe `teable` service must show `healthy`. If `teable-db` is not ready yet, wait a few more seconds — PostgreSQL takes longer on the first start (schema initialization).",{"title":125,"body":126},"Configure the reverse proxy","Teable listens on port 3000 by default. Configure your reverse proxy (nginx or Caddy) to route HTTPS traffic to `localhost:3000`. Minimal nginx example:\n```\nserver {\n    listen 443 ssl;\n    server_name teable.your-domain.tld;\n    location \u002F {\n        proxy_pass http:\u002F\u002F127.0.0.1:3000;\n        proxy_set_header Host $host;\n        proxy_set_header X-Real-IP $remote_addr;\n    }\n}\n```\nIf using the ServOrbit template, this configuration is generated automatically.",{"title":128,"body":129},"First access and admin account creation","Open `https:\u002F\u002Fteable.your-domain.tld` in a browser. On first login, Teable prompts you to create an admin account. This account is local to your instance — there is no external registration. Choose a strong password and store it in your secrets manager.",{"title":131,"body":132},"Create a workspace","After login, create a workspace (equivalent to an organization in Airtable) that will hold your bases migrated from undb. Give it a descriptive name — `undb Migration` for example — to distinguish imported data from new bases you will create directly in Teable.",{"type":39,"title":134,"body":135},"Importing your undb data into Teable","Teable offers two import paths: CSV for simple tables, and structured JSON for tables with complex field types. The import interface is accessible from the '+' menu of a workspace or from the 'Import table' button inside an existing base.",{"type":94,"title":137,"steps":138},"Import and verify your data",[139,142,145,148],{"title":140,"body":141},"Create the target base in Teable","In your workspace, click 'New base' and give it the same name as the original database in undb. This naming consistency makes cross-verification easier during migration. If you are migrating multiple databases, process them one at a time.",{"title":143,"body":144},"Import tables from CSV or JSON","Inside the target base, click '+ Add table' then 'Import from file'. Select your CSV or JSON export. For CSV, Teable auto-detects column types — verify that date columns are interpreted as `Date` rather than `Text`. For JSON, the mapping is more direct if the undb export format is standard.\n\nImport tables without relations first (the leaf tables in your data graph), then those that reference them.",{"title":146,"body":147},"Map and adjust field types","After import, review each column in Teable and verify its type. Common issues when migrating from undb:\n- undb `formula` fields have no direct import equivalent — they arrive as frozen computed values. Recreate formulas in Teable manually.\n- `attachment` fields do not migrate via CSV; if undb stored files, handle them separately.\n- Boolean fields exported as the string `true`\u002F`false` need to be converted to `Checkbox` type in Teable.",{"title":149,"body":150},"Verify relationships and data integrity","If your undb tables had relationships (link-type fields), these arrive flattened in the CSV export. Recreate link fields in Teable once all tables are imported, then use the filter view to verify that record counts match the originals. A persistent discrepancy indicates an encoding issue in the export (special characters, Windows line endings) — re-export using JSON in that case.",{"type":152,"title":153,"body":154},"tip","Test on a non-critical database first","Before migrating your production data, run the complete procedure on a secondary database — test data, an archived project, or an anonymized copy. This surfaces field type mapping issues and edge cases specific to your usage without risking operational data integrity.\n\nKeep the undb export archive for at least thirty days after migration. If a data inconsistency surfaces two weeks after import — a missing field, a corrupted value — the original export is your only source of truth. Once that period has passed and the migration is fully validated, you can shut down the undb instance with confidence.","Deploy Teable on ServOrbit in minutes","The ServOrbit Teable marketplace template automatically configures Docker Compose, PostgreSQL, the reverse proxy, and TLS certificate. Entry-level VPS at €3.99\u002Fmonth, sufficient for a team of fewer than ten people. Your data stays on your infrastructure.","Install Teable on ServOrbit","\u002Fmarketplace\u002Fdatabases\u002Fteable",[160,182,202,220],{"id":161,"slug":162,"slugs":163,"title":167,"excerpt":168,"readTime":169,"views":18,"isPinned":19,"publishedAt":170,"updatedAt":171,"category":172,"categories":178,"featuredImage":30,"bgImage":31,"posterImage":180,"relatedSolution":181},397,"self-host-teable-airtable-alternative-vps",{"fr":164,"en":162,"ar":165,"es":166},"self-host-teable-vps","استضافة-teable-على-vps-بديل-airtable-مفتوح-المصدر","autoalojar-teable-en-vps-alternativa-airtable-codigo-abierto","Self-Host Teable: Open-Source Airtable Alternative on a VPS","Deploy Teable on your ServOrbit VPS: an open-source Airtable alternative with grid, kanban, gallery views and a REST API. Your data, your server. AGPL-3.0.",4,"2026-09-30T00:00:00+00:00","2026-09-30T11:20:31+00:00",{"id":173,"name":174,"slug":175,"color":176,"icon":177},7,"Self-hosting","self-hosting","bg-indigo-500\u002F10 text-indigo-400","cloud",[179],{"id":173,"name":174,"slug":175,"color":176,"icon":177},"\u002Fblog\u002Fcovers\u002Fself-host-teable-vps-poster.svg",{"categorySlug":34,"appSlug":35},{"id":183,"slug":184,"slugs":185,"title":189,"excerpt":190,"readTime":191,"views":18,"isPinned":19,"publishedAt":192,"updatedAt":193,"category":194,"categories":199,"featuredImage":30,"bgImage":31,"posterImage":201,"relatedSolution":30},336,"migrating-from-airtable-to-nocodb-or-grist-on-a-vps",{"fr":186,"en":184,"ar":187,"es":188},"migrer-airtable-vers-nocodb-grist-vps","الانتقال-من-airtable-إلى-nocodb-أو-grist-على-خادم-vps","migrar-de-airtable-a-nocodb-o-grist-en-un-vps","Migrating from Airtable to NocoDB or Grist on a VPS","Bending Spoons acquires Airtable for $1.28B (August 4, 2026). Full guide to migrate your bases to self-hosted NocoDB or Grist on a VPS.",8,"2026-09-07T00:00:00+00:00","2026-09-21T15:22:04+00:00",{"id":195,"name":196,"slug":197,"color":198,"icon":197},5,"Comparison","comparatif","bg-info\u002F10 text-info",[200],{"id":195,"name":196,"slug":197,"color":198,"icon":197},"\u002Fblog\u002Fcovers\u002Fmigrer-airtable-vers-nocodb-grist-vps-poster.svg",{"id":203,"slug":204,"slugs":205,"title":209,"excerpt":210,"readTime":211,"views":18,"isPinned":19,"publishedAt":212,"updatedAt":213,"category":214,"categories":215,"featuredImage":30,"bgImage":31,"posterImage":217,"relatedSolution":218},157,"how-to-self-host-nocodb-on-a-vps",{"fr":206,"en":204,"ar":207,"es":208},"self-host-nocodb-vps","كيفية-استضافة-nocodb-ذاتيا-على-خادم-vps","como-autoalojar-nocodb-en-un-vps","How to Self-Host NocoDB on a VPS","Deploy NocoDB on your VPS for a self-hosted, open-source Airtable alternative. Turn any database into a smart spreadsheet with REST and GraphQL APIs, via Docker Compose.",3,"2026-01-20T00:00:00+00:00","2026-09-07T11:26:10+00:00",{"id":173,"name":174,"slug":175,"color":176,"icon":177},[216],{"id":173,"name":174,"slug":175,"color":176,"icon":177},"\u002Fblog\u002Fcovers\u002Fself-host-nocodb-vps-poster.svg",{"categorySlug":34,"appSlug":219},"nocodb",{"id":221,"slug":222,"slugs":223,"title":227,"excerpt":228,"readTime":169,"views":18,"isPinned":19,"publishedAt":229,"updatedAt":230,"category":231,"categories":232,"featuredImage":30,"bgImage":31,"posterImage":234,"relatedSolution":235},56,"postgresql-on-a-vps-a-reliable-and-controlled-database",{"fr":224,"en":222,"ar":225,"es":226},"heberger-postgresql-vps","postgresql-على-خادم-vps-قاعدة-بيانات-موثوقة-ومتحكم-بها","alojar-postgresql-en-un-vps","PostgreSQL on a VPS: a reliable and controlled database","Host PostgreSQL on a VPS: volumes, backups, restricted network access and sound configuration for your applications.","2026-04-25T00:00:00+00:00","2026-09-08T22:00:02+00:00",{"id":23,"name":24,"slug":25,"color":26,"icon":27},[233],{"id":23,"name":24,"slug":25,"color":26,"icon":27},"\u002Fblog\u002Fcovers\u002Fheberger-postgresql-vps-poster.svg",{"categorySlug":34,"appSlug":236},"postgresql-stack",1790987773170]