The Data Synchronization Layer ensures customer data stays accurate everywhere. Bidirectional sync keeps changes aligned across OnboardFi, CRM, billing, and custom applications.
One source of truth
Mappings are transparent and tenant-aware, so each organization can customize sync rules without impacting others.
Sync Architecture
- Bi-directional flows: Updates made in OnboardFi or external systems propagate automatically.
- Field mappings: Administrators control how objects align across platforms.
- Conflict resolution: Define priority rules when simultaneous changes occur.
Configuration Console
| Section | Purpose | Key Controls |
|---|---|---|
| Field mapping | Align fields between systems | Data type conversions, default values |
| Sync frequency | Schedule real-time or batched updates | Cron controls, throttling |
| Validation rules | Prevent malformed data | Required fields, regex, value ranges |
| Monitoring | View sync status and errors | Activity logs, retry management |
Setup Workflow
Connect Systems
Authenticate integrations (CRM, billing, data warehouse) using secure OAuth or API keys.
Map Objects & Fields
Pair customers, projects, tasks, and custom objects with their external counterparts.
Define Conflict Policies
Choose authoritative systems per field or enable last-write-wins based on context.
Run Test Syncs
Preview updates with sample records to ensure mappings and transformations behave correctly.
Monitor & Optimize
Track sync health, resolve exceptions, and adjust schedules as your data volume grows.
Best Practices
Design for scale
Start with essential fields, then expand mapping coverage once the foundation is stable.
- Document mapping decisions and share with RevOps or IT stakeholders.
- Use tags or flags to identify records still awaiting sync confirmation.
- Pair with workflow automations to trigger actions when synced data changes.
Next, explore Workflow Automation Triggers to orchestrate cross-system actions.