How to switch from Centerpoint Connect without a leak call falling between two systems
Short answer: check your Centerpoint Connect billing period, term and notice first (its pricing cards list per-user prices but not the period, so get the terms in writing). Then ask Centerpoint for a full export of companies, properties, inspections, service tickets, agreements, warranties and invoices, and agree the scope and any fee up front. Rebuild your roof sections, leak statuses and warranty rules in the new system, move one service crew or region at a time, avoid switching mid inspection season, and keep Centerpoint readable until a fixed date.
With Fieldproxy, migration is free and assisted and you're live within a day: your first crew runs real leak calls and inspections in Fieldproxy the day after the call, on your own owners, buildings and roof sections. Everyone else moves on a schedule you set. One price per company, unlimited users, so office staff, supervisors and seasonal techs cost nothing extra.
Leaving Centerpoint Connect? See your setup first
Send us a Centerpoint Connect export. We build your stages, forms and data in Fieldproxy, free, before you decide.
Why teams leave
Why teams leave Centerpoint Connect, with the facts checked
Centerpoint Connect is built only for commercial roofing, and it shows: properties, inspections, proposals, service tickets and production jobs in one roofing system, a deep accounting and ERP list, and published prices. Most teams that look at leaving aren't unhappy with its roofing knowledge. They have a service and maintenance side that has outgrown how the product is packaged or modelled. These are the reasons we see, each checked against Centerpoint's own pages.
The roof section is the unit of work
Warranty, code and repair decisions are made per roof section: membrane, attachment, layers, manufacturer, warranty number and expiry. Centerpoint's public roadmap lists โRoof sections on agreementsโ as planned work, so today a service agreement's coverage per section can end up in notes. Check the current release in a demo. In Fieldproxy, each building is split into sections from day one, and the agreement names the sections it covers.
source: Centerpoint Connect: home page and public product roadmap
Paying for a sales CRM to run a service department
Centerpoint's pricing says CP Essentials is the required Sales CRM foundation, and Service It is an add-on to it. A service-led department still buys the sales platform, its setup fee and its per-user prices ($50 per field user, $100 per office user). Fieldproxy is one price per company with unlimited users, set by job volume. See pricing.
Leak calls run on each owner's clock
Every owner writes its own response time and not-to-exceed amount. Centerpoint's service flow covers request, dispatch, documentation, supervisor review, client notice and invoicing. Teams leaving want the due time computed from each owner's agreement and an alert before a breach. In Fieldproxy the leak ticket sets its own due time from the agreement, and the Watcher agent warns the service manager before it runs out.
Manufacturer warranty duties left to memory
Carlisle and GAF both require written leak notice to the manufacturer within 30 days, and GAF says notice to the contractor doesn't count. In Fieldproxy, a leak on a warrantied section opens a manufacturer notice task due in 30 days, and any job that adds a curb, penetration or solar racking is blocked until the written authorization is attached.
source: Carlisle SynTec: Golden Seal warranty sample, 30-day leak notice (F0001, Rev 12/24)source: GAF: EverGuard Diamond Pledge NDL guarantee, notice terms (COMTS728-1224)
Nobody answers the leak line at 2 am
The Centerpoint pages we read don't describe an AI phone or text agent that takes a leak call and opens a ticket. Fieldproxy's calling agentcan be set up to answer, identify the building, ask where water is coming in, check the owner's emergency clock, open the ticket and page the on-call tech, with a person confirming anything it changes.
Integration and API fees
Centerpoint's FAQ says accounting, API, ERP and custom integrations may need separate scoping and fees, and Enterprise API access is an extra monthly subscription. Fieldproxy includes integrations by plan, and its open API and MCP server let Claude, ChatGPT or Copilot read your roofs and do anything the app can do, with a confirm step.
source: Centerpoint Connect: pricing, plans and FAQ (per-user prices, setup fees, integration scoping)source: Centerpoint Connect: integrations and REST API
Stay on Centerpoint Connect if
- Your books run on Spectrum, Vista, Acumatica, Sage Intacct, Foundation or ComputerEase. Centerpoint lists these; Fieldproxy's accounting links are QuickBooks Online, Desktop and Enterprise, Xero and Sage, so ask us in writing how your ERP would connect before you decide.
- Reroof and new-construction production, with daily progress reports, budgets and job costing, is most of your revenue and works well in Centerpoint today.
- You like having sales, service and production in one roofing-only system, and the roadmap items you need (such as roof sections on agreements) will ship in time for you.
- You want a published price list you can budget from before a call. Centerpoint publishes its; Fieldproxy's pricing is by job volume, on request.
- You're mid-term or the team is settled. Check your agreement first, and don't switch to fix a problem you don't have.
Before you go
What to export from Centerpoint Connect, and how
Centerpoint doesn't publish a self-serve export guide on the pages we read. Its integrations page lists a REST API, and its pricing FAQ says custom work may need separate scoping and fees. So the plan is simple: ask Centerpoint early for a CSV of each record type below, get the scope and any fee in writing, and pull files and photos before your seats end.
| Data | How to get it out of Centerpoint Connect | What happens to it in Fieldproxy |
|---|---|---|
| Companies, contacts and properties | Ask Centerpoint for a CSV of companies, contacts and properties with addresses and billing rules, or pull them through the REST API. | Owners, buildings and contacts, checked for duplicates. Each building gets a QR code and is split into roof sections. |
| Roof inspections | Ask for a CSV of inspections by property, plus the report PDFs and photos. | Past inspections sit on each roof section as history; condition notes carry forward to the next spring or fall visit. |
| Service tickets | Ask for open and recent tickets with status, assigned tech, photos and notes. | Open tickets come in as live leak tickets at the right status; closed ones become history on the section. |
| Maintenance agreements | Ask for scope, frequency, pricing, start and renewal dates for every agreement. | Rebuilt as agreements with sections covered, inspection windows, response clocks and not-to-exceed amounts. |
| Warranties | Ask for warranties stored against production jobs: manufacturer, number, term and expiry. | Put on each roof section, with the manufacturer's notice and alteration rules attached. |
| Open proposals and estimates | Ask for proposals still awaiting a decision, with line items and photos. | Carried over so the owner can approve line by line online; none lost mid-decision. |
| Repair and material libraries, labor rates | Ask for a CSV of the libraries and rates. | Your price list, with approved repair materials tagged by membrane type. |
| Invoices and payment status | Reconcile against QuickBooks or your ERP, which already holds the ledger. | Open balances checked with your bookkeeper; the ledger stays in your accounting system. |
| Files, client portal users, drone and 3D links | Ask for property files, portal user lists and stored links (including CompanyCam links). | Files attached to the right building; owners re-invited to their new portal on day one. |
source: Centerpoint Connect: integrations and REST APIsource: Centerpoint Connect: pricing, plans and FAQ (per-user prices, setup fees, integration scoping)source: Centerpoint Connect: client portal
What doesn't come with it
What doesn't export, and what we rebuild
An export carries records, not the way your account is set up. Here is what to expect, and who does the work.
Your statuses, report templates and approval gates
Records move; setup doesn't. Ticket statuses, the supervisor review step, approval gates before billing and your inspection report layout are rebuilt. We mirror your current status names where they work, so techs recognise them on the first morning.
Integrations and API connections
Links to QuickBooks, your ERP, HubSpot, CompanyCam, Zapier or MindCloud stay in Centerpoint. List each one and what it syncs. In Fieldproxy, the accounting sync is agreed and tested on a copy before go-live, and anything not on our list is discussed openly on the first call.
Roof drawings and pinned repair locations
Centerpoint lets techs capture repair locations by drawing or photo. Ask how those drawings come out: as images, PDFs or data. We attach them to the right section and pin open deficiencies on the roof plan again where it matters.
Portal logins and owner habits
Owner logins don't transfer. Plan a short note to each property manager with the date and the new link, and load their full roof history first so the new portal is never emptier than the old one.
Do these before you cancel Centerpoint Connect
- Read your Centerpoint agreement for the billing period, minimum term, notice and renewal date, and get anything unclear in writing.
- Request the full export early, with its scope and any fee in writing, and keep every file.
- Pull inspection report PDFs, ticket photos, roof drawings and warranty certificates, property by property.
- Screenshot your ticket statuses, approval gates, report templates and agreement terms.
- Turn off Centerpoint's accounting sync for any job Fieldproxy now invoices, so nothing reaches the books twice.
- Keep read access for at least one full inspection season: warranty disputes often reach back to inspections done years earlier.
Send us your Centerpoint Connect export and see it running in your setup.
Get DemoLive within a day
The move from Centerpoint Connect, day by day
Migration to Fieldproxy is free and assisted: our team builds your setup and moves your data. You're live within a day, meaning your first team runs real jobs in Fieldproxy the day after the call. How fast everyone else follows is your call.
Live within a day is when your first crew runs real jobs, not a deadline for the whole department. A large portfolio, many ERP links or a big warranty clean-up adds time, and we say so on the first call.
What happens on go-live day- 1
Before the call: terms, exports and a first crew
You, about an hour
Find your Centerpoint term and notice date and request the export. Pick a first crew or region to move, ideally after a full spring or fall round has been reported, and a date for Centerpoint to go read-only. - 2
The call: one leak, from 2 am call to paid invoice
You and Fieldproxy, 30 minutes
Walk us through a leak on a warrantied roof and a spring inspection: who takes the call, the owner's clock, the not-to-exceed amount, the manufacturer notice, the report and the invoice. Send the exports, a few agreements, inspection reports and warranty certificates. - 3
We build the roof register and your rules
Fieldproxy's team
Owners, buildings, roof sections and components (drains, scuppers, curbs, units, skylights, hatches), with warranty fields per section. Leak statuses from New to Closed, close-out rules, the 30-day manufacturer notice task, alteration blocks and your inspection checklist and report template. - 4
We move your data, free
Fieldproxy's team and Fieldproxy AI
Properties, inspections, open tickets, agreements, warranties, proposals and libraries, mapped and checked for duplicates. Spring and fall inspection windows are set per section from your agreements. - 5
We connect the books
Fieldproxy's team, with your bookkeeper
Two-way sync with QuickBooks Online, Desktop or Enterprise, Xero or Sage, agreed and tested on a copy against real invoices before it goes live. - 6
Live: the first crew on Fieldproxy
Day one
One crew or region takes today's leak calls and inspections in Fieldproxy: safety check, roof access log, pins on the roof plan, before and after photos, owner sign-off. Everyone else stays on Centerpoint for now. - 7
Weeks or months: region by region, then switch off
Your schedule
Move the next crew when the last is settled, and invite owners to the new portal as their buildings move. When the last Centerpoint ticket closes and the invoices reconcile, take the final export and end the seats.
Cutover
Running Centerpoint Connect and Fieldproxy side by side
For a short, dated window, both tools are open. Fieldproxy is there to replace Centerpoint Connect, not to sit on top of it, so the rules below are about ending the overlap cleanly. Our view from moves we have run, not a sourced fact.
Split by crew or region, not by ticket
Each crew works in one system. A crew on Fieldproxy takes every new leak call and inspection there; a crew still on Centerpoint stays there. The leak line routes by building, so nobody keys a ticket twice and no call lands in the gap.
One system invoices each job
Open tickets finish where they started. Agree which jobs each tool bills and a numbering rule, and turn off Centerpoint's accounting sync for anything Fieldproxy invoices.
A fixed switch-off date, after a full season
Don't cut over mid inspection round: switch in summer or winter, after spring or fall is fully reported. Keep Centerpoint readable, not in use, and set the date it goes off.
The fear
What if a warrantied roof leaks in the middle of the move?
It's the right worry. A missed 30-day manufacturer notice or a late response on an owner's clock costs more than any software. This is how to make the move small and checked before it counts.
- 1
Warranties go in first
Every warrantied section is loaded with its manufacturer, number and expiry before the first crew goes live, so the 30-day notice task fires on the first leak, not the tenth. - 2
Every open leak is listed on both sides
On cutover day we list every open Centerpoint ticket on a warrantied roof, with its notice date, and the Watcher agent tracks them until each is closed or the notice is sent. - 3
One crew finds the gaps
If a checklist line or a close-out rule is missing, one crew finds it in a day and we change it, while the rest of the department carries on in Centerpoint. - 4
Nothing goes out without approval
AI agents are off until you switch them on, and each asks before a message, proposal or invoice goes out. Your data stays yours: export to CSV or read it through the API or MCP server whenever you want.
Where things live
Centerpoint Connect terms and where they go in Fieldproxy
So your service team knows where things went on the first morning. How sales and production work maps, if you move them too, is agreed on the call.
| In Centerpoint Connect | In Fieldproxy |
|---|---|
| Properties | Owners and buildings, each split into roof sections with components |
| Roof inspections | Spring and fall inspection jobs per section, with deficiencies pinned on the roof plan |
| Service tickets | Leak tickets with a due time from the owner's agreement and close-out rules |
| Supervisor review and approval gates before billing | Approval steps you define, including holds above each owner's not-to-exceed amount |
| Repair locations by drawing or photo | Pins on the section's roof plan with photo, severity and quantity |
| Service agreements | Maintenance agreements naming the sections covered, inspection windows and response clocks |
| Warranties on production jobs | Warranty fields per roof section, with the 30-day notice task and alteration blocks |
| Proposals | Proposals built from deficiency lines that owners approve line by line online |
| Client Portal | Owner portal per customer or site: roof plans, reports, open deficiencies, leak tickets, warranty expiry |
| Stax payments (in testing) | Payment links and Tap to Pay for card payments in the field |
| QuickBooks and ERP integrations | QuickBooks Online, Desktop and Enterprise, Xero, Sage (two-way); other ERPs discussed case by case |
| REST API | Open API and an MCP server for Claude, ChatGPT and Copilot |
Straight answers
Switching from Centerpoint Connect: FAQ
How long does it take to switch from Centerpoint Connect to Fieldproxy?
Is migration from Centerpoint Connect free?
Can I keep Centerpoint Connect for sales and use Fieldproxy for service?
Does Fieldproxy work with QuickBooks, Xero, Sage or a construction ERP?
Does the technician app work on a roof with no signal?
Can Fieldproxy track manufacturer warranty rules per roof section?
Can AI agents take leak calls after hours?
Can I use ChatGPT or Claude with my roof data?
When is the best time of year to switch?
Sources
Where the facts on this page come from
Every Centerpoint Connect fact links to Centerpoint Connect's own pages, opened on 19 November 2026. Features and terms change, so check the current page before you decide. More detail, with every source, is in How Fieldproxy is set up for commercial roofing service departments.
- source: Centerpoint Connect: home page and public product roadmap
- source: Centerpoint Connect: pricing, plans and FAQ (per-user prices, setup fees, integration scoping)
- source: Centerpoint Connect: service management
- source: Centerpoint Connect: integrations and REST API
- source: Centerpoint Connect: client portal
- source: Centerpoint Connect: payments (listed as in testing)
- source: Carlisle SynTec: Golden Seal warranty sample, 30-day leak notice (F0001, Rev 12/24)
- source: GAF: EverGuard Diamond Pledge NDL guarantee, notice terms (COMTS728-1224)
- source: Professional Roofing (NRCA): inspection frequency, spring and fall
Leave Centerpoint Connect without the leap. Live within a day.
A 30-minute call about how a job runs in your business, and a Centerpoint Connect export. We show you your own setup and data running in Fieldproxy before you commit.
Plan my switchFree, assisted migration. One price per company, unlimited users. Changes are a conversation.