Kipso Bridge
Move your construction data into Kipso, or get it ready for the system you use.
Into Kipso directly, or as a verified load package for Kahua, Oracle, Procore, Trimble or your ERP. AI matches the messy parts of your spreadsheets, PDFs and old-system exports, and you answer only the exceptions. When Bridge loads into Kipso, it checks every field and can undo; for other systems you get an import guide and a check after you import.
Use our fictional sample files, or upload your own edited copies of them to see how it reads them (demo only, so please no confidential data). In the demo, every destination except Kipso is simulated.
Are you an implementation firm or owner's rep? Partner with us
Kahua, Oracle, Procore and Trimble are trademarks of their respective owners. Kipso and Kipso Bridge aren't affiliated with or endorsed by them.
How it works
Six steps, and people decide at every one that matters.
-
1
Pick your files
Spreadsheets, contract and pay-app PDFs, accounting exports and exports from the system you're leaving. Send what you have, as it is.
-
2
Pick the destination
Bridge reads the destination's setup (its fields, cost codes, project structure and required values) so the data lands the way that system expects.
-
3
AI matches the messy parts
AI proposes how each field and record maps across, with a confidence score, so the clear matches can be accepted together.
-
4
You answer only the exceptions
Your team sees only what it can't match with confidence, like a contract with two amounts, with a best guess filled in. No re-keying.
-
5
Reconcile, sign off and load
Totals must tie before anything loads. A dry run shows what will be created, a named person signs off, and then it loads.
-
6
Verify and undo
Loads into Kipso are read back field by field and can be undone in one step. For other systems, you upload an export after importing and Bridge checks it. Either way, you get a handover report of what moved and why.
What you get
A verified load package
Your data, cleaned and mapped to the destination's own field names, ready for that system's import tools. Live connections may be added later, one system at a time.
An import guide for your system
Step by step, in the right order, with this load's exact counts and totals to check against. Written from each vendor's public documentation, with its sources.
Verify after import
Export the lists from your system after importing and upload them. Bridge compares every field and total to the cent, and lists anything missing, changed or extra.
A mapping and exceptions report
How every field was mapped, every question your team answered and who answered it, and anything that had no place to go.
Reconciliation to the penny
Budgets, commitments, change orders and payments tie out by project, contract and funding source, against your source files.
Undo
When Bridge does the load, which today means loads into Kipso, every record it writes is tracked, so a whole load can be undone in one step.
Who it's for
Owners switching systems
Bring years of projects, contracts and payments with you, reconciled, instead of starting over or re-keying.
Owner's reps and consultants
Spend your time on the client's process, not on data cleanup. Bridge takes on the mapping and reconciliation so you can deliver migrations faster.
Contractors changing software
Moving to new project management or accounting software? Bring your jobs, budgets and billing history across, checked and tied out.
Your migration lead runs it
Program controls, a capital program manager or your owner's rep picks the files, answers Bridge's questions and signs off the dry run. Nothing loads without a named person's sign-off.
Finance can sign off
Bridge reconciles to your accounting to the cent, by project, contract and fund, so your controller or budget analyst can confirm the numbers match the books before go-live.
Into Kipso, or ready for your system
Into Kipso, loaded and verified, free. Or prepared for the system you already use, with an import guide and a check after you import: project management systems like Kahua, Oracle Unifier, Procore and Trimble Unity Construct, and accounting systems like Infor, PowerSchool, Tyler Munis and Viewpoint Vista.
Bring data in from
- Budget workbooks and other spreadsheets
- Contract and pay-app PDFs
- Accounting system exports
- Exports from the system you're leaving
Load it into
- Kipso, free
- Construction project management systems
- Accounting and ERP systems
Today, every destination other than Kipso gets a verified load package for its own import tools. Live connections to other systems may be added later, one system at a time. We haven't run a customer migration yet.
Infor, Kahua, Oracle Unifier, PowerSchool, Procore, Trimble Unity Construct, Tyler Munis and Viewpoint Vista are trademarks of their respective owners. Kipso and Kipso Bridge aren't affiliated with or endorsed by them.
Privacy and security
Your project data stays yours, and you decide what moves.
- A private workspace. Each migration for a real project will run in its own workspace with sign-in, separate from the public demo. Private workspaces aren't open yet; they're available by invitation under a signed agreement.
- A data agreement first. Before you send real data, we agree in writing how it's handled, where it's processed and how long it's kept.
- Deleted on request. When the migration is done, we delete your files and working data when you ask.
- An audit trail. Every mapping decision, sign-off, load and undo is recorded with the person and time.
- Sub-processors: Cloudflare (hosting and storage), Anthropic (AI reading and matching), Resend (sign-in and receipt emails) and Stripe (payments, once paid migrations are offered). We don't train models on your data.
Expected pricing, early preview
Free to try. A flat price per migration.
The dry run and mapping preview are free, and moving into Kipso is free. Into other systems, a flat price per migration starts at $2,500, or ask us to do it for you.
Talk to us about a migration
Tell us what you're moving and where it needs to go. We'll reply by email and can run a free dry run with you, on our sample files or under a signed data agreement first.
Common questions
What is Kipso Bridge, and who is it for?
A data migration tool for construction. It reads the files you already have, matches them to the system you're moving to, checks every number, and loads the data or prepares it for loading. It's for owners switching systems, owner's reps and consultants running a migration, implementation partners, and contractors handing data over to an owner.
Which systems can Kipso Bridge move data into?
Into Kipso, loaded and verified, free. Or prepared for the system you already use: project management systems like Kahua, Oracle Unifier, Procore and Trimble Unity Construct, or accounting systems like Infor, PowerSchool, Tyler Munis and Viewpoint Vista. For those, Bridge produces a verified load package for the system's own import tools, a step-by-step import guide and a check after you import. There are no live connections to other systems yet; they may be added later, one system at a time. In the public demo every destination except Kipso is a simulation built from public documentation.
How does Bridge handle messy data?
AI reads your files and proposes each match with a confidence and its reasoning. Anything it isn't sure of comes to a person with its best guess filled in, which you accept or change; it doesn't fill gaps silently. We test it on deliberately messy sample data, like vendors spelled three ways, dates in seven formats, scanned contracts and two versions of the same file, and we keep fixing what those tests turn up. On messy files, expect more questions for you, not fewer checks.
How do you know the data is right?
Three ways. Bridge reads back every field after a load and compares it with what it meant to write. It reconciles totals to the cent by project, contract and funding source, and against your accounting export when you provide one. And everything it couldn't load or wasn't sure of goes on an exceptions list with the reason, so nothing disappears quietly.
Can we undo a load?
Yes, when Bridge does the load, which today means loads into Kipso: every record it writes is tracked, and the whole load can be undone in one step. If you import a load package with another system's own tools, removing it happens in that system, and the package lists every record so you know exactly what went in.
What does it cost?
The dry run and mapping preview are free, and moving into Kipso is free. For other systems we expect a flat price per migration, set by how many records Bridge reads: $2,500 for up to 500, $7,500 for up to 5,000, and a quote above that. If you'd rather not run it yourself, ask us to do it with you. These are expected prices, confirmed with you in writing first.
Is our data private and secure?
Real projects will run in a private workspace with email sign-in, separate from the public demo, and everyone accepts the data agreement before any file is uploaded. Files are stored privately and encrypted at rest by our hosting provider, Cloudflare, and travel over HTTPS. Uploads, loads, undos and downloads go into an audit log that shows whether it has been altered. You choose how long source files are kept, and you can delete everything, with a receipt. Private workspaces for real projects aren't open yet; they're available by invitation under a signed agreement. Talk to us before sending real files, and please don't upload confidential data to the public demo.
What doesn't Bridge do yet?
It doesn't load live into any system except Kipso yet: every other destination gets a verified load package for its own import tools, with an import guide and a check after you import, and live connections may be added later. Private workspaces for real projects aren't open yet, and two-factor sign-in, malware scanning of uploads and a choice of where your data is stored aren't built. We haven't run a customer migration yet. We'll tell you plainly what applies to your migration before you pay for anything.