If you run Visual Shop or Bluestreak, you now have a deadline
Two of the small number of ERP systems built for heat treat now have published end dates.
Steelhead Technologies has acquired Visual Shop and Bluestreak. Both products are being retired, and Steelhead has said so plainly on its own announcement pages:
- Visual Shop is supported until the end of 2027.
- Bluestreak is supported through June 30, 2028.
In both cases the wording is the same: “All AI and product development will be focused on the Steelhead platform.” Existing customers are offered a white-glove migration onto Steelhead, with incentives for moving early, and no immediate change to billing.
None of that is hidden, and none of it is unusual. Software companies buy other software companies. What is worth sitting with is the arithmetic it creates for a shop that did nothing wrong and made no decision.
The deadline is real, and it is not yours
If you run Visual Shop, you have roughly sixteen months of support left. If you run Bluestreak, roughly twenty-two. After that the software you run your floor on is retired.
You will replace it. The only open questions are when, onto what, and how much of your history comes with you. Those are the three questions you normally get to answer on your own schedule, and this time the first one has been answered for you.
That is the part that matters. Not that a competitor bought a competitor — that is ordinary — but that the timetable for a decision this size now belongs to someone else’s roadmap. A migration you choose is a project. A migration you are given a date for is a scramble, and scrambles are where records get lost.
Two vendors became one
There were never many systems that understood a load, a pyrometry interval, or why a certificate is the actual deliverable. There are now fewer.
That is a real change in the market, and it is worth naming without exaggerating it: consolidation is not a conspiracy, and Steelhead has been straightforward about the dates. But the practical effect for a shop evaluating options in 2027 is a shorter list, and a shorter list is worth knowing about before you are standing on a deadline.
The thing actually at risk is your evidence
Here is what a heat-treat shop should be worried about, and it is not the user interface.
Your system holds SAT and TUS records going back years. It holds instrument calibration history, thermocouple lots and their expiry, load records with the cycle each one ran, hardness results, and the certificates you issued against all of it. Under AMS 2750 and an AC7102/8 audit, that history is the compliance position. It is not reporting. It is evidence.
When a system is retired, that evidence has to move — into a new system that models the same things, or into an export that somebody can still read and defend in 2031 when an auditor asks about a load that ran in 2024.
So the migration questions worth asking now, while you still have time and therefore leverage:
- Can I get a complete export, on my own, without asking? Not a report. Every record, in a documented format, on demand.
- Does the destination model pyrometry as records with dates and intervals, or as fields on a furnace? The difference decides whether you can still answer “was this furnace in compliance on the day this load ran” three years from now.
- What happens to the certificates I have already issued? They were signed. They should stay immutable and readable, not become rows in a new schema that has drifted.
- What is the as-of-date behaviour? If a calibration is recorded next year, does last year’s load still show the calibration that was in force when it ran — or does it silently show the current one?
- What does the price look like in year three, after the migration incentive has expired and switching again means doing all of this a second time?
Question four is the one people skip and regret. A system that overwrites history rather than preserving it will pass every demo and fail the one audit that matters.
Our position, stated plainly
We build a competing product, so read this with that in mind.
We think the right answer to all of the above is that your data should never be the thing that keeps you. HeatLock exports everything it holds, and the records that constitute an audit position — pyrometry, load actuals, issued certificates — are stored as immutable, dated records precisely so that they can be reproduced as of a past date. That design is there for auditors, but it has the same effect for leaving: nothing is trapped in a shape only we can read.
We would rather earn the renewal than hold the data.
If you run Visual Shop or Bluestreak, you do not need to decide anything today. You do need to start asking, while a deadline is still eighteen months away rather than eighteen weeks.
We have written up what actually has to move, and what migration really costs — including an honest account of the part no vendor puts on a slide.
Sources: Steelhead Technologies’ own announcement pages for Visual Shop and Bluestreak, as published and accessed on 8 August 2026. Dates and quotations are theirs; if they change, this post is the stale one.