Performing a large dataset transformation in SOLIDWORKS PDM vault—whether for cleaning up, updating existing drawings, or merging with a new vault—is not just a technical task; it’s a business-critical operation. At Blue Byte Systems Inc., we’ve led many data migration projects and learned that success starts with a solid virtual machine setup. That’s why this virtual machine checklist for your SOLIDWORKS PDM large data transformation helps ensure IT infrastructure is properly prepared before any migration work begins
If you’re planning a PDM migration, automation-based renaming, or metadata/files export, use this field-proven checklist to avoid costly disruptions and ensure a smooth process.
System Configuration
Start with a robust system foundation to avoid performance or permission issues:
- RAM: Ensure the VM has at least 16 GB of memory (as per SOLIDWORKS Corp system recommendations) to handle large datasets and API operations.
- Disable Windows Updates: Prevent unexpected reboots or resource conflicts by turning off automatic updates.
- Enable Remote Access: Turn on RDP so migration tasks can be managed remotely.
- User Privileges:
- Windows user must have local administrator rights.
- PDM user must have vault admin permissions, including rights to check in/out, transition, rename, and update metadata.
Environment Stability
Unattended automation demands reliability:
- Auto-Lock Disabled: Turn off session lock and idle logout policies. Check this article.
- Sleep/Hibernate Disabled: Prevent the VM from sleeping mid-process:
Exporting Files to Network Drives
If part of your migration involves exporting files to a shared directory:
- Ensure the Windows user has write access to the target network path (e.g.
\\network\pdm-migration\export). - Prefer UNC paths over mapped drives to avoid inconsistencies across user sessions.
SOLIDWORKS Setup (for API-Dependent Tools)
Even PDM-focused tasks may rely on SOLIDWORKS for:
- Extracting custom properties
- Processing derived drawings
- Handling references
Verify the environment:
- SOLIDWORKS is installed and the proper licenses for the type of installation can be borrowed.
- Required features like Toolbox are available. (Note: Toolbox is not included with SOLIDWORKS Standard.)
- No blocking dialogs (e.g., missing add-ins, license popups).
- Test with a basic macro to validate API connectivity.
Renaming Files? Do This First
If you’re renaming files as part of the migration—especially in batch using the API or scripts—vault consistency is critical.
Before running the migration:
- Ensure all users are completely logged out of the vault.
- Ensure all files are checked in. No files should be checked out by anyone.
- Clear all local vault views on user machines and secondary VMs.
- Optionally, temporarily disable user access during the operation to prevent interference.
Renaming in a live vault with active users or cached files can lead to reference corruption, rename failures, and broken assemblies. Don’t skip this step.
Why This Checklist Matters
PDM migrations are high-risk if not managed carefully. Misconfigured VMs, insufficient permissions, or unlocked files can turn a one-day export into a week-long recovery job.
By following this checklist, you ensure:
- A stable, API-ready VM environment
- No dialog interruptions
- Data consistency when renaming, exporting, or migrating
- A smoother experience for both IT and engineering teams
At Blue Byte Systems Inc., we help companies automate, migrate, and modernize their SOLIDWORKS PDM environments with confidence.
📩 Need expert guidance? 🌐Schedule a discovery call or request a free vault readiness review today.