"One-click migration" is one of the most comforting phrases in the whole Horizon move. It sounds like you press a button and your entire business appears, whole, on the other side. Sometimes that is close to true. Often it is true about one half of your business and quietly not true about the other half. This article is about telling those two halves apart.
Your software holds two very different things
One: your records. These are the facts of every job. Dates, addresses, prices, order IDs, the agents and clients tied to each inspection. Think of records as your filing cabinet: who, when, where, how much.
Two: your comment library. This is not facts about jobs. It is your writing. The sentences you use to describe a cracked heat exchanger, a soft deck board, a double-tapped breaker, all in the exact wording you trust and have defended. Think of the library as your voice.
One-click migration is usually very good at the first half and much shakier on the second.
What "one-click" usually moves well
The records move. That is the part built for a clean automated transfer, because it is structured data: neat rows and fields that map easily from one system to another. Your past job list, your addresses, your contacts, your order history. Good migrations carry this over reliably, and that is genuinely useful. Not having to retype your client list is real value.
What it often leaves behind or changes
Your comment library is the piece to watch, for two reasons.
First, it may come in a changed form. This is the common one. Your library transfers, but on the way it gets converted into the new tool's format, and some tools then run your comments through an AI that rewrites and refines your language. That is not your wording moved over. That is new wording written to resemble yours, and you will feel the difference the first time you read a report that is almost you but not quite.
Second, with some tools it may not come at all, or not all of it. A one-click move can carry your records and still leave part of your library sitting in the old software. You arrive at the new tool with your job history intact and pieces of your voice missing.
Why this is the part that matters
Your records are replaceable in a pinch. You can retype a client list. You cannot retype fifteen years of carefully worded comments from memory, and you should not have to. Your library is the reason your reports sound like a seasoned inspector instead of a form letter. It is also, honestly, a safety layer: wording you have already checked and stand behind is wording that will not surprise you in front of a lawyer.
So when a tool says "one-click migration," it is not a lie, but it is not the whole answer either. The real question is underneath it.
The question to ask under the button
Ask it plainly: "Your one-click migration moves my records. Does it also move my comment library, in my exact words, unchanged? Or does it rebuild my comments into new text?"
Get the answer before you commit, and get it in writing. "It rebuilds them" and "it moves them" lead to two completely different first months in your new software.
How Mach One handles it
We treat your comment library as the main event, not an afterthought. We import it in your exact words, unchanged, reading 7 common file types. Nothing gets rewritten. Your report comes out sounding like you, and it is built to tell "no damage" from "damage," so it does not just grab any comment with the word damage in it.
And on our rescue rate, monthly or annual, you do not press a button and hope. A real person sits with you one on one, during your free 30 days, and moves your library and template across with you, so you can see your own words land where they belong.
Your software is shutting down. We import the library you spent years building.
