Bitrix24 Integration with Planfix

Bitrix24 Integration with Planfix

A company works across two systems: CRM and sales in Bitrix24, project management in Planfix. A manager closes a deal, then manually creates a project in Planfix, copies customer data, duplicates the brief. The production team doesn't see the deal status; the manager doesn't know the project stage. Information diverges within a week. Integrating both systems eliminates double entry and provides end-to-end transparency: a deal in Bitrix24 is linked to a project in Planfix, statuses synchronize, data transfers automatically.

Integration Scenarios

Bitrix24 and Planfix integration can be implemented three ways. Choice depends on integration depth and budget:

Planfix provides a REST API with API key authentication. Bitrix24 — REST API with OAuth 2.0 or incoming/outgoing webhooks.

Scenario 1: Deal → Project

The most common case. When a deal in Bitrix24 moves to "Won" or "In Progress" stage:

1. Handler receives deal data via ONCRMDEALADD / ONCRMDEALUPDATE webhook.
2. In Planfix, a project is created via API project.add: name = deal name, client, deadline, responsible person.
3. Inside the project, a set of template tasks is created — production stages, approvals, shipping.
4. Project ID in Planfix is saved to a custom field in the Bitrix24 deal — for quick navigation.
5. Link to the Bitrix24 deal is saved in the Planfix project — for reverse connection.

Scenario 2: Status Synchronization

When a project in Planfix moves to a new stage, the deal stage in Bitrix24 updates. This matters for managers: they see progress without entering Planfix.

Stage mapping is configured individually:

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

Scenario 3: Contact and Company Synchronization

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

• Contact/company is created in Planfix if it doesn't exist
• Duplicate search — by email or phone
• When updating a contact in Bitrix24 — data updates in Planfix (one-way sync)

Reverse sync (Planfix to Bitrix24) usually isn't needed — CRM remains the master system for client data.

Scenario 4: Tasks and Comments

For tighter integration:

• Comments on a Planfix project are duplicated in the deal timeline in Bitrix24 — managers see what's happening with the order
• Planfix tasks requiring manager involvement (approval, client clarification) are created as tasks in Bitrix24
• Files uploaded to Planfix are accessible via link in the deal card

Migration from Planfix to Bitrix24

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

1. Process audit — which Planfix functions are actually used, what Bitrix24 covers.
2. Entity mapping — projects → Bitrix24 projects/groups, tasks → tasks, custom fields → user fields.
3. Data export — via Planfix API: projects, tasks, comments, files.
4. Import to Bitrix24 — via REST API: batch task import, file uploads to disk.
5. Parallel operation — 2–4 weeks working in both systems for verification.
6. Disconnect Planfix — after confirming all processes work in Bitrix24.

Migration risks: loss of Planfix custom logic (analytics, auto-scenarios), team retraining needed, differences in task model (Planfix is more flexible in task hierarchy).

Systems Coexistence

Migration isn't always necessary. If Planfix handles project management better than Bitrix24, systems 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
• Connection — automatic via integration

What We Configure

• Event handler for "Bitrix24 Deal → Planfix Project" connection
• Two-way status sync with configurable mapping
• Contact and company synchronization (Bitrix24 = master)
• Transfer of comments and tasks between systems
• For migration — data export from Planfix and import to Bitrix24
• Documentation on integration scenarios and operational rules