PLM Upgrade & Modernization
Upgrade Your PLM. Leave the Customisation Debt Behind.
We take 3DEXPERIENCE, Teamcenter and Aras Innovator to a current release, on-premises or in the cloud, and use the upgrade to bring your implementation back toward standard.
3DEXPERIENCE · Teamcenter · Aras Innovator
Why Upgrades Get Deferred
Upgrades Stall on What Was Built, Not on the Release.
Years of custom code, workflows and integrations sit on the platform, and nobody has the full list. Without it, effort can’t be estimated — so the upgrade moves to next year again.
Vendor releases
Your release
What the gap costs
- Support ends
- Browsers move on
- Skipped releases add up
- New features wait
Three Platforms, Three Upgrades
The Same Word Means Different Work on Each Platform.
Dassault Systèmes C&SI partner
On-premises to 3DEXPERIENCE Cloud
3DEXPERIENCE Cloud runs Dassault’s baseline. On-premises JPOs, triggers and custom schema don’t move across as they are.
What we do
- Fit check against the cloud baseline
- Retire what current apps now cover
- Rebuild as widgets, web services or EKL
- Integrations onto published APIs
- Data migration and reconciliation
- On-premises release upgrades
Version upgrades · Active Workspace
Version upgrades and the move to Active Workspace
A Teamcenter upgrade is decided by what sits on it. We plan the version upgrade and the Active Workspace move so neither blocks the other.
What we do
- BMIDE and ITK review
- Rich Client to Active Workspace — only what’s used
- SOA, ERP and CAD integrations re-tested
- Workflows and access rules proven
- Teamcenter X readiness inventory
Aras partner — OEM, VAR, SI, since 2010
Upgrades where Aras’s own service doesn’t reach
Aras upgrades its subscribers. Unsupported releases, lapsed subscriptions and heavy custom code often fall outside that — that is where we come in.
What we do
- Release gap analysis with Rabbit
- Custom methods, forms and reports remediated
- Browser XSLT replaced
- Regression on the Test Automation Suite
- Every environment brought forward
Customisation Triage
Every Upgrade Should Make the Next One Easier.
An upgrade is the one moment everything that was built gets touched. We use it to bring the implementation back toward standard — one decision per customisation.
Retire
- Out of the box
- Unused
Reconfigure
- Configuration
- Not code
Rebuild
- Supported
- Upgrade-safe
Keep
- Tested
- Documented
How an Upgrade Runs
From Assessment to a Quiet Cutover.
The upgrade is built and proven beside production. Production is touched once, at a cutover you have already rehearsed.
Assess
Know the effort
- Customisation inventory
- Integration map
- Effort and risk
Decide
Agree the path
- Triage register
- Target release
- Cloud or on-premises
Build
Beside production
- Target environment
- Remediation
- Data migration
Prove
Before cutover
- Regression suite
- Business-process tests
- Data reconciliation
Cut Over
Production, once
- Rehearsal
- Rollback point
- Hypercare
Proven Modernisation
Upgrades We Have Delivered.
Each one is written up in full. Customers are described rather than named.
- 3DEXPERIENCEA North American FMCG manufacturer3DEXPERIENCE upgraded to 2015x with a custom solution letting users switch between indexed search and real-time search, so newly created data stayed reachable.Read the case study
- 3DEXPERIENCEA fashion retail customer3DEXPERIENCE upgraded from 2017x to 2021x alongside forty enhancements, with the upgrade’s data migration scripts re-engineered for concurrent execution across partitioned data.Read the case study
- 3DEXPERIENCEA German industrial equipment manufacturer3DEXPERIENCE upgraded from 2015x to 2018x, with the full CAD migration parallelised across multiple machines and completed inside one weekend.Read the case study
- 3DEXPERIENCEA UAE-based aerospace manufacturer3DEXPERIENCE upgraded from 2017x to 2021x and migrated from on-premises to an Azure private cloud, with the de-customisation the new version required.Read the case study
- 3DEXPERIENCEMTorres3DEXPERIENCE upgraded from 2017x to 2021x, then CATIA V5 data migrated from Designer Central to POWER’BY (UPS), with SmarTeam data migrated on demand.Read the case study
- Aras InnovatorA global tobacco manufacturerGovernance of a complex Aras migration alongside the customer’s IT team, with CI/CD implemented, access control built across the modules, and the platform upgraded from V14 to V28.Read the case study
- Aras InnovatorA world-leading European certification authority for marine vesselsEnd-to-end Aras implementation partner for a European marine certification authority — migrating 40 applications built in the late 20th century onto one platform, with functional, technical and data model architecture designed from scratch.Read the case study
Upgrade Readiness Assessment
Find Out What Your Upgrade Actually Involves.
We inventory what sits on your platform and come back with effort, risk and a recommended path.
FAQ
Frequently Asked Questions
Some can; most change shape. JPOs, triggers and custom schema aren’t carried across as they are. We check each customisation and decide whether current apps already cover it, whether configuration can replace it, or whether it is rebuilt as a widget, web service or EKL script. You see that list, with effort against each item, before you commit.
No. They are separate pieces of work, and the Rich Client still ships in current Teamcenter releases. Many teams upgrade the version first and move user groups to Active Workspace as their customisations are rebuilt.
On a supported release with a current subscription, Aras’s upgrade service may be all you need. We come in where it doesn’t reach: unsupported releases, lapsed subscriptions, and custom methods, forms and reports that need remediation.
Aras Innovator uses XSLT to render grids and reports. Chrome 158 removes it on 17 November 2026, and Edge follows. Releases 22 to 38 have an Aras hotfix; Release 21 and earlier need an upgrade. An enterprise browser policy keeps XSLT working until August 2027 — time to upgrade, not a way round it. On any release, custom code using browser XSLT needs checking.
It depends on what is built on the platform, not on the platform. The assessment gives you an estimate grounded in the customisation inventory — before you commit.
The upgrade is built and proven in a separate environment. Production is touched once, at a rehearsed cutover in a window you choose, with a rollback point.