I’ve helped hundreds of companies make the transition from their old CAD systems to modern CAD and one of the most frequent questions I hear is: “But what do we do about our legacy data? I’d love to switch over to Onshape, but we have YEARS worth of old CAD files to deal with.”

I’ve talked with engineering leaders who love Onshape’s advanced modeling tools, universal accessibility and built-in data management, but still wonder, “Oh my God, how would I close up on Friday from my SOLIDWORKS® workstation and then show up on Monday with a MacBook and do everything in Onshape?”

The answer: You don’t.

For brand new startups or companies launching a new category of products, working from a clean slate in Onshape is easy. But some engineering leaders who have been working with and managing SOLIDWORKS for years might initially feel frozen in their tracks. I get it. Changing CAD systems doesn’t feel like replacing an old pair of jeans. For many, it can feel like changing your religion.

Practically speaking, however, it’s not really that complicated. If you have lots of old CAD files and want to switch to Onshape, there are two strategies most companies follow successfully:

  1. Run Two Systems at Once – This is the “it’s not a light switch, it’s a dimmer” approach. It’s employed by larger, more mature companies (the ones that probably still have a license of AutoCAD kicking around from 1998), but also works for younger companies that prefer to take a slower, more pragmatic approach to modern CAD. For minor revisions of old projects and supporting stable products that have shipped, it’s simple: Do those in SOLIDWORKS. Is it a new project? Is it one that’s going to take significant engineering time? Great! Import the necessary existing data into Onshape and take advantage of the many benefits of modern CAD. There is no better time than now to stop paying for the upgrades you don’t really care about and the support you don’t need from your VAR.
  2. Import Everything Into Onshape and Translate on Demand – This is the equivalent of digitally scanning your entire archive of paper files. Whether this makes sense for your company depends on a couple factors. The companies who choose this route are usually at an earlier stage when they don’t have a lot of legacy data to manage. But these are also companies that never wanted to have a server in the first place, and SOLIDWORKS is the only locally installed software they’ve needed to get their job done (G-Suite, Office365, Salesforce.com, Slack, SOLIDWORKS – one of these things is not like the others!). You also might be taking this path because you feel your CAD provider is holding your upgrades hostage with a PDM upgrade you’re forced to pay for, whether you want it or not. Yes, I’m thinking about you, Workgroup PDM users.

There’s a third option: Do nothing. Hold back your design team from the latest and best tools because all your old work is being held prisoner by your old system. Of course, that’s not a winning strategy. Standing still is the equivalent of moving backwards when your competitors seek to seize every advantage they can.

Most Transitions Take Time

Heuresis engineer Howard Kellogg says he no longer has to worry about file corruption or crashes with Onshape. “When you’re recreating work, you’re not moving forward,” he says.

Let’s take a look at a company that recently switched to modern CAD and see how they handled their legacy data.

Based in Boston, the Heuresis Corporation makes handheld X-Ray imaging devices that allow law enforcement to more easily find illegal drugs, weapons and contraband in hidden compartments inside buildings, furniture, appliances, vehicles, luggage and other objects. The equipment allows police to detect contraband without having to destroy property. Heuresis also manufactures a handheld lead paint analyzer that helps safety inspectors more efficiently find hazardous materials.

Heuresis, which previously used SOLIDWORKS, decided to do all of its new product design in Onshape, but is keeping one seat of SOLIDWORKS around so it can access legacy parts that may possibly be used in new products.

“We originally envisioned migrating all of our legacy data into Onshape, but it doesn’t make sense for us,” Heuresis engineer Howard Kellogg says. “Instead we’re just importing legacy files or recreating them on a case-by-case basis. Using this approach, we’ve found the transfer process to be very straightforward and easy.”

“The vast majority of our legacy parts have been released and we don’t anticipate making any changes. We might have to change a few things here or there, but we feel comfortable making a clean break. Everything we develop for now on will be done in Onshape.”

“Onshape is just so much more stable than our previous CAD system,” he adds. “You don’t run into problems where individual files get corrupted. You don’t have to worry about file names getting messed up or if you saved over the autosaved version. The old way was just a mess that would take away from being able to just focus on product development,” he says.

The big takeaway is that there is no such thing as an instant transition. Your business is in it to succeed in the long haul, and modern CAD will improve your processes to help you get there. It’s worth repeating that switching CAD systems is not so much flipping a light switch, but is more like using a dimmer. There’s different transition speeds for different companies, but ultimately, every modern CAD user’s future will be much brighter!

Migration Station

Find everything you need to know about
transitioning from SOLIDWORKS to Onshape.