Data Migration Services
TriMech provides Data Migration Services for both new and existing SOLIDWORKS PDM users, offering refined service levels and tools developed by a dedicated programming team to ensure efficient and secure data migration, meeting evolving client needs.
Our commitment is to deliver top-notch service and a superior migration experience.
TriMech Service
Data Migration Services Benefits & Capabilities
- Minimize downtime by ensuring a 98% success rate file import, utilizing migration validation, addressing missing SOLIDWORKS file references, and continuing the migration despite encountering corrupt files.
- Address file duplication by identifying duplicate files by name or digital fingerprint using our specialized tools.
- Increase adoption by automatically capturing file properties and references in your new vault environment.
TriMech's Migration Services and Feedback
TriMech is committed to providing detailed feedback during the process, reducing migration time, and preventing errors that slow down the process.
Data Doctor - Data Analysis
Service Definition - Customer Input to Define Service Parameters
Testing and Validation - All Data Services Include Client-led Validation
Go Live Execution - Your Vault is Ready to Use
Data Migration Systems
Choose between our migration service packages based on your specific needs.
The standard-level system is designed to meet the basic needs of customers migrating data from Windows Explorer or SOLIDWORKS Workgroup who desire limited clean-up of their data.
Data Source
The Data Transition Service can migrate from a single source either from Windows File Explorer or SOLIDWORKS Workgroup PDM.
Project Guidance
The Data Transition Service includes structured project guidance provided by a dedicated technical resource assigned to your engagement. Throughout the project, our team maintains regular communication, provides updates at key points, and clearly communicates next steps and client responsibilities to support steady progress from start to completion.
Property Mapping
Property mapping Up to 15 properties from SOLIDWORKS files or AutoCAD attributes can be mapped to PDM Variables. All existing properties in files will be maintained.
File De-duplication
SOLIDWORKS CAD, DWG, and DXF files identified as duplicates, either by matching file names or by identical digital fingerprints, can be addressed using configurable de-duplication options provided as part of the service.
Service Timeline
When delivered alongside our Rapid Deployment SOLIDWORKS PDM Implementation, the Data Transition Service forms part of a comprehensive transition to SOLIDWORKS PDM. From service kickoff through go live with your new vault, the combined project delivers vault setup, user and administrator training, and data migration within an overall timeline of approximately nine to twelve weeks.
TriMech's Data Migration Matrix
Explore our Data Migration System Packages
| Requirements | Data Transition Service | Data Migration Service |
|---|---|---|
| Data Source | Single source, either Windows Explorer or SOLIDWORKS Workgroup PDM | Data can be migrated from any source(s) including existing document management systems |
| Functional Groups1 | Single group | Single or multiple groups supported |
| Destination Vault Type | SOLIDWORKS PDM Standard SOLIDWORKS PDM Professional | SOLIDWORKS PDM Standard SOLIDWORKS PDM Professional |
| Pre-existing PDM Vault destination supported | No | Yes |
| Access Requirements | Attended access via remote web meeting (eg: Teams) | Supports Attended or Unattended access as well as environments requiring elevated security requirements |
| Project Management | Basic Project Guidance | Detailed project plan creation, dedicated Project Management resource, weekly project status update meetings and reports available |
| Total Number CAD files2 | 50,000 (Maximum 100,000 Workgroup versions) | Unlimited |
| Total number of Non-CAD files | Unlimited | Unlimited |
| Non SOLIDWORKS 3D CAD Files | Included as “dumb” files only | Some additional file types can be fully processed, capturing reference structure and properties |
| Service Completion Time | Approximately 9-12 weeks for combined implementation and migration services. | Varies depending on data source, conditioning requirements, and the client’s validation testing schedule |
| Project Management3 | Data Transition Service | Data Migration Service |
|---|---|---|
| Project Coordination | Technical resource only | A dedicated project manager can be included to oversee and coordinate the project |
| Project Plan | Project follows a standard service plan | A detailed project plan can be developed as part of project initiation |
| Project Status Update Meetings | Dedicated status meetings not included. Status updates are communicated through working session and direct coordination as needed to support progress | Structured status meetings available to review progress, upcoming work, and any open risks or dependencies requiring coordination. |
| Project Status Reports | Status reports not included. Informal updates provided as needed to communicate progress and next steps | Formal status reports available to summarize completed work, upcoming milestones, and key risks and decisions for stakeholders |
| Change Management | Service delivered to the defined scope; changes will require re-scoping | Formal change management processes are available to assess scope, schedule, and impact of requested changes |
| File De-Duplication | Data Transition Service | Data Migration Service |
|---|---|---|
| File Types | Limited to SOLIDWORKS parts (.sldprt), assembly (.sldasm), and drawing (.slddrw), as well as 2D CAD files (DWG/DXF) only. | De-duplication of all file type supported |
| Duplicate File Name and Duplicate File Content4 | Single approach can be selected for all files identified in this scenario, either: -Files transitioned as is with no cleanup -Include one file and rename the remainder -Include one file and exclude the remainder | Customized de-duplication options supported |
| Duplicate File Name Only5 | Single approach can be selected for all files identified in this scenario, either: -Files transitioned as is with no cleanup -Include one file and rename the remainder -Include one file and exclude the remainder | Customized de-duplication options supported |
| Duplicate File Content Only6 | Files transitioned as is with no cleanup | Customized de-duplication options supported |
| Data Conditioning | Data Transition Service | Data Migration Service |
|---|---|---|
| File Renaming | Not included. | File renaming supported |
| Folder Structure Mapping | Direct mapping of current structure. Directories (Windows Explorer source) or Projects (Workgroup PDM source) can be excluded or renamed7 | Full control of file distribution and folder name changes |
| File Version History Structure | Workgroup PDM only | Full history can be migrated from existing data management systems or can be built from Windows file structure8 |
| Custom Property Mapping | Up to 15 properties from SOLIDWORKS files or DWG/DXF attributes (Windows Explorer source) or Workgroup PDM properties mapped to PDM Variables. | Property mapping to PDM Variables is not limited. Property names and values can be updated as part of the migration, including optionally updating properties in physical files. Property information can be updated to match values in ERP, MRP or other systems. |
| Revision Mapping | SOLIDWORKS “Revision” property or DWG/DXF attribute (Windows Explorer source) or Workgroup PDM Revision mapped to PDM Revision | Revision information can be extracted from multiple sources including file naming schema or file properties |
| Workflow Mapping | Files from Windows Explorer mapped to single state. PDM Workgroup Lifecycles mapped one to one to PDM Workflow States. | Rule sets can be used to map files to various states and workflows in the PDM Vault |
| PDM Category Mapping | One category per file extension | Custom category mapping options |
1A functional group can be one or more business units, with one or more data sources, but which will have identical data conditioning requirements.
2SOLIDWORKS (sldprt, sldasm, slddrw), dwg and dxf file formats.
3Any Project Management services included in the Data Migration Service must be explicitly defined in the Statement of Work.
4Files identified as having the same file name and as identical based on the file’s unique digital fingerprint.
5Files identified as having the same file name as other files included in the migration.
6Files identified as identical based on the file’s unique digital fingerprint, but that have different file names.
7Directories can be renamed using a singular replacement ruleset. (Eg: Replace “x” with “y”).
8Building files history for files from a Windows source requires consistent file naming schema and/or folder structure to indicate historic versions.
Data Management Resources
Guides, tutorials, and best practices to help you organize, secure, and optimize your engineering data.
