Six Bitrix24 Disk Migration Errors That Force Portal Redesign After Six Months

Bitrix24 Disk migration projects often appear complete after a weekend file transfer, yet six months later companies face missing contracts, unauthorized access to salary folders, and severe performance degradation. The root cause is rarely a failed copy operation; instead, the original network share structure is replicated unchanged into a platform whose storage model relies on three distinct container types: My Disk, group and project disks, and the company-wide common disk.

Ошибка 1 — copying the folder tree verbatim — produces 30–40 top-level folders with names such as “Miscellaneous 2” and eight levels of nesting. Because Bitrix24 search is under-used, employees cannot locate documents efficiently. The recommended approach is to map every top-level folder to an owner, a readership group, and a business process before any files are moved.

Ошибка 2 occurs when My Disk becomes the de-facto working repository. When an employee leaves, signed contracts disappear; when the employee is on vacation, colleagues cannot retrieve needed files. The fix is a written policy that restricts My Disk to personal drafts only, enforced by periodic REST inventory scripts that flag personal storages containing more than three top-level folders.

Ошибка 3 — granting rights to individual users rather than departments — results in access matrices containing dozens of personal entries that quickly become stale. After one reorganization the list is unreadable and auditing is impossible. Rights should be assigned via department codes (DR5) or workgroups so that personnel changes are handled automatically.

Ошибка 4 places every ambiguous document into the common disk with full access for all authenticated users. The Toyota T-Connect, G-Link and G-BOOK breach affecting 2.15 million customers between 2013 and 2023 shows how a single misconfigured open bucket can remain unnoticed for ten years. The correct default is read-only access on the common disk, with write rights granted only to specific sections and no “Miscellaneous” folder allowed.

Ошибка 5 attaches file copies to tasks and CRM records instead of links. Version history is lost, storage quotas are wasted, and the latest approved document is never visible in the deal card. The rule is simple: the authoritative copy lives on Disk; every other entity receives a link.

Ошибка 6 enables desktop synchronization for the entire tree. Offline editing on multiple machines produces conflicting copies that nobody resolves. Only folders actively edited offline should be synchronized; the rest should be accessed via mapped network drives or the online editor.

Successful teams now follow four practices: a thorough pre-migration inventory that discards 40–60 % of untouched files, a two-week pilot on a single department, named owners for every top-level section, and mandatory quarterly rights reviews. These steps convert a one-time migration into a sustainable information-security process.