What to Evaluate Before Replacing Legacy Office Equipment ERP

Most office equipment dealers do not fail a system project because they picked the wrong logo. They fail because they sat through demos before they defined the work the system has to do.

If you are replacing a legacy ERP, write the scorecard first. Clean customers, serials, contracts, and item masters second. Then watch a live flow with your data: a service call, a contract invoice, an inventory move, a customer record that sales and service both use. If the vendor cannot show that path without another product taped on, you are still in a slide deck.

That sequence is the difference between a software purchase and a business-process project that happens to include software.

Why dealers replace the system they already know

Channel systems get replaced for a short list of reasons, and they rarely start with “we wanted a modern screen.”

• The architecture is closed. Every new need becomes another connector, spreadsheet, or paid custom.
• Service, inventory, contract billing, and customer records do not share one operational picture.
• Adding an online storefront, device data, or another location means another application.
• Support is slow, or the people who still know the old customizations are leaving.
• Seat-based licensing gets expensive as soon as technicians, warehouse staff, and customer-facing users all need access.

Those are selection problems discovered late. Panorama Consulting Group’s 2026 ERP Report  (170 respondents, median project about 9 months, median revenue about $200.5 million) found that more than a quarter of projects ran over budget. Coverage of the same report puts the over-budget share near 30%. The most common budget cause was the unexpected need for additional technology, usually a misfit found after selection, which then becomes extra software, extra scope, and extra custom work. Schedule slips were driven more by organizational issues than by code. Fewer than 25% of respondents put intense focus on change management.

Dealers feel that pattern as a “we’ll connect billing later” promise, a report that still lives in Excel, or a second product for service.

What the system has to do in a dealership

Generic mid-market checklists talk about the general ledger and inventory. That is necessary and not enough. Score any platform against the work that actually runs an office technology business.

Should live in one system of record, not in a sidecar

1. Service management tied to the customer and the installed equipment.
2. Inventory that service, warehouse, and sales can trust.
3. Contract billing that uses the same customer and equipment records as service.
4. CRM that is not a separate island from orders, service, and invoices.
5. An online storefront or customer portal that uses the same items, prices, and accounts as the ERP – the difference between a website and a connected revenue channel, which we covered in Connected ERP and eCommerce Workflows.
6. Room to connect device data and other systems through open interfaces, instead of another closed stack.
7. A licensing model that does not punish you for putting technicians, warehouse staff, and partners in the same system.

If a vendor can only show financials plus a generic work order, you do not have a channel system. You have accounting with a service brochure.

In The Cannata Report’s 40th Annual Office Technology Dealer Survey (October 2025), 45% of 415 dealers – 187 shops – said they planned to buy another dealership or service company in 2025 and beyond. If growth by acquisition is even on the table, ask how customer, contract, and item data would move into one set of books. That is a conversion question, not a logo question. If that purchase closes, the hard part is not the signature. It is two customer files, two serial histories, and two dispatch boards still running 90 days later. That is the operating problem we covered in What Breaks When Office Technology Dealers Acquire Each Other.

Clean the data before you migrate it

Gartner still publishes the enterprise figure that poor data quality costs organizations an average of $12.9 million a year, and that 59% of organizations do not measure data quality. A mid-size dealership will not lose $12.9 million. It will lose the same shape of money: disputed invoices, duplicate customers, techs rolling without the right part, and reports nobody trusts.

Aquant’s 2025 Field Service Benchmark Report (157 service organizations) puts median first-time fix at 75% across industries and 77% in printing. The top 20% reach 86%. The usual gap is not technician skill. It is parts and information at the point of work.

Before any conversion, assign an owner to four files:

• Customers and sites – one record the CRM, service, and billing teams can share.
• Serials and equipment – live devices mapped to the customer and the contract.
• Contracts – terms that finance actually invoices, not a copy in a folder.
• Item masters – the SKUs that warehouse, service, and any storefront already use.

A dirty file in a new system is still a dirty file. It just costs more to correct after go-live. Dirty item data is its own project; see LLM Copilot for StockItems Data Hygiene for why the catalog has to be clean before anything downstream works.

Hidden cost drivers that do not show up on the license quote

Third-party 2026 implementation guides often publish mid-market year-one planning ranges. Treat those as industry context, not a quote for any one platform. Your number follows data cleanup, integrations, training, and whether service, inventory, contract billing, and CRM already sit in one product.

The line items that surprise dealers are usually not the subscription.

• Integrations nobody listed in the first conversation: leasing, distributors, storefront, device data, tax, shipping.
• Seat-based licensing that looked cheap until every technician, CSR, and warehouse clerk needed a login.
• Reports you currently pay someone else to run, which you assumed were “in the system.”
• Data migration hours. Cleaning serials, contracts, and items is not a weekend import.
• The extra product required when service, billing, inventory, or commerce is not part of the same platform.

Panorama’s top overrun cause, unexpected additional technology, is this list with a purchase order attached. That is the same pattern described in ERP Integration Debt and the Hidden Cost of Workarounds.

A scorecard to take into the demo

Print this. Score each row Must / Nice / Not needed, then Yes / Partial / No after the demo. Partial means “yes, with another product or a custom.”

Decision rule: if rows 13 and 14 are not a clean Yes on your data, stop. You can keep shopping. You should not keep negotiating.

How to run the evaluation without getting lost in demos

1. Write the scorecard with operations, finance, and service in the same room. If they disagree on “must,” you are not ready for vendors.
2. Give every vendor the same three scenarios and the same sample file: one contract, a set of serials, one messy customer.
3. Count the extra products. A platform that needs add-ons to invoice, run service, keep inventory, and sell online is not simpler than the system you have. It is a new integration map.
4. Price the work over several years, not year-one software only: services, integrations, users as the team grows, and the reports you cannot live without.
5. Ask who owns the data if you leave, and whether your team can report without a gatekeeper. If the answer is vague, treat that as a risk.
6. Budget time for people. Panorama’s schedule overruns were organizational. A project that ignores dispatchers and technicians will make the same list.

Staying on a system that cannot do the work has a cost too. That is a separate decision from which platform replaces it. See Doing Nothing Costs More: Legacy Systems Hold Business Back if the question is still whether to move at all.

Open architecture, cloud deployment, and the ability to adapt the system without a closed vendor queue belong in the same evaluation. Those themes are covered in Open Architecture ERP for Office Tech Dealers, Why Cloud ERP Reduces IT Costs and Infrastructure Risk, and The Technical Benefits of No-Code/Low-Code ERP Platforms.

How you will know the project worked

Not “we went live.” Use operating tests for two quarters:

• Time from contract activity to a clean invoice, and the dispute rate on those invoices.
• First-time fix versus your current baseline (printing peers sit near 77% in Aquant’s 2025 set).
• Service calls that stall because inventory in the system does not match what is on the shelf.
• Time to add another location or acquired book without standing up a second stack.
• Number of spreadsheets that still sit between service, inventory, and billing.

If those numbers do not move, you changed software. You did not change the business.

Replacing a dealer system is a process project. The vendors that look best in a polished demo are not always the ones that can run service, inventory, contract billing, and CRM on the same records, and still connect a storefront or device data without another stack. Write the scorecard first. Clean the files second. Watch the live flow third. Put every extra product on the same page as the license. That is how you avoid becoming another “unexpected technology” line in next year’s implementation survey.

FAQ

How long does a mid-market ERP replacement take?

Panorama’s 2026 report puts the median project at about nine months across its respondent set. Dealer timelines follow data quality and how many extra applications you are retiring. Plan the cleanup of serials, contracts, and items as its own phase.

What should we budget for?

Ask each vendor for software, implementation, integrations, training, and five-year access for the people who will actually use the system. Industry planning articles publish wide mid-market ranges. Use them only as a reason to demand a line-item proposal, not as a price for any one product.

Should we keep the old system running next to the new one?

Only as a temporary source during conversion. Two live ERPs after go-live recreate the problem you are paying to leave.

What should we send vendors before a demo?

The scorecard, three scenarios, and a sample of real (anonymized) contracts, equipment, and items. If they will only show their own sample company, you have not tested fit.

Does “industry-specific” guarantee a better fit than generic software plus add-ons?

No. It is better when service, inventory, contract billing, and CRM share the same records. It is worse when “industry-specific” still means three products connected after the fact. Score the flow, not the category label.