US trucking holding: moving the CRM to its own server, then ongoing support

How did the move from the cloud to the holding's own server go?

The holding runs freight trucking in the US and has several divisions. Drivers work in the portal as guests, each in their own group chat, so drivers cannot see one another.

In August 2025 we chose the server configuration and installed Bitrix24 On-Premise on it. The data came over from the cloud in a single weekend in mid-September, and the client signed off the work on 23 September. Leads were not moved, as the holding does not use them. What came over:

• the company structure and users;
• groups, projects and tasks with comments and files;
• CRM settings, companies, contacts and deals with their details and timeline history;
• the knowledge base.

How can divisions keep passwords in the CRM so that each person sees only their own?

For passwords we built a separate smart process. Records are encrypted on the server, and each employee sees only their own. Later we added a split by division: personal passwords are visible only to their owner, shared ones to the head and the department, and each division has its own master passwords. The first version was delivered in December 2025 and the revision in January 2026.

How do you send one message to every driver when each has a separate chat?

A guest can only be messaged inside their own chat, so the platform itself has no way to send one announcement to every driver. We wrote our own module: a staff member writes one message and it goes to every driver chat. In the second phase we added segmentation: the chats got extra fields, such as trailer type, so a message can go to just the right group. The client signed off the module on 2 April 2026.

How do managers enter and see their weekly metrics?

Managers enter their figures in a smart process, and a BI dashboard brings them together; access depends on who created the record. We showed the first version in February 2026 and built the second, with extra metrics, in the spring. In May the client confirmed that everything works, and in June we handed the team a user guide.

What else does the support cover?

Leave and sick-leave requests follow a set route: an employee's request goes to their head of department and HR, and a head of department's goes to an assigned executive and HR. A trigger creates a task when any of five deal fields changes, such as driver status. We also removed the platform branding from the portal and added the holding's logo.

Since January 2026 we have run monthly backups and portal updates. A specification for changes to the drivers' mobile app is under review: we have sent a proposal, and work has not started yet.