Box ↔ Dalux synchronization

Bridge Box — where the office, contracts and clients live — and Dalux — where the site teams work on the iPad. DMS Sync Manager moves drawings, models and metadata between the two on a schedule, so nobody has to download from Box and upload to Dalux by hand.

How it works

Three steps to keep Box and Dalux in sync.

01

Connect Box and Dalux

Box authenticates with OAuth 2.0 against your Box enterprise. Dalux uses an API key issued by your Dalux tenant administrator. Each project keeps its own pair of connections, stored encrypted at rest.

02

Map Box folders to Dalux document areas

Pick a Box folder as the source (or destination) and a Dalux project + document area on the other side. Box metadata templates map to Dalux metadata fields, with direction set per sync task.

03

Filter and schedule

Rules filter by file type (PDF, DWG, IFC, RVT), label, revision, or last-modified window. Schedule hourly, every 6 hours, daily, or on demand. Every run is logged file by file.

What customers do with it

A few real-world scenarios.

  • Push Box-managed issued drawings into Dalux so site supervisors open the latest set on the iPad.
  • Pull Dalux as-built markups back into Box for the company-wide project archive and client access.
  • Maintain a Box archive of every Dalux-issued revision for retention and handover documentation.

"Projects rarely fail in design — they fail when teams can't trust they're looking at the latest version."

— BUCC

Frequently asked questions

Does this work with both Dalux Box and Dalux Field?

This pair targets Dalux Box / Document — the document storage layer — not to be confused with Box.com. Dalux Field issues, snags and inspections are out of scope; they stay in Dalux Field.

Are IFC models preserved through the sync?

Yes. IFC 2x3, IFC 4 and IFC 4x3 pass through unchanged — bytes-identical at the destination. Models keep their property sets, geometry and structure.

Are Box metadata templates mapped to Dalux fields?

Yes. Each sync task lets you map Box metadata template fields to Dalux metadata fields of your choice, so revisions carry their identifiers across.

Is Box version history preserved?

Each new revision arrives as a new version in the destination, preserving Box's native version history. The revision label is written into the configured Dalux field.

Where is the data stored?

Sync workers run in eu-west-1 (Ireland). Files transit through the workers but are not retained; only metadata and audit logs are stored. For Box itself, EU data residency is available via Box Zones.

Ready to sync Box and Dalux?

Book a demo and we'll walk you through setting it up for your project.

  • Tailored to your Box ↔ Dalux setup
  • 30-minute session, no commitment
  • We handle the setup, you just show up
Book a Demo