What's new in import
All project imports run on a shared engine:
- File queue — you can upload several exports at once, with progress shown by stage.
- A single “Units” window — select the units you need, rename them and merge “split” sections into a single unit.
- 3D preview of the whole assembly before creating the order — a clear view of what arrived and how.
Import from 3D-Конструктор now uses the .project and DXF formats (with automatic hardware drilling and splitting into units); the Basis and SketchUp imports have been moved to the same shared engine.
Importing projects from other programs into iFurn.pro lets you transfer a finished furniture design together with parts, dimensions, edge banding, drillings, grooves and milling — without re-entering anything by hand. 10+ formats are supported: from popular furniture designers (Basis-Furniture, 3D-Конструктор, PRO100, Woody, SketchUp PRO) to industrial CAD (TopSolid, Blum Configurator) and universal Excel/CSV templates.
For each source there is a separate guide with a list of steps in the source program, the export format (XML, CSV, XLSX, BXF2, Project3dc, etc.) and a description of what is transferred into iFurn.pro and what needs to be completed manually.
Supported programs and formats
- Basis-Furniture (3D) via plugin
- Modern import using a script plugin; transfers parts, edge banding, drillings and hardware. Basis versions 10–12. The format is JSON via a special iFurn.pro script plugin installed in Basis.
- Basis-Furniture 11/12 — installing the script
- Classic script export via the “Scripts — Import/Export” menu. Supports hardware operations and material replacement at the start of the import.
- iFurn.pro material database → Basis-Furniture
- Reverse export of the materials catalog from iFurn.pro into Basis-Furniture via XML nomenclature import.
- 3D-Конструктор (Project3dc XML)
- Import of an XML file in the
Project3dcformat — the output format of 3D-Конструктор built on top of AutoCAD DWG. Two engines: a local converter for all part types and cloud conversion via giblab.com. Panel parts, drillings, edge banding, edge milling and grooves are transferred. - SketchUp PRO via the ABF plugin + DXF
- Export from SketchUp PRO with the ABF plugin to the DXF AutoCAD 2018 format. Supports labels on parts and an edge-banding mode.
- TopSolid 7 — Ardis Optimizer XML
- Import via the
ArdisOptimizerProjectformat (TopSolid Wood → Cut Export → Export to Ardis). Universal importer v1.0.0 with an interactive material-replacement window. - Blum Configurator — BXF2
- BXF2 v1.1.0 import — both schemas (
cabinetLinkand the newcontainerLink). Blum hardware, pull-out drawers and the link to the cabinet body are transferred. - Excel — XLSX template
- A universal way to upload a part list with one edge band per side. Download the ready-made .xlsx template and fill it in following the example.
- PRO100 via an Excel copy
- Export the “Parts List” from PRO100 reports → copy into the iFurn.pro Excel template → import. A material “pro100_import” and an edge band “Кромка PRO100” are created automatically.
- Woody — WES and XML via Giblab
- Export the specification (.WES) + XML from Woody, process it through the Giblab.com service, save as .project and upload into iFurn.pro.
- Giblab.com — .project format
- Direct import of a project from Giblab.com (not to be confused with GitLab — these are different products). The format is XML with a
<viyar>tag. - Cabinet Vision — the CVJ project file
- The original
.cvjfile opens directly: parts, their position in the assembly and the explicit CNC operations. Materials are matched by hand; there is no edging in the file. - PRO100 — the project as OBJ
- The whole PRO100 project is exported to
.objand opens as an assembly: parts, their position, edging and round bores are recognised from the geometry. This route does not carry over grooves or milling — the Excel copy stays for a flat parts list.
What all imports have in common
- A starting order is required. First create an empty order in iFurn.pro — import always adds parts to an existing order.
- File limit — 10 MB. Large Basis projects with 3D models may not go through; export without 3D visualization.
- Antivirus scanning. All uploaded files are checked; if a file is rejected for no reason, re-save it (this is often a ZIP with a non-standard structure).
- Encoding. UTF-8 and Windows-1251 are supported for text formats (XML, CSV). Exotic encodings (KOI-8R, CP866) may be processed incorrectly.
- Material matching. For most formats, a matching window opens after upload: materials from the imported project are linked to materials from your database. You can choose an existing material or create a new one automatically.
- Round parts. If a round part (for example, a tabletop or a seat) comes from the source project as a set of arcs, the system automatically recognizes the case where the circle is inscribed in the entire blank and marks the part as a “circle” — with a correct trimming contour, correct edge allowances and without unnecessary duplicate operations. It reliably distinguishes this case from a round cut-out of a smaller diameter inside the part.
Which programs are NOT supported
The following programs are frequently asked about — at the moment there is no direct import:
- K3-Мебель / K3-Cottage
- БМебель (Б-Мебель)
- Plain AutoCAD DXF (only via SketchUp with the ABF plugin)
- IFC (BIM format)
- Pytha
- NX-CAD / Siemens NX
- Autodesk Inventor, SolidWorks, Fusion 360
For these programs, export via an intermediate format is possible: for example, via the Excel template (iFurn.pro) or via the Giblab.com service.
Integration via API
Besides manual file upload, projects can be integrated into iFurn.pro via the REST API (endpoint POST /import). This opens up automation options: integration with your own ERP, plugins for designers, batch processing. The API documentation is available in the API section.
Unified import: units, 3D preview, file queue
The import pages (Basis, SketchUp/DXF, 3D-Конструктор) run on a shared engine: you can upload several files at once (a queue) with progress by stage, see the whole assembly in 3D before uploading, and break the order down into units — select, rename and merge “split” sections into a single unit.
The import accepts ZIP archives
Your own software exports a project as a folder of files, and that folder is sent over as an archive. Every import page takes an archive: Basis, DXF, the 3D designer, iMOS, HOMAG/MPR and Astra. The archive is unpacked before the format check, so from there on the page works with the same files as if you had picked them one by one.
- Only the files that suit the page are taken out of the archive: an MPR set takes every
.mpr, the Astra page takes.add. When there is nothing suitable inside, the import states which extension it was looking for. - Every unpacked file is verified by its checksum. A quietly corrupted byte is a hole in the wrong place, not a visible error.
- Nested archives are not expanded: a report archive sitting next to the parts usually is not meant to be imported.
- The limits apply to the whole selection, not to a single archive: up to 128 MB after unpacking and up to 5000 files.
There is nothing to unpack RAR with, so the import plainly asks for a ZIP. A RAR renamed to .zip is recognised as well — by its content, not by its name.