Architects and engineers working with SketchUp often face a critical transition point when their design models need to move into a more robust Building Information Modeling environment. Bringing a skp file into Revit is rarely a simple drag-and-drop action, but rather a strategic process that requires careful preparation and understanding of how both platforms handle geometry and data. This workflow is essential for preserving the conceptual massing developed in SketchUp while unlocking the advanced analytical and documentation features of Revit.
Understanding the SKP to RVT Workflow
The journey begins with the native SketchUp file, typically saved with a .skp extension. This file contains the 3D geometry, textures, and basic components that form the initial design. Revit, being a BIM-centric tool, does not natively open .skp files, necessitating an import or export translation. The goal of this process is to transfer the visual representation and spatial logic from SketchUp into a Revit project file (.rvt) without losing critical structural information or compromising the model's integrity.
Preparation and Cleanup in SketchUp
Before initiating the transfer, it is crucial to optimize the SketchUp model. A messy file with unnecessary edge lines, overlapping faces, or misaligned components will translate into a problematic Revit file. Users should utilize the "Purge Unused" function to remove unused materials and components, and meticulously check for geometry errors using the built-in validation tools. Taking the time to ensure faces are clean and groups are well-organized will drastically reduce the risk of import errors and ensure a smoother translation of surfaces into Revit elements.
Methods for Importing SketchUp Files
There are generally two primary pathways to get your design into Revit: importing the SketchUp file directly as a mesh or exporting to a format like DWG for more precise vector translation. The choice depends largely on the design's complexity and the required level of detail. Importing as a mesh preserves the visual appearance but sacrifices the individual editability of walls and floors, whereas a DWG export maintains vector geometry that can be traced into Revit elements.
Option 1: Direct Import as a Mesh
The most common method involves using the Import function in Revit and selecting the .skp file. When the import options appear, it is vital to select the correct positioning, usually "Origin to Origin" to align the model correctly within the project coordinates. Once imported, the SketchUp geometry resides as a static mesh. While this is excellent for visual reference, lighting studies, and massing analysis, the elements cannot be modified with typical wall or floor tools. This method is ideal for early-stage coordination where the BIM specifics are handled separately.
Option 2: Export to DWG for Traceability
For users who require editable components, exporting the SketchUp model to a DWG file is the preferred route. This process usually involves installing a third-party plugin within SketchUp that flattens the active view to a 2D plan or section. The resulting DWG file contains polylines representing the edges of the walls and slabs. In Revit, these vectors can be imported into a drafting view and meticulously traced to create actual Revit walls, floors, and foundations. This workflow is more labor-intensive but yields a fully parametric model suitable for construction documentation.
Managing Materials and Textures
One of the most significant challenges in this conversion is the handling of materials. SketchUp materials are texture-based, while Revit materials are defined by graphical overrides and physical properties. When importing a mesh, the original textures often appear pixelated or distorted. To combat this, users should apply high-resolution images in SketchUp and ensure the texture resolution is adequate for the final render. When using the DWG method, materials must be manually reassigned in Revit, providing an opportunity to apply accurate thermal and acoustic properties to the building components.
