Integrate Bitrix24 with Planfix: Sync Deals, Projects, Contacts

Integrate Bitrix24 with Planfix

A manager closes a deal in Bitrix24, then manually creates a project in Planfix, copying client data and duplicating the technical specification. The production department doesn't see the deal status, and the manager doesn't know the project stage. Information diverges within a week. We solve this with a turnkey integration of the two systems. Our seven years of Bitrix24–Planfix integration experience and certified specialists ensure smooth operation without double entry. We'll assess your project in one day—get a consultation.

Savings on manual data entry reach up to 120,000 RUB per year for a department of five managers.

Why integrate Bitrix24 with Planfix?

Integration eliminates double entry and provides end-to-end transparency: a deal in Bitrix24 is linked to a project in Planfix, statuses sync, and data transfers automatically. Without integration, managers spend up to 30% of their time on manual copying. Order integration and reclaim time for sales.

How to sync deals and projects?

Linking Bitrix24 and Planfix can be done three ways. The choice depends on integration depth and budget:

REST API offers 5× more flexibility than iPaaS solutions. Planfix provides a REST API with API‑key authentication. Bitrix24 offers a REST API with OAuth 2.0 or incoming/outgoing webhooks. Official documentation: Bitrix24 REST API.

// Handler for ONCRMDEALUPDATE event
$arFields = $_REQUEST['data']['FIELDS'];
if ($arFields['STAGE_ID'] == 'WON') {
    $deal = CRest::call('crm.deal.get', ['ID' => $arFields['ID']]);
    $projectData = [
        'name' => $deal['result']['TITLE'],
        'client' => $deal['result']['CONTACT_ID'],
        'status' => 'in_progress'
    ];
    $result = callPlanfixAPI('project.add', $projectData);
    CRest::call('crm.deal.update', [
        'ID' => $deal['result']['ID'],
        'fields' => ['UF_PLANFIX_PROJECT_ID' => $result['id']]
    ]);
}

Scenario: Deal → Project

This is the most common case. When a deal in Bitrix24 moves to the "Won" or "In progress" stage:

1. A handler receives deal data via the ONCRMDEALADD / ONCRMDEALUPDATE webhook.
2. A project is created in Planfix via the project.add API: title = deal title, client, deadline, assignee.
3. Inside the project, a set of typical tasks is created from a template—production stages, approvals, shipping.
4. The Planfix project ID is written to a custom field of the Bitrix24 deal for quick navigation.
5. A link to the Bitrix24 deal is stored in the Planfix project—reverse reference.

Scenario: Status sync

When a project in Planfix advances to a new stage, the deal stage in Bitrix24 updates automatically. This is critical for managers: they see progress without logging into Planfix.

Stage mapping is configured individually:

Planfix sends a webhook when a task/project status changes. The handler calls crm.deal.update in Bitrix24.

Scenario: Contact and company sync

The client database is maintained in Bitrix24 as the master source. When creating a project in Planfix:

• If a contact/company doesn't exist in Planfix, it is created.
• Duplicate search is done by email or phone.
• When a contact is updated in Bitrix24, the data is refreshed in Planfix (one-way sync).

Reverse sync (from Planfix to Bitrix24) is usually not needed—CRM remains the master system for client data.

Scenario: Tasks and comments

For tighter integration:

• Comments on the Planfix project are duplicated in the Bitrix24 deal timeline—the manager sees order progress.
• Tasks in Planfix that require manager involvement (approvals, client clarifications) are created as tasks in Bitrix24.
• Files uploaded to Planfix are accessible via a link in the deal card.

What about migrating from Planfix to Bitrix24?

If the goal is to replace Planfix and move project management into Bitrix24:

1. Process audit—which Planfix features are actually used, and which of those Bitrix24 covers.
2. Entity mapping—projects → Bitrix24 groups/projects, tasks → tasks, custom fields → user fields.
3. Data export—via Planfix API: projects, tasks, comments, files.
4. Import into Bitrix24—via REST API: bulk import of tasks, upload files to the drive.
5. Parallel run—2–4 weeks with both systems active for validation.
6. Decommission Planfix—after confirming all processes work in Bitrix24.

Risks of migration: loss of Planfix custom logic (analytics, automation scripts), need to retrain the team, differences in task models (Planfix is more flexible with task hierarchy).

Systems coexistence

Migration isn't always necessary. If Planfix handles project management better than Bitrix24, the systems can work in parallel with integration. Key rules:

• Single source of truth for clients—Bitrix24.
• Single source of truth for projects—Planfix.
• Deals and sales—only Bitrix24.
• Production tasks—only Planfix.
• Bridging—automatic via integration.

Scope of integration work

We provide a full cycle:

• Audit of current business processes and data schemas.
• Integration architecture design (flow diagram).
• Implementation via REST API or iPaaS with custom scripts.
• Webhook and automatic update configuration.
• Testing of all scenarios (including edge cases).
• Integration documentation and operational rules.
• Team training (2–3 hours).
• Post-launch support for 2 weeks.

We'll assess your project in one day—contact us. Order integration and eliminate double data entry.

On a recent project handling 50 deals per month, we cut manual data entry by 10 hours per week, reducing errors to near zero.

How a corporate portal on Bitrix24 solves the problem of information chaos?

Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.

We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).

What does the portal offer in daily work and why is it better than messengers?

In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.

Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.

Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.

Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.

HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.

Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.

Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.

How does integration with 1C and Active Directory accelerate HR management?

Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.

Types of corporate portals and key integrations

Additional integrations that deliver real value:

• Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
• IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
• Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
• EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.

Security and compliance with Federal Law 152‑FZ

The portal contains personal data, financial reports, strategic plans. We guarantee protection:

• role model via CGroup and section‑level permissions;
• two‑factor authentication (OTP, Yandex.Key, SMS);
• audit of all actions (b_event_log);
• TLS encryption for transmission and disk encryption;
• full compliance with Federal Law No. 152‑FZ "On Personal Data".

How is implementation carried out? Step‑by‑step plan

1. Audit — we record current processes, measure time losses.
2. Design — choose portal type, plan integrations.
3. Implementation — configure business processes, permissions, interface.
4. Test — pilot group tests scenarios, we fix issues.
5. Launch — connect all employees, train, hand over documentation.

What you receive after implementation

• Project documentation: architecture, integration scheme, business process diagrams.
• Configured portal with all integrations (1C, AD, telephony, EDI).
• Business process descriptions and instructions for administrators and users.
• 30 days of technical support after launch.
• Access to our knowledge base and migration scripts.

Post‑launch support: how to prevent the portal from becoming obsolete

After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.

Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.

Order a turnkey corporate portal implementation

Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.