How a biomed service company moves off AIMS without breaking a PM cycle
Short answer: first settle whose AIMS it is. If a hospital owns the instance, its records stay there, and you agree with its HTM lead whether you keep entering work in it. If the instance is your own, check your Phoenix agreement for the notice period, then export equipment, PM schedules and work orders with their labor and material lines to Excel, and ask Phoenix for anything else as CSV. Rebuild your procedures, test forms and contracts, run one client for one full PM cycle in both systems, cut over at the start of a month, and keep the old history readable until a fixed date.
With Fieldproxy, migration is free and assisted and you're live within a day: your first team runs real PMs and repairs the day after the setup call, on your own contracts, device records and test sheets. Every other client and technician moves on a schedule you set. One price per company with unlimited users, so field techs, depot staff, coordinators and client contacts never add a seat. It is a guided setup, not a self sign-up.
Leaving AIMS? See your setup first
Send us a AIMS export. We build your stages, forms and data in Fieldproxy, free, before you decide.
Why teams leave
Why teams leave AIMS, with the facts checked
AIMS is a healthcare-only CMMS from Phoenix Data Systems of Southfield, Michigan, in use since 1984 and now in its AIMS 3 generation. Phoenix lists 3,000 hospitals, 60,000 users and 8 million pieces of equipment under management. It is built for the hospital's side of the table, and it does that well. An independent service organization sits on the other side: it sells contracts, carries many clients at once and has to get paid. That is where the reasons below come from, each checked against Phoenix's own pages or the rule's source.
Contracts from the buyer's side, not the seller's
AIMS's contracts module tracks the service contracts a hospital buys: vendor performance, limits, costs, coverage groups and linked POs. You need the opposite: what each client bought from you, which device classes are in scope, the response terms and the out-of-scope rates. In Fieldproxy each client contract holds coverage, device classes in and out, on-site hours, loaner terms, response terms per priority and the PM window rules, with statuses from Proposal to Renewal due.
source: AIMS, Optional components (contracts, inventory, dispatch center, offline mobile)
Many clients, and a recall that hits all of them
A hospital CMMS holds one organization's inventory. When a recall lands, you have to search every client, including rentals and vendor-owned units. Fieldproxy keeps one inventory per client, searchable across all of them by normalized model and serial, with ownership on each device, so a recall check is one search, not a login per hospital.
source: Phoenix Data Systems, AIMS home page (hospitals, users, equipment under management)source: AIMS, Core components (Scheduled Events, equipment, inspection templates, reports)
Surgery centers and clinics with no CMMS at all
Many of your smaller clients have no system. Your records are their inventory and their survey evidence. In Fieldproxy, each client gets a portal scoped to its own sites and devices: inventory, PM completion by month, incomplete PMs with reasons, failed tests, open repairs and recall status. One-off approvals, like a depot repair quote, go by link with no login.
The clock and the completion number in each contract
A public Texas Tech HSC solicitation asked for on-site response within 4 hours for emergencies. A VA biomed solicitation wants PMs done by the 15th and a month-end list of every incomplete PM with the reason. Joint Commission PM completion on high-risk equipment is a common finding. Fieldproxy runs an SLA clock per contract, escalates before a breach, and counts completion per device, with Not completed as a status that carries a reason.
source: Texas Tech University HSC, biomedical equipment maintenance solicitationsource: VA solicitation 36C26026Q0785, biomedical PM and service supportsource: ACCE webinar, Joint Commission 2026 Physical Environment standards
Every safety test tied to a calibrated analyzer
AIMS interfaces with Ansur, BC Group and Datrend test devices, which is a real strength. What an ISO also needs is a register of its own analyzers. In Fieldproxy each analyzer has a serial, assigned tech, calibration due date and certificate, the test form makes the tech pick the analyzer, an overdue one can't be picked, and if one comes back out of tolerance you can pull every test it ran.
source: AIMS, Interfaces (test devices, ECRI, parts, ServiceNow, ERP)
Invoicing the hospital, and AI on your own data
A hospital CMMS is not built to bill the hospital. Fieldproxy invoices contracts plus out-of-scope repairs and parts at contract rates, synced two-way to QuickBooks, Xero or Sage. AI agents can take service calls, chase depot quote approvals and flag a high-risk PM still open late in the month, and our MCP server lets Claude, ChatGPT or Copilot read your data and act, with a person confirming each change.
Stay on AIMS if
- You work inside a hospital that runs AIMS, and its HTM lead wants your PMs and repairs in its system. The hospital owns the inventory and the survey binder, so keep entering work there.
- You run a full in-house HTM program for one large client, on its AIMS. That is the job AIMS was built for.
- You depend on AIMS's interfaces: ECRI Sourcebase, UMDNS and Alerts Tracker, PartsSource, Medigate, Asimily, Palo Alto Networks, ServiceNow, or Lawson, McKesson and PeopleSoft for purchasing. Check each one you use before you move.
- Your IT rules require on-premise hosting. Phoenix offers its own cloud for a monthly fee or the client's server with a Phoenix team managing it.
- You need a vendor that makes compliance claims about its software. We don't: Fieldproxy records the evidence your clients' programs ask for, and the compliance call stays with them.
Before you go
What to export from AIMS, and how
Phoenix describes an AIMS Import Tool that exports equipment, PM schedules, work orders and their labor and material lines to Excel. For anything else, ask Phoenix in writing for a CSV, and ask how long the data stays readable after you leave. If the AIMS instance belongs to a client hospital, the export is the hospital's to give: ask its HTM lead for the devices you service, and keep what is yours.
| Data | How to get it out of AIMS | What happens to it in Fieldproxy |
|---|---|---|
| Equipment | Export from AIMS with the Import Tool to Excel: asset tag, serial, manufacturer, model, location, risk and warranty. | One device record per serial, per client, with risk flags, ownership and a QR label. Duplicates flagged by serial, models normalized for recall matching. |
| PM schedules (Scheduled Events) | Export with the Import Tool: interval, cycle type and last done date per device or type. | PM strategy per device type and client, manufacturer or AEM, with approver and date. Next due dates carried over. |
| Work order history | Export work orders with labor and material lines with the Import Tool. | History on each device, so a tech sees past repairs and PMs on the first scan. |
| Inspection results and readings | Ask Phoenix how inspection template results export; keep analyzer exports (Ansur and others) as files. | Attached to the device as history. New tests use your Fieldproxy forms with limits by class and applied part. |
| Your contracts with clients | Usually in spreadsheets or your accounting system, since AIMS contracts track what a hospital buys. Gather the signed contracts. | A contract record per client: coverage, scope, response terms, PM window rules and rates. |
| Parts inventory | If you use the optional inventory module, ask Phoenix for a CSV of parts, quantities and locations. | Parts and stock per van or depot, with purchase orders if you track them. |
| Test equipment | A plain list: analyzers, simulators and meters with serial, assigned tech, calibration date and certificate PDF. | A test-equipment register with calibration reminders; an overdue unit can't be used on a test. |
| Clients, sites and contacts | From the equipment export and your own client list: client, site, department, HTM contact. | Clients and sites, each with a scoped portal login for its contacts. |
source: AIMS, Core components (Scheduled Events, equipment, inspection templates, reports)source: AIMS, Optional components (contracts, inventory, dispatch center, offline mobile)source: AIMS, Interfaces (test devices, ECRI, parts, ServiceNow, ERP)
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.
Procedures and inspection templates as working forms
Inspection templates in AIMS capture readings, pass/fail answers and condition rankings. The template logic doesn't travel in an export. We rebuild each procedure per device type as a checklist with your limits, and keep the version and approver on it.
source: AIMS, Core components (Scheduled Events, equipment, inspection templates, reports)
Reports and dashboards
AIMS's Performance & Quality reports and dashboards stay in AIMS. We build each client's monthly report to the format that client asks for: high-risk and non-high-risk completion, incomplete PMs with reasons, repairs with response times, failed tests and open recalls.
source: AIMS, Core components (Scheduled Events, equipment, inspection templates, reports)source: AIMS, Optional components (contracts, inventory, dispatch center, offline mobile)
Interfaces
AIMS's links to test devices, ECRI, parts suppliers, ServiceNow and ERP systems stay with AIMS. List the ones you rely on, and agree in setup what replaces each: a file import, a Zapier flow, or a manual step. Accounting connects two-way to QuickBooks, Xero or Sage.
source: AIMS, Interfaces (test devices, ECRI, parts, ServiceNow, ERP)
Records that belong to the hospital
If a client runs its own AIMS, its inventory and history are the hospital's. You take a copy of the devices you service, with permission, and the hospital's system stays its record for surveyors.
Do these before you cancel AIMS
- Confirm, client by client, who owns each AIMS instance and whether the HTM lead wants your work entered there after the switch.
- If the instance is yours, find the notice period in your Phoenix agreement and ask in writing how long your data stays readable after you leave.
- Export equipment, PM schedules and work orders with labor and material lines to Excel, and keep the files.
- Save inspection results and analyzer exports for every device; surveyors can ask for past test records.
- Screenshot your inspection templates, PM cycles, report formats and dispatch priorities.
- Send each client's month-end report from AIMS before cutover, so no month's completion count straddles two systems.
- List every AIMS interface you use and agree what replaces it.
Send us your AIMS export and see it running in your setup.
Get DemoLive within a day
The move from AIMS, 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 team runs real work, not that every client moves at once. Large inventories with messy model names, many procedures or clients who need their own report formats add time, and we tell you on the first call.
What happens on go-live day- 1
Before the call: exports and one client
You, about an hour
Run the Import Tool export for one client. Pick that client for the parallel run, a month to cut over, and a first team. Gather that client's contract and your analyzer list. - 2
The call: one device, PM to invoice
You and Fieldproxy, 30 minutes
Walk us through a real month: how PMs are projected, a safety test on an infusion pump, a failed test and the repair, the emergency call, the month-end report and the invoice. Send the exports, procedures and one client report. - 3
We build your setup
Fieldproxy's team
Client contracts with response terms, device inventory per client, PM strategy per device type, procedure checklists, safety test forms with limits by class and applied part, the analyzer register, repair calls with timestamps, depot and loaner tracking, the client portal and the screens each tech and coordinator sees on the web and the Android and iOS app. - 4
We move your data, free
Fieldproxy's team and Fieldproxy AI
Devices, PM schedules and work order history, mapped and checked: duplicates flagged by serial, manufacturer and model names cleaned so recall matching works. We check device counts and next due dates against AIMS. - 5
We connect the books
Fieldproxy's team, with your bookkeeper
Two-way sync with QuickBooks Online, Desktop or Enterprise, Xero or Sage, checked against a real contract invoice and an out-of-scope repair with parts. - 6
Live: the first team on Fieldproxy
Day one
One team runs real PMs and repairs for the first client: scan the tag, pick the analyzer, enter readings, photos and signatures, offline in basements and imaging suites. Every other client stays as it is for now. - 7
One PM cycle, then client by client
Your schedule
Run the first client for one full PM cycle and compare completion and test records. Cut over at the start of a month, after the month-end report is out, then move the next client.
Cutover
Running AIMS and Fieldproxy side by side
For an ISO, โrunning bothโ often never fully ends: where a client runs its own AIMS, you may keep entering PMs there while Fieldproxy runs your company. The rules below keep that clean. Our view from moves we have run, not a sourced fact.
One system of record per client
For each client, agree in writing which system is the record: the hospital's AIMS, or Fieldproxy with reports and exports sent to the client. Where it is the hospital's AIMS, Fieldproxy holds your copy for scheduling, recalls and billing.
Cut over at the start of a month
A month's PM projection and completion count live in one system. Move each client after its month-end report has gone out, so no completion number straddles two tools.
A fixed switch-off date for your own AIMS
If you run your own AIMS instance, set the date it stops being used, after the last client has moved. Keep it readable for look-ups and surveys for as long as your agreement allows, then end it.
The fear
What if a survey or a recall lands in the middle of the move?
Surveys and recalls don't wait for a software change. Your clients need to show complete records and you need to find every affected device on the day it lands. This is how to stay ready throughout.
- 1
Old history stays readable
Past PMs and tests stay in AIMS, and the exports are attached to each device in Fieldproxy. Nothing a surveyor might ask for is deleted on cutover day. - 2
Recall search works from day one
Every client's devices are loaded with normalized models before the first team goes live, so a recall can be matched across all clients even while some still run in AIMS. - 3
Deadlines watched, not remembered
Agents can watch a high-risk PM still open late in the month, an emergency repair past its response time, an analyzer due for calibration, or an X-ray component repair without its Form FDA 2579, which is due within 15 days. - 4
Nothing goes out without approval
AI agents are off until you switch them on, and each can be set to ask before a report, quote or reminder goes to a client. Your data stays yours: export it, or read it through the API or MCP server, whenever you want.
Where things live
AIMS terms and where they go in Fieldproxy
So techs and coordinators know where things went on the first morning. The left column uses the component names on Phoenix's own pages.
| In AIMS | In Fieldproxy |
|---|---|
| Equipment records | Device inventory per client: serial, normalized model, risk flags, electrical class, ownership, QR label |
| Scheduled Events (PM scheduling) | PM strategy per device type and client, manufacturer or AEM with approver; PMs generated per device |
| Inspection templates | Procedure checklists and safety test forms with limits by class and applied part, and the analyzer used |
| Performance & Quality reports | Monthly report per client: completion by risk, incomplete PMs with reasons, response times, failed tests, recalls |
| Contracts management | Your sales contracts per client: coverage, scope, response terms, PM window rules, rates, renewal |
| Dispatch center and triage queue | Repair calls with priority, timestamps and an SLA clock per contract that escalates before a breach |
| Parts inventory and purchasing | Parts and stock per van or depot, with purchase orders if you track them |
| AIMS Mobile and the offline mobile app | Technician app: scan the tag, checklist, readings, photos, signatures, GPS check-in, offline, 27 languages |
| EasyNet web requests | Client portal and no-login links to request service, approve a depot quote or sign off work |
| Test device interfaces (Ansur, BC Group, Datrend) | Analyzer register with calibration dates; analyzer exports attached to the test record |
| Dashboards | Dashboards per client and for your own operation, plus scheduled reports by email |
Straight answers
Switching from AIMS: FAQ
How long does it take to switch from AIMS to Fieldproxy?
How do I export my data from AIMS?
Is migration from AIMS free?
Do I have to stop entering work in my client's AIMS?
Is Fieldproxy certified for Joint Commission or CMS compliance?
Does Fieldproxy work with QuickBooks, Xero or Sage?
Does the technician app work offline in basements and imaging suites?
Can Fieldproxy block AEM where it isn't allowed?
Can I use AI agents, Claude or ChatGPT with Fieldproxy?
Sources
Where the facts on this page come from
Every AIMS fact links to AIMS'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 medical equipment service companies.
- source: Phoenix Data Systems, AIMS home page (hospitals, users, equipment under management)
- source: AIMS, About AIMS (since 1984, AIMS 3)
- source: AIMS, Core components (Scheduled Events, equipment, inspection templates, reports)
- source: AIMS, Optional components (contracts, inventory, dispatch center, offline mobile)
- source: AIMS, Interfaces (test devices, ECRI, parts, ServiceNow, ERP)
- source: AIMS, Cloud solutions (hosted monthly or on-premise)
- source: CMS S&C 14-07-Hospital, hospital equipment maintenance requirements (AEM)
- source: ACCE webinar, Joint Commission 2026 Physical Environment standards
- source: 21 CFR 1020.30 (Form FDA 2579 within 15 days)
- source: VA solicitation 36C26026Q0785, biomedical PM and service support
- source: Texas Tech University HSC, biomedical equipment maintenance solicitation
Leave AIMS without the leap. Live within a day.
A 30-minute call about how a job runs in your business, and a AIMS 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.