Migrating Projects to Domus.Cad — Step-by-step best practices
1. Plan the migration
- Inventory: List all projects, files, formats, textures, external references, and plugins to move.
- Prioritize: Start with a small, representative project as a pilot.
- Set timeline: Allocate time for backups, conversion, testing, and staff training.
2. Back up everything
- Full backups: Create read-only archives of original files and assets (cloud + local).
- Versioning: Tag the backup with project name, date, and software version.
3. Check compatibility and prerequisites
- File formats: Identify source formats (DWG, DXF, IFC, OBJ, 3DS, etc.) and Domus.Cad import capabilities.
- System requirements: Ensure target machines meet Domus.Cad’s hardware and OS specs.
- Plugins/scripts: Catalog custom scripts or plugins; find Domus.Cad equivalents or plan workarounds.
4. Convert geometry and assets
- Use native import tools first: Import DWG/DXF/IFC directly into Domus.Cad when possible to preserve layers and blocks.
- Export intermediary formats: When direct import fails, export from source as IFC or a neutral format (DXF, OBJ) and import into Domus.Cad.
- Textures & materials: Export texture maps and relink them in Domus.Cad; convert material definitions to Domus.Cad’s material system.
- Scale & units: Confirm units and scale on import; fix mismatches immediately.
5. Recreate or map metadata and BIM data
- Layer/level mapping: Map source layers, levels, and object types to Domus.Cad equivalents.
- Object properties: Migrate custom properties and BIM data (room names, materials, cost codes) via IFC or CSV where supported.
- Naming conventions: Standardize names during import to avoid conflicts.
6. Rebuild complex elements and families
- Parametric elements: Recreate parametric components (doors, windows, stairs) using Domus.Cad’s native families if import doesn’t preserve them.
- Scripts/macros: Translate essential automation scripts into Domus.Cad’s scripting language or replace with plugins.
7. Validate and fix geometry
- Clash checks: Run interference checks for overlapping geometry.
- Topology fixes: Repair open edges, flipped normals, duplicated faces, and non-manifold geometry.
- Tolerance & precision: Adjust tolerance settings to match original model fidelity.
8. Update documentation and drawings
- 2D sheets: Recreate or import layouts, title blocks, and annotation styles; verify scales and dimension styles.
- Schedules & BOMs: Regenerate material schedules, takeoffs, and bills of materials in Domus.Cad.
- Detailing: Reproduce key construction details that didn’t transfer.
9. Test workflows and performance
- Pilot review: Have the design team review the pilot project for accuracy and usability.
- Performance tuning: Optimize model complexity, LOD, and visibility settings for acceptable performance.
- QA checklist: Run a checklist covering geometry, metadata, drawings, and render output.
10. Train team and update standards
- Training: Provide focused sessions on Domus.Cad workflows, file management, and best practices found during pilot.
- Templates & libraries: Create standardized templates, title blocks, and component libraries in Domus.Cad.
- Documentation: Publish a migration playbook with mapping tables, common fixes, and contact points.
11. Roll out and monitor
- Phased rollout: Migrate projects in batches based on priority and team readiness.
- Support channel: Maintain a rapid-response support channel for migration issues.
- Post-migration audit: Audit completed migrations against the QA checklist and correct gaps.
Quick checklist (short)
- Backup originals
- Pilot test one project
- Verify formats, units, and scale
- Map layers/metadata, convert materials
- Recreate parametrics and detail drawings
- Run QA, train users, and standardize templates
If you want, I can create a migration checklist tailored to your current source format (e.g., Revit, ArchiCAD, AutoCAD) — tell me which one and I’ll generate it.
Leave a Reply