Bring your whole company with you

Switching systems used to have a tax: re-enter everything, or leave it behind. We've removed most of the tax.

In-flight jobs migrate as in-flight jobs. A jobs import lands each one in execution with its contract — number, value, retainage, dates — and an SOV import brings every line's scheduled value and billed-to-date. Each job gets sealed with a locked migration baseline carrying your old system's last pay-app number, so your first STrOp pay app picks up at the next number with the previous-application columns already right. The GC sees continuous paperwork.

Nothing links silently. Names that don't match — a GC spelled two ways, a cost code that doesn't exist yet — get called out at review with suggestions, and companies can be created as minimal records on the spot instead of rows importing with dropped links.

Every import is an entry in a ledger, and revertible. Until something real builds on the imported rows — a timecard, a pay app — an admin can undo the whole run from the Import page. Botched file? Revert, fix, re-import.

Coming from American Contractor? Pick the AC kit on the upload step: it pre-maps the .dbf column names and walks the extraction. Hand-fixed a mapping? Save it as a template and the next file maps itself.

Products and CBA labor-rate sheets import now too, so estimating works on day one. The whole path is written up in Help → Migrate your data into STrOp.