Migration
Move your shop into Thoma without a re-keying marathon.
Most prospects come to us from shared drives, Excel BOMs, or a creaking legacy PLM. The migration story matters. Here's the plan.
Status
Migration tooling is under construction.
We're shipping the tooling alongside our 1.0 launch. The page below is the planned shape, not the documented current state — every item is on the roadmap and design-locked, but not all are wired up yet. If you're evaluating Thoma and migration is the gating concern, talk to us. We've helped early customers migrate by hand and we can do the same for you while the importer matures.
What we plan to offer
Each item below is a planned migration capability. Some land in the first installer, others ship as importer add-ons over the first few releases. The data-export contract is committed from day one.
File-vault import from shared drives
Point the importer at a network share (or a zip of one). It walks the directory tree, brings each file into the controlled vault, preserves the folder structure as document categories, and generates an audit-log entry for every imported file so your migration is itself defensible.
Planned
BOM import from Excel
Excel-based BOMs are how most pre-PLM shops keep parts lists. The importer reads structured BOM workbooks (configurable column mapping), creates parent / child part records, links revisions, and flags ambiguity for human review rather than guessing.
Planned
Change-history seeding (or starting fresh)
Two paths. (1) Import existing change records from CSV / Excel — useful when a CMMC auditor expects historical traceability. (2) Start fresh with the day-one state baselined — simpler when prior records aren't reliable.
Planned
User-and-permission migration
Bulk-import users from CSV with role assignments. Map your existing approver matrix into Thoma's per-category permission structure. New users get setup-link emails on a controlled cadence so day-one isn't a flood of password resets.
Planned
Data export contract
Migration runs in both directions. You can leave Thoma whenever you want — full Postgres dump + the file vault is yours. No export fee, no proprietary container format. Documented in the Terms of use.
Planned
Guided migration (Enterprise)
Enterprise tier includes a guided onboarding call where we work through your existing data shape together, set up the importer config, run a dry-run against a copy of your data, and only then execute the real migration on a scheduled cutover window.
Planned
Principle
Your data is yours.
Whatever migration tooling we ship, it's symmetric. If you can get your data in, you can get it back out — no proprietary file format, no per-export fee, no "we'll release your data after a 90-day notice period" clause. A full backup is a Postgres dump plus the file vault directory. Both are formats your IT team already knows how to handle.
The export contract is documented on the Terms of use page. It's the same contract for trial, paid, and Enterprise customers.
Have a specific source system in mind?
Tell us what you're migrating from — Arena, Windchill, Teamcenter, shared drive, custom Excel. We'll be honest about what's a clean import vs. what's going to need hand-massaging.