Skip to main content
Business & GrowthCRM Services30 lines

Synchronize Companies Between Twenty CRM and ERPNext

Map company and customer identities between Twenty and ERPNext, separate field ownership, and reconcile repeated or failed sync operations.

Quick Summary8 lines
Record the Twenty workspace and API version, ERPNext and Frappe versions, and exact object definitions. Determine which Twenty object should correspond to an ERPNext Customer. In a customized workspace, inspect the API schema rather than assuming the UI labels are the object names. Confirm which contact, address, billing and account fields are optional or mandatory in each system. Classify personal and financial fields before exposing them to a sync account.

## Key Points

- [Twenty APIs](https://docs.twenty.com/developers/extend/api)
- [Frappe REST API](https://docs.frappe.io/framework/user/en/api/rest)
skilldb get crm-services-skills/twenty-crm-erpnext-integrationFull skill: 30 lines
Paste into your CLAUDE.md or agent config

Synchronize Companies Between Twenty CRM and ERPNext

Agree on object and field ownership

Record the Twenty workspace and API version, ERPNext and Frappe versions, and exact object definitions. Determine which Twenty object should correspond to an ERPNext Customer. In a customized workspace, inspect the API schema rather than assuming the UI labels are the object names. Confirm which contact, address, billing and account fields are optional or mandatory in each system. Classify personal and financial fields before exposing them to a sync account.

Build an external identity crosswalk from stable Twenty and ERPNext IDs. A company name or email domain is useful for a candidate match but can change or refer to several legal entities. Require an explicit decision before merging records. Define field ownership separately. For example, Twenty may own sales owner and display label, while ERPNext owns billing classification and posting status. Preserve each system's canonical values and define what happens when an upstream field is blank.

Verify the sync before enabling writes

Start with read-only fixture exports and produce a dry-run mapping report. For each row show source ID, proposed target, fields to be set, and any blocking issue. Test a new company, an existing match, a repeated event, and a malformed address. Verify mapping of enumerated values, timezones and nested data. Identify how stale rows or deletions should be handled, with archive or manual review where deletion would lose business evidence.

Use service identities scoped to the approved test objects and fields. Keep API credentials in approved storage and avoid logging record payloads. Write one owned fixture and read it back through the documented APIs. Persist the crosswalk together with the outcome. Where the two systems cannot share a transaction, record a recoverable operation identity so a timeout or replay can be reconciled before another create.

Exercise concurrent and partial failures

Change one CRM-owned field and one ERP-owned field independently, then run the sync. Keep each authorized update and route incompatible mappings to a conflict queue. Record the source versions or timestamps used to decide whether work was stale. Retry a read or a known idempotent update within bounds, and verify an ambiguous create by external identity before retrying it.

Reconcile counts for processed, skipped, linked, rejected and unresolved records against a known fixture population. Save the schema mapping, credential scopes, record IDs and scenario results. Enable one direction in the organization's approved staging path before considering two-way operation.

References

Install this skill directly: skilldb add crm-services-skills

Get CLI access →