A DevRev integration that keeps accounts, deal registrations, opportunities, meetings, and comments consistent two-way between your workspace and Partner Portal, sharing only partner-safe fields.

Partner Lifecycle Sync keeps your team and your partners working from a single source of truth. It mirrors the partner deal lifecycle two-way between your primary DevRev workspace and your Partner Portal workspace, while ensuring only partner-safe data ever crosses the boundary.

Features

• Deal Lifecycle Sync

Accounts, deal registrations, opportunities, meetings, and customer-facing comments stay in sync across both workspaces, each flowing in the direction it should.

• Field-Level Security

Only a partner-safe subset of fields is ever serialized and sent. Internal notes and internal CRM and commercial fields never leave your workspace – the absence of a field is the security boundary.

• Cross-Workspace Delivery

On each side, the integration writes only to its own workspace using its platform service account. Changes are HMAC-signed and verified by the peer workspace before they are applied, so there are no cross-workspace credentials to manage.

• Duplicate-Safe Correlation

Records are correlated by a stable source identifier, so a re-sync updates the existing twin in place instead of creating duplicates.

• Loop and Conflict Safety

An echo-and-actor loop guard prevents changes from ping-ponging between workspaces, and modified-date revisions resolve conflicts last-writer-wins.

Installation

1. Install the integration from the marketplace on both workspaces from the same package.
2. Set sync_role to dev0 on the production side and portal on the Partner Portal side.
3. Point each side's peer trigger URL at the other workspace's inbound trigger URL.
4. Set the same shared signing secret on both workspaces.
5. Optionally configure fallback owners for created records and a pilot partner allow-list to scope which Partner accounts originate.

Once both sides point at each other and share the secret, the partner deal lifecycle syncs automatically.

Access

The integration runs as a service account scoped to each workspace, reading and writing only the objects it syncs. Only partner-safe fields cross, over HMAC-signed messages; internal notes and commercial fields never leave your workspace. Your data stays yours.