The scariest part of switching inspection software is not learning a new tool. It is the fear that your comment library, years of your exact wording, will not make it across in one piece. That fear is why a lot of inspectors stay stuck on software they have outgrown. Here is the plain truth about how a library actually moves, the file types that carry it, and why import beats rebuild every time.
Your library already lives in a file
Whatever software you use now, your comment library is stored in some format underneath. When you export it, it comes out as one of a handful of common file types. The whole game of a clean switch is having new software that can read the format your library comes out in, and keep your wording exactly as written.
The formats that carry a library
Mach One reads 7 common formats, which covers the great majority of what inspection software exports:
- ZIP backup (such as a RapidRemarks backup file)
- Excel (.xls and .xlsx spreadsheets)
- Word (.doc and .docx documents)
- RTF (rich text)
- CSV (comma-separated values)
- TXT (plain text)
- JSON (structured data)
That is 7 formats across the file types most libraries live in. If your export lands in one of these, your wording can come across unchanged.
One honest caveat about messy exports
File reading is not always perfectly clean, and it is fair to know why. Some exports include a banner or title row at the very top before the real column headers, and a strict importer can misread that and jumble the columns. It is a known, fixable kind of snag. The point of white glove onboarding is that a real person handles exactly these bumps for you, checks the import came in clean, and fixes the file if it needs it, so you are not left wrestling a spreadsheet alone.
Import versus rebuild, one more time
This matters enough to repeat. Import means your exact comments carry over, word for word. Rebuild means new software generates a fresh library in its own style, often averaged from thousands of other inspectors' reports, and hands you the job of correcting sentences that are close but not you. Import keeps what you built. Rebuild quietly replaces it. When you ask about moving your library, get a straight answer on which one you are being offered.
What to ask before you trust the move
- What file formats do you import, and which one does my current software export?
- Do my comments come across in my exact words, unchanged?
- Who does the work if my export file is messy, me or you?
- Can I export my whole library back out later, whenever I want?
Good answers sound like "we handle that" and "your words, unchanged, and yes you can always export." Weak answers push the work back onto you or dodge the export question.
How Mach One does it
We import your existing comment library in your exact words across those 7 formats, so nothing gets rewritten into robot text. With white glove onboarding, a real person runs the import for you, from your existing files, and confirms it came in clean before your walkthrough call. And your library stays yours: you can export it anytime and take it wherever you go.
Your software is shutting down. We import the library you spent years building.