(Including SolidWorks Support For SLW)
Why Migrate Out of ENOVIA SmarTeam?
- The future of ENOVIA SmarTeam is uncertain, and companies should prepare for potential obsolescence.
- SmarTeam was built on older architecture, making it difficult to scale with evolving business needs.
- Newer SOLIDWORKS releases and service packs may not fully integrate with SmarTeam, leading to workflow disruptions.
- Modern PLM systems offer advanced features that SmarTeam struggles to keep up with.
Note: Many customers are still using and expanding SmarTeam and receiving an ROI on it. Though companies should also be proactive and look into other systems as well
Considerations for Migrating from ENOVIA SmarTeam to 3DEXPERIENCE
How will 3DEXPERIENCE be implemented?
- Will it follow the 3DEXPERIENCE out-of-the-box (OOTB) data model?
- Will it use a custom data model similar to ENOVIA SmarTeam?
- Should we rethink and optimize how best to deploy the new system?
What data is in scope for the migration?
- Documents, folders, BOM, workflow history
Data mapping and transformation considerations:
- Converting and mapping data from ENOVIA SmarTeam to 3DEXPERIENCE
- Managing unique names and serialization of migrated data
- Merging multiple ENOVIA SmarTeam attributes into a single 3DEXPERIENCE attribute
- Consolidating multiple ENOVIA SmarTeam classes into one 3DEXPERIENCE type (or vice versa)
- Adjusting attribute types and revision schemas during migration
Cutover plan:
- Are there any downtime restrictions for the migration?
- Will data access be required during the migration?
- Are users trained and prepared for the transition to 3DEXPERIENCE?
xLM’s ENOVIA SmarTeam to 3DEXPERIENCE Migration Solution Objectives
- Deliver a proven methodology for seamless data migration
- Accommodate different data models between ENOVIA SmarTeam and 3DEXPERIENCE
- Enable future growth with 3DEXPERIENCE functionality, avoiding migration roadblocks
- Ensure migrated data appears native in 3DEXPERIENCE, maintaining usability and integrity
- Execute large-scale migrations efficiently, typically within a weekend timeframe
Migration Highlight Features
- Full history migration – Including documents, items, and custom classes from ENOVIA SmarTeam
- Data model adaptation – Seamlessly transition ENOVIA SmarTeam projects and folders into 3DEXPERIENCE workspaces and folders
- Advanced mapping capabilities – Type, state, attribute, and reference conversions, including lookup tables
- CAD (SOLIDWORKS, CATIA, Inventor, SolidEdge, etc.) integration support – Creation of instance, family, and version objects in 3DEXPERIENCE
- Workflow history migration – Including ENOVIA SmarTeam WorkFlow objects (e.g., ECOs) as 3DEXPERIENCE document objects
- Optimized performance – ENOVIA SmarTeam remains the master source, eliminating file processing delays
- Validation & post-processing – Ensures data integrity and system readiness after migration
Typical Migration Steps
- Toolset Configuration
🔹 Pre-migration data analysis – Validate file name uniqueness and data integrity
🔹 Migration solution setup:
- Map ENOVIA SmarTeam classes to 3DEXPERIENCE types
- Map fields, attributes, and lifecycle states
- Align ENOVIA SmarTeam folders/projects with 3DEXPERIENCE workspaces
- Implement customer-specific migration rules
- Data Extraction & Import
🔹 Export data from ENOVIA SmarTeam
🔹 Import into 3DEXPERIENCE, following structured mapping and transformation
- Customer Test Environment
🔹 Install, configure, and validate the migration tool in 3DEXPERIENCE test environment
🔹 Perform test runs, review logs, and fine-tune settings
🔹 Validate sample test results before proceeding to full migration
- Production Migration & Cutover
🔹 Align on final migration date
🔹 Execute full data migration to 3DEXPERIENCE production environment
🔹 Perform post-migration validation to ensure accuracy
SmarTeam to 3DEXPERIENCE Migration Challenges and Solutions
Requires a company with both SmarTeam and 3DEXPERIENCE programming capabilities, data model and database understanding, application understanding and business processes.
xLM has all of these capabilities.
SmarTeam data extraction techniques using API scan be slow when dealing with large data sets.
xLM has developed a methodology to extract SmarTeam data without using API which will avoid such issues.
With any database system there may be data integrity issues.
xLM will report any “bad data” before and during the process of data extraction.
SmarTeam data may need to be cleaned to avoid possible migration issues such as duplicate names corrupted data in the database , etc.
xLM can assist in both identifying the issue, recommend a solution and possibly implement a fix if it is a low level Smarteam corruption (result of bugs, bad customization, etc.).
Every SmarTeam and 3DEXPERIENCE customer will most likely have different data models.
xLM’s SmarTeam to 3DEXPERIENCE migration Solution can be configured to handle the different data models. The Solution will follow a 60/40 rule— it can handle 60% of the migration out of the box and the remaining 40% will involve configuration of the toolset for the specific customer implementation.
SolidWorks integration data model is completely different between SmarTeam and 3DEXPERIENCE. No easy way to "nvent" missing 3DEXPERIENCE objects to support the SolidWorks Integration (SLW)
xLM develop and proprietary algorithm to migrate and create necessary data in 3DEXPERIENCE to support full history migration of SoldiWorks data as well as support for 3DEXPERIENCE SoldiWorks Integration (SLW).
Merging multiple SW classes in SmarTeam to Single type (assuming SLW OOTB)
xLM has developed the methodology to accomplish that as well as tools and DB queries to do that.
Migrate items as engineering parts in 3DEXPERIENCE and support future EBOM synch in 3DEXPERIENCE
xLM has developed the methodology to accomplish that as well as tools and DB queries to do that.
Migration Down Time may be an issue for some customers
By using direct DB extraction from SmarTeam makes the migration tenfold faster than using smarTeam APIs to extract data.
