The best way to judge a project drive is on your own files. We migrate one live project, configure users and locking, test Windows and macOS access, and run a restore test. If your team doesn’t prefer it over NAS, VPN or sync tools — you don’t pay.
We run a repeatable pilot built from our onboarding runbook — so you evaluate Orbifs under real conditions, with a safety net.
We bring a real project across from your NAS, SharePoint, Dropbox or LucidLink, preserving structure and permissions.
We set up accounts, roles and per-project permissions, then confirm lock visibility for the whole team.
We verify that mixed teams can open, lock and edit large files from both platforms at acceptable speed.
We restore a prior version and a deleted file, so you see recovery work on your own data before you commit.
Your source stays intact and read-only during stabilisation. Nothing is deleted until you confirm a successful cutover.
Data integrity, access, restore and performance are each checked against pass criteria you can see.
A pilot follows the same runbook we use for paid onboarding — just scoped to one project.
We agree the project, data volume, users and platforms, identify the source system, and set a migration window and rollback plan.
We provision your tenant and capacity, create users and roles, set project structure and permissions, then migrate the data and verify counts and integrity.
We configure file locking, confirm lock visibility, then restore a prior version and a deleted file.
If go-live criteria are met, we cut over and keep the source read-only during stabilisation. If not, you simply continue on your original system.
A few details help us scope the pilot before our first call. Prefer email? Write to support@orbifs.eu.
European AEC, engineering, geospatial or creative teams of roughly 10–150 people, with 1–30 TB of active project data and pain from VPN, NAS, SharePoint or sync conflicts.