Platform Quality
Migration and data imports
Bring your customers, jobs, and history over from legacy FSM tools, structured, validated, and checked before it lands.
Overview
The biggest thing stopping a switch is the fear of losing years of customer and job data. Thorbis is building structured imports from legacy FSM tools that map your existing records into Thorbis and validate them before anything's committed. You'll see what's coming in and what needs attention up front, so your history arrives intact instead of as a messy one-shot dump.
What we're building
Switching tools means moving years of customer records, job history, and notes, and the fear of losing that history keeps a lot of contractors stuck on software they have outgrown. A bad one-shot dump turns into weeks of cleanup and jobs nobody can find.
Thorbis is building structured imports from legacy FSM tools that map your existing records into Thorbis and validate everything before it commits. You map source fields to the right Thorbis records, see what is coming in, and get conflicts and gaps flagged for review up front, so your history arrives intact instead of as a mess you untangle after the fact. It is built for teams leaving another platform who need their past to come with them.
What you'll be able to do
- Import customers, jobs, and history from legacy tools
- Map source fields to Thorbis records
- Validate data before it's committed
- Flag conflicts and gaps for review
- Preserve historical records through the switch
- Preview the full import before anything is committed
- Correct flagged records before they land in Thorbis
Rollout plan
- 01
Core record imports
In progressBring core customer and job records over from a legacy tool with field mapping and pre-commit validation.
- 02
History and edge cases
In progressExtend imports to fuller job history and trickier record types, with conflict and gap flagging for review.
- 03
Repeatable migrations
In progressSupport larger migrations and re-runnable imports so additional records can follow without redoing the whole move.
Milestones
- Not started:
Field mapping
Map source fields from a legacy tool to Thorbis records.
- Not started:
Validation pass
Validate imported data and flag conflicts and gaps before commit.
- Not started:
Review and commit
Let teams review what is coming in and commit a clean import.
- Not started:
History preserved
Carry historical records through the switch intact.
More in Platform Quality
How to send useful feedback
Name the blocked role
Product feedback is more useful when it names the owner, dispatcher, technician, office user, or customer affected.
Explain the workaround
Describe what your team does today and where the process fails under real work.
Define success
Share what would change after launch: time saved, fewer manual steps, cleaner records, or better customer follow-up.