How to switch from FIELDBOSS without losing a single car's test date or callback history
Short answer: check your FIELDBOSS term and your Microsoft license renewal dates first, then decide with your accountant whether Business Central stays as your ledger and payroll. FIELDBOSS doesn't publish an export guide and your data lives in Business Central, so ask FIELDBOSS or your Microsoft partner in writing for Excel or CSV files of buildings, units, MCP task lists, test dates, contracts and open work. Rebuild your MCP checklists and callback board, move one route at a time, move contract billing last at a month end, and keep FIELDBOSS readable until a fixed date.
With Fieldproxy, migration is free and assisted and you're live within a day: your first route mechanic runs real monthly visits and callbacks in Fieldproxy the day after the setup call, with your own MCP tasks, test sheets and callback stages. Everyone else moves on a schedule you set. One price per company, unlimited users, so adding an apprentice or a dispatcher never adds a license.
Leaving FIELDBOSS? See your setup first
Send us a FIELDBOSS export. We build your stages, forms and data in Fieldproxy, free, before you decide.
Why teams leave
Why teams leave FIELDBOSS, with the facts checked
FIELDBOSS is a serious product. It puts elevator field service, CRM, general ledger and payroll inside Microsoft Dynamics 365 Business Central, handles A17.1 compliance, Category 5 testing and violations, and its mobile app works offline. Contractors who leave it are rarely missing an elevator feature. More often they don't want an ERP project attached to their field software, or they want software that reaches the phone and the building owner. Each point below was checked against FIELDBOSS's own pages on 19 November 2026.
You didn't want to adopt Microsoft Dynamics 365
FIELDBOSS runs as an extension inside Business Central, with sign-in through Microsoft Entra ID, and its own comparison page describes implementation typically with a Microsoft partner and per-user Business Central and Dynamics licenses. That suits a contractor already standardised on Microsoft. If you're not, you're taking on an ERP, a license relationship and usually a partner. Fieldproxy needs none of that: it runs on its own, and syncs two-way with QuickBooks Online, Desktop and Enterprise, Xero and Sage, with exactly what syncs agreed and tested during setup.
source: FIELDBOSS: Dynamics 365 Business Central (native extension, Entra ID sign-in)source: FIELDBOSS: FIELDBOSS vs LiftKeeper (Microsoft partner implementation, per-user licenses)
Onboarding priced like an ERP project
FIELDBOSS publishes onboarding from $50,000 (Rapid), $75,000 (Complete) and $100,000 (Enterprise White-Glove). Its Action Elevator story describes an eight to nine month program run with an outside implementation partner. That is a fair price for an ERP rollout at a company with thousands of units. With us, migration is free and your first mechanic is on real jobs the day after the setup call.
source: FIELDBOSS: Pricing (per-user licenses, onboarding tiers)source: FIELDBOSS: Action Elevator customer story (8 to 9 month program, Liberty Advisor Group)
Every mechanic and office user is a license
FIELDBOSS mobile licenses start at $90 per user a month and back office licenses at $185. Twenty mechanics and six office staff start at $2,910 a month on those figures alone. Fieldproxy has unlimited users on every plan and prices by monthly job volume, so apprentices, helpers on a Category 5 test day and a part-time dispatcher all log in without changing the bill. See how plans work.
source: FIELDBOSS: Pricing (per-user licenses, onboarding tiers)
MCP checklists sit on the higher tier
FIELDBOSS's pricing page shows the Rapid tier without Forms and Checklists, payroll, inventory or IoT. For an elevator contractor the unit's MCP task list is the core record. In Fieldproxy every car carries its own MCP task list with intervals and code sections, each visit pulls only the tasks due that month, and the mechanic's ticked checklist prints as a signed page where the jurisdiction wants paper in the machine room.
source: FIELDBOSS: Pricing (per-user licenses, onboarding tiers)
AI that works on records, not on the after-hours line
FIELDBOSS's two published agents classify work as billable or contract-covered and brief a technician at clock-in. Both are useful, and both work inside the system. We found no phone, text or email agent and no ChatGPT, Claude or MCP connection on its AI pages. Our calling agent can answer the after-hours line, ask which car and whether anyone is trapped, and page the on-call mechanic, and our MCP server lets ChatGPT, Claude and Copilot work on your data with a person confirming each change.
source: FIELDBOSS: AI and agents (Service Review Agent, Site Brief Agent)
Owners want to see their cars, not a PDF
FIELDBOSS lists a customer portal among its reporting features. In Fieldproxy each property manager gets a portal scoped to their buildings, showing every unit's last visit, callbacks with response times, last Category 1 and 5, certificate expiry and open deficiencies with due dates, and can approve a repair or modernization quote from a link without a login.
source: FIELDBOSS: Elevator contractor management software (modules, Selco Elevators)
Stay on FIELDBOSS if
- You want general ledger, payroll, three-way PO matching and multi-entity consolidation in the same Microsoft system as dispatch. FIELDBOSS does that and Fieldproxy is not a ledger.
- You're a roll-up whose finance team, auditors or owner already run on Business Central, and the field side is working.
- You rely on FIELDBOSS's CEDES IoT integration for live shutdown alerts. Fieldproxy doesn't list a CEDES integration, so confirm a route before you move.
- You've just finished a FIELDBOSS implementation and your team trusts it. Don't move to fix a problem you don't have.
- You're mid-term on FIELDBOSS or Microsoft licenses. Build and test now, and set the cutover for the renewal date.
Before you go
What to export from FIELDBOSS, and how
FIELDBOSS doesn't publish an export guide. Because it runs inside Business Central, your records sit in Business Central tables, and many lists there can be opened in Excel. Treat every row below as a written request to FIELDBOSS or your Microsoft partner: ask for Excel or CSV files with FIELDBOSS's own customer, building and unit numbers kept so records can be matched. Ask well before your notice date and open every file.
| Data | How to get it out of FIELDBOSS | What happens to it in Fieldproxy |
|---|---|---|
| Customers, buildings and contacts | Ask FIELDBOSS or your partner for customers, bill-to and site addresses and contacts, with their IDs. | Customers and buildings with bill-to kept separate, so management companies with many buildings bill correctly. |
| Units and equipment | Ask for every unit per building: device number, type, controller, capacity, speed, stops, install date, certificate expiry, custom fields. | One record per car, escalator or lift with its own QR code. Controller, code edition and hydraulic cylinder type are kept. |
| MCP task lists and checklist templates | Ask for the checklist templates per unit type and per unit, with intervals, as Excel or as printouts. | An MCP task list per unit, with interval and code section, versioned when the unit is altered. |
| Visit and callback history | Ask for completed service activities per unit with dates, cause and fix, covering the retention period your jurisdiction sets. | History attached to each unit, so the next mechanic and the inspector see what was done to that car. |
| Category tests and violations | Ask for last Category 1 and Category 5 dates per unit and open violations with their clearance status. | Next tests generated from the last dates; open violations become deficiencies with code reference and due date. |
| Maintenance contracts | Ask for each contract: units covered, monthly price per unit, coverage type, rates, escalation, start, renewal, notice and next bill date. | Contracts priced per unit with response terms, keeping their next bill date. Nothing is billed until you switch billing over. |
| Open jobs, quotes and modernization projects | Ask for open service activities, repair jobs and quotes with status, and projects with cost and billing to date. | Open work lands at the right stage; projects carry cost and billing to date as a starting point. |
| Open AR, inventory and POs | Run an AR aging at cutover in Business Central and export stock by location and open purchase orders. | Open invoices go to your accounting system; stock per warehouse and van, with parts used on jobs pulled from it. |
source: FIELDBOSS: Dynamics 365 Business Central (native extension, Entra ID sign-in)source: FIELDBOSS: Elevator industry page (A17.1, Cat 5, violations, CEDES IoT)source: FIELDBOSS: Elevator contractor management software (modules, Selco Elevators)
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 ledger and payroll in Business Central
If Business Central has been your books and payroll, the chart of accounts, posting setup and payroll history stay there. If you're moving them, your accountant sets up QuickBooks, Xero or Sage from trial balances, open AR and AP and payroll year-to-date at a period end. We then agree and test what syncs, for example invoices, payments, customers and items. If Business Central stays your ledger, ask us early how the sync to it will be handled.
source: FIELDBOSS: Dynamics 365 Business Central (native extension, Entra ID sign-in)
AI agents, dashboards and Power BI reports
The Service Review and Site Brief agents, pre-built dashboards and any Power BI reports are part of FIELDBOSS and Microsoft, not data. List the reports your owners and service managers read each week, and we rebuild them as Fieldproxy dashboards and scheduled reports.
source: FIELDBOSS: AI and agents (Service Review Agent, Site Brief Agent)source: FIELDBOSS: Elevator contractor management software (modules, Selco Elevators)
CEDES IoT and other integrations
The CEDES IoT feed, Power BI and Fabric links and anything your partner built stop with FIELDBOSS. Note which ones you use and what each one creates, so we can agree a replacement or a manual step for each before cutover.
source: FIELDBOSS: Elevator industry page (A17.1, Cat 5, violations, CEDES IoT)
Paper in the machine room
Changing software never removes on-site records. In Colorado the MCP belongs to the building owner and a replaced contractor leaves the records behind; other jurisdictions keep the MCP logbook in the machine room. Those pages stay where they are, and Fieldproxy prints new signed pages from the first visit.
source: Colorado Division of Oil and Public Safety: Conveyance MCP guidance (records stay on site)
Do these before you cancel FIELDBOSS
- Read your FIELDBOSS agreement and your Microsoft license terms for term, notice and renewal dates, and get anything unclear in writing.
- Decide with your accountant whether Business Central stays as the ledger and payroll system after cutover.
- Send a written export request covering every row in the table above, and open each file when it arrives.
- Check that every unit's last Category 1 and Category 5 dates are in the export; these drive next year's test schedule.
- Export open violations and deficiencies with their due dates, so no NYC 90-day correction or AHJ deadline slips.
- Run the AR aging and financial reports at cutover, and keep them for audits.
- Keep read-only access to FIELDBOSS and Business Central until after year-end close if the ledger lived there.
Send us your FIELDBOSS export and see it running in your setup.
Get DemoLive within a day
The move from FIELDBOSS, 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 means your first route runs real jobs, not that the whole company has moved. Moving the ledger and payroll off Business Central, a large unit count or many open modernization projects add time, and we say how much on the first call.
What happens on go-live day- 1
Before the call: renewal dates, ledger decision and export request
You and your accountant, about two hours
Find the FIELDBOSS and Microsoft renewal dates. Decide whether Business Central stays. Send the export request. Pick a first route to move, for example one mechanic's monthly route in one city, and a month end for contract billing. - 2
The call: one building, end to end
You and Fieldproxy, 30 minutes
Walk us through one building: its cars, the MCP tasks per car, a monthly visit, a callback with an entrapment, the last Category 5 test day, an inspector's deficiency list and how the contract bills. Send a sample MCP page, test sheet and contract, and the exports you already have. - 3
We build your setup
Fieldproxy's team
Unit register and MCP task lists, monthly visits, the callback and entrapment board with your contract response terms, Category 1, 3 and 5 test jobs and sheets, deficiencies with due dates, contracts priced per unit and the owner portal, on the web and the iOS and Android app. - 4
We move your data, free
Fieldproxy's team and Fieldproxy AI
Customers, buildings, units, MCP lists, contracts, open work and history, mapped and checked for duplicates with FIELDBOSS IDs kept. Every unit arrives with its last visit and last Category 1 and 5 dates, so the next ones generate on time. - 5
We connect the books
Fieldproxy's team, with your accountant
Two-way sync with QuickBooks Online, Desktop or Enterprise, Xero or Sage, tested with real invoices and payments before anyone depends on it. Contract billing stays in FIELDBOSS for now. - 6
Live: the first route runs real jobs
The day after the call
The pilot mechanic scans the controller QR code, works the MCP tasks offline in the machine room and pit, records oil added and firefighters' service results, and prints the signed page. Everyone else stays on FIELDBOSS, and the office sees both. - 7
Weeks or months: route by route, billing last
Your schedule
Move the remaining routes and then the after-hours callback line. After one billing cycle matches line by line, switch contract billing at a month end. Then take final exports and reduce licenses at renewal.
Cutover
Running FIELDBOSS and Fieldproxy side by side
For an elevator contractor the overlap has two speeds: routes and callbacks move quickly, team by team, and contract billing moves once, at a month end, after a full cycle has been checked.
Every unit lives in one system
A unit's visits, callbacks and tests are worked in Fieldproxy or in FIELDBOSS, never both. When a route moves, its units move with it; anything opened in FIELDBOSS before the move is finished there.
One callback line at a time
The after-hours number points to one place. Until the last route moves, callbacks for units still on FIELDBOSS are logged there, and entrapments are never split across two boards.
A fixed switch-off date
Agree the date FIELDBOSS becomes read-only, ideally at its renewal. While the team is new to Fieldproxy, the Watcher agent flags entrapments with no on-site time, deficiencies near their deadline and Category 5 windows with no test booked.
The fear
What if a Category 5 test or an inspector's correction deadline slips during the move?
A missed test window or correction date lands on the building owner as a fee or a violation, and the owner remembers who was maintaining the car. In NYC, CAT1 and CAT5 reports are due within 21 days and defects must be corrected within 90. This is how we keep the switch from touching those dates.
- 1
Dates move before anything else
Every unit's last Category 1 and 5 dates and every open deficiency with its due date are loaded and checked first, before any route moves, against the schedule you run today. - 2
A due list you can compare
Fieldproxy produces the list of tests and corrections due in the next 180 days. Your service manager compares it with FIELDBOSS line by line and every difference is fixed before go-live. - 3
Deadlines watched from day one
The Watcher agent alerts your service manager when a deficiency nears its deadline or a Category 5 window approaches with no test booked, whichever system the unit is in during the overlap. - 4
Filing dates are required fields
A test job can't close without its filed date, and a deficiency can't close without its correction date and its AOC or clearance date, so nothing is marked done that the AHJ hasn't received.
Where things live
FIELDBOSS terms and where they go in Fieldproxy
So your office and mechanics know where things went on the first day. How contracts and modernization projects bill is agreed on the call.
| In FIELDBOSS | In Fieldproxy |
|---|---|
| Service activity / work order | Job on the unit, with your statuses, checklist and required photos |
| Emergency call creates a service activity | Callback with trapped flag and timestamps; entrapments page the on-call mechanic |
| Equipment record | Unit register: device number, controller, code edition, certificate expiry, QR code |
| Inspection and safety checklists | MCP task list per unit, pulled into each monthly visit, printable as a signed page |
| Safety test and violation management | Category 1, 3 and 5 test jobs and deficiencies with code reference and due date |
| Contract management, recurring billing | Contracts priced per unit with response terms, syncing invoices to your accounting |
| Projects (modernization, installation) | Modernization quotes and project jobs on the unit, approved from a link |
| Mobile app (offline) | Offline mechanic app in 27 languages: checklists, photos, signatures, QR codes, GPS check-in |
| Customer portal | Owner portal per customer or building: units, callbacks, tests, deficiencies, quotes |
| Business Central GL, payroll, purchasing | No ledger in Fieldproxy: books stay in QuickBooks Online, Desktop or Enterprise, Xero or Sage |
| Service Review Agent, Site Brief Agent | AI agents on phone, text and email, and an MCP server for ChatGPT, Claude and Copilot |
Straight answers
Switching from FIELDBOSS: FAQ
How long does it take to switch from FIELDBOSS to Fieldproxy?
Is migration from FIELDBOSS free?
Do I still need Microsoft Dynamics 365 or Business Central?
Does Fieldproxy replace FIELDBOSS's accounting and payroll?
Does the mechanic app work offline in machine rooms and pits?
Can Fieldproxy keep the MCP on paper where the jurisdiction requires it?
Do AI agents answer entrapment calls?
Can ChatGPT or Claude work with my elevator data?
Will I keep my CEDES IoT shutdown alerts?
Sources
Where the facts on this page come from
Every FIELDBOSS fact links to FIELDBOSS'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 elevator service companies.
- source: FIELDBOSS: homepage (built natively on Business Central, industries)
- source: FIELDBOSS: Elevator contractor management software (modules, Selco Elevators)
- source: FIELDBOSS: Elevator industry page (A17.1, Cat 5, violations, CEDES IoT)
- source: FIELDBOSS: Pricing (per-user licenses, onboarding tiers)
- source: FIELDBOSS: About (offices in Toronto and Aventura)
- source: FIELDBOSS: Dynamics 365 Business Central (native extension, Entra ID sign-in)
- source: FIELDBOSS: Mobile app (iOS, Android, offline)
- source: FIELDBOSS: AI and agents (Service Review Agent, Site Brief Agent)
- source: FIELDBOSS: Action Elevator customer story (8 to 9 month program, Liberty Advisor Group)
- source: FIELDBOSS: FIELDBOSS vs LiftKeeper (Microsoft partner implementation, per-user licenses)
- source: Colorado Division of Oil and Public Safety: Conveyance MCP guidance (records stay on site)
- source: NYC Department of Buildings: Elevator compliance (21-day filings, 90-day corrections)
Leave FIELDBOSS without the leap. Live within a day.
A 30-minute call about how a job runs in your business, and a FIELDBOSS 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.