Visual Shop and Bluestreak after the Steelhead acquisition: what to ask before you migrate

On July 29, 2026, Steelhead Technologies announced it had acquired Visual Shop and Bluestreak, the two longest-standing shop management systems in metal finishing and heat treating. It followed an $84 million growth investment from Mainsail Partners in December 2025. The stated plan is consolidation into one unified platform covering MES, QMS, ERP, financials, and customer service.

Over 350 plants run Visual Shop. Bluestreak has its own installed base across heat treating, plating, and coating. If your shop is one of them, this article is for you, and its advice fits in one sentence: nothing requires you to act this month, but everything rewards you for asking your questions now, before a migration date exists, and getting the answers in writing.

What was actually announced?

Three facts matter more than the press language.

First, the acquirer is well regarded. Steelhead built a serious all-in-one system for finishing shops, its customers on Capterra consistently praise the deployment experience and the job costing visibility, and its stated deployment time is weeks rather than the industry's usual months. This is not a distressed asset sale. It is a funded company executing a consolidation plan competently.

Second, the plan is a unified platform, which means the product you run today is now a legacy line inside somebody else's roadmap. The candid quote in the announcement came from Kevin Pluedeman of Cornerstone Systems, which built Visual Shop: to stay competitive long term, they would need to build a new product on a modern platform. If you are a Visual Shop customer, that sentence is about your install.

Third, nobody has published a timeline. That is normal this early, and it is also exactly why this is the right moment to ask. A vendor mid-integration has strong reasons to keep migrating customers happy, and you have more leverage before you have agreed to anything than at any point afterward.

What does consolidation usually mean for the product you run?

Not an accusation, just the mechanics, because they are the same in every roll-up regardless of who runs it.

Acquired products get maintained, then maintained less, then migrated. The people who knew your specific configuration take new roles or leave. The roadmap starts serving the platform strategy, and the smallest customers are served last. Renewal pricing tends to move up, not down, because the investment thesis requires it. None of this happens on day one, and some of it may not happen here at all. But planning on the assumption that a platform migration is in your future is not pessimism. It is what the announcement says in its own words.

The failure mode to avoid is the passive one: waiting until the migration email arrives with a date in it, then making a platform decision for the next decade in ninety days, during your busy season, with no answers in writing.

What should you get in writing first?

Ask by email, not on a call. A verbal reassurance is worth nothing in eighteen months when the account team has turned over. Send the questions, date the answers, keep the thread. If a vendor will not put an answer in writing, that is itself the answer.

The support horizon comes first, because every other answer depends on the clock:

• What is the committed end-of-support date for the version we run today? "No plans to sunset" is not a date.
• Will we keep receiving bug fixes and security patches until then, or only critical fixes? Maintenance mode usually arrives quietly, years before end of support.
• How much notice do we get before a migration becomes mandatory?
• Can we stay on the current product indefinitely if we choose, and at what cost? Sometimes the answer is yes at a premium, and it is rarely volunteered.

Then the cost, and not the license fee, which is the knowable part:

• What is the one-time migration cost in dollars, quoted for our shop, not a range?
• How many hours of our staff's time does it consume, and from which roles? It is usually the owner, the office manager, and the lead who knows the routings, your three least replaceable people, during weeks the shop still has to ship.
• How long do we run both systems in parallel, and who does the double data entry?
• If the migration overruns, who absorbs it? Ask for the overrun clause specifically. Most contracts are silent, which means you do.

What happens to your data and your quality records?

This is the section most shops discover too late, because if your certs and travelers live in the system being replaced, your audit evidence is migrating too.

• Can we export our complete dataset today, in an open format, without vendor help? Ask them to prove it with a test export this month, not describe it.
• Which history migrates and which does not? Job cost history, old quotes, and closed work orders are the usual casualties, and they are what you price repeat work from.
• Do certs, travelers, and inspection records carry their full audit trail: who signed, when, against which revision? A record without its trail is not evidence, and auditors ask for the trail.
• Will the new platform satisfy our Nadcap, AS9100, ISO 13485, or ITAR obligations without requalification? Name your accreditations in the question. A generic "we're compliant" does not cover your scope.
• Has the vendor supported a Nadcap audit on the new platform at a shop like ours, and can we speak to that shop by name?
• Do customer-specific approvals and process specs carry over, or are they rebuilt by hand? Rebuilt by hand means re-approved by your customer, and that is a schedule risk your buyer will hear about.
• How do gauge calibration records, SPC data, and rectifier or furnace data migrate? Instrument data is frequently out of scope by default.

And the part every consolidation trades away: Visual Shop was built to be customized per shop, and a unified platform is the opposite bet. Ask for the gap list in writing, which features you use today have no equivalent, what happens to your custom reports, and whether your customers will notice anything change: portal, cert format, invoice layout. Anything your customer receives is a document their receiving department was trained on.

What leverage do you have right now?

More than you will ever have again, because the vendor needs the installed base to move willingly and to say good things about the move.

While that is true, negotiate the terms that outlast the migration: year one, two, and three pricing on the new platform, not just the migration-year number, which is often introductory. A cap on annual increases, in the contract, which is the single most valuable clause available to you this year. And what the price does when you add users, a second shift, or a location, because per-seat models quietly tax your own growth.

If the answers come back solid, migrate with confidence. Plenty of shops should, and a shop that works through all of this and lands on Steelhead's platform has made a good decision with dates and numbers behind it instead of an assurance. The shops that get hurt are the ones that never asked.

Where does BrixIQ fit in this, honestly?

BrixIQ is the operating system for job shops: machine, plating, coating & finishing. We compete with Steelhead for some of your budget, so weigh this article accordingly. We wrote it anyway because the questions are the same whatever you buy.

The specific thing worth knowing while you weigh a platform decision: the pain that sends most finishing shops software shopping is not the floor system, it is the front office. RFQs wait while somebody figures surface area off a print by hand. Certs take half an hour to find. Invoices go out missing the document their customer's AP match requires. BrixIQ reads the customer's drawing, prices it against your rates including the area math, and hands your estimator a drafted quote to approve, then carries the same record through the PO, the cert, and the invoice. One shop's own measurement, from Anodizers Inc, stated as one shop's numbers rather than a benchmark: RFQ research and quote creation went from two people at one to two hours per quote to one person finishing in under five minutes.

None of that requires a platform migration, which is the point of raising it here. It is $995 per facility per month with unlimited users, shops are live in days, and there is nothing to undo if your platform decision later takes you somewhere it does not fit.

Common questions

Should we leave Visual Shop or Bluestreak now?

No. Nothing in the announcement makes your system worse this quarter, and panic-switching is how shops end up in a second bad migration. The move is to ask the questions above now, in writing, and decide on a timeline you chose instead of one you were handed.

Is Steelhead's platform a bad destination?

By its customers' own accounts, no. The reviews are strong and the deployment speed is real. The argument here is not against Steelhead. It is against migrating anywhere without the support horizon, the cost in your people's hours, the data and quality-record answers, and a price cap in writing.

Can BrixIQ replace Visual Shop as our system of record?

For some shops, yes. BrixIQ connects to an existing system of record, reads from it and posts back to it, or serves as the record itself: job and work order tracking, inventory and purchasing, scheduling and capacity, and job costing. Which path fits depends on what your floor needs, and a demo on your own drawings settles it faster than a feature list.

We run Bluestreak for Nadcap heat treat. Does the quality side carry over?

Ask Steelhead the audit-trail and requalification questions above, and ask for a heat treating reference that has passed a Nadcap audit on the new platform. On the BrixIQ side, certs, operator stations, gauge data, and SPC are part of the platform and tied to the same job record as the quote and the invoice.