Our methodology: your PSA stays the source of truth
Every MSP tool asks you to trust it with your data. Current's answer is deliberately conservative: your PSA — ConnectWise, Autotask, or HaloPSA — remains the system of record, and Current is never designed to become the source of truth for your business data. Current is an operating layer: it reads what your PSA and Microsoft 365 already know, adds scheduling intelligence, a CRM motion, and AI synthesis on top, and writes back only what you explicitly allow.
Why we built it this way
- ＋Your billing is sacred. Invoices, contracts, hours, and approval states drive real money. The system your accountant reconciles against must stay authoritative — a project tool that quietly forks billing data creates disputes, not efficiency.
- ＋Your history predates Current. Years of tickets, time, and account records live in your PSA. Mirroring beats migrating: nothing is converted, so nothing is lost or subtly changed.
- ＋No lock-in by hostage-taking. Because the record of truth never moves, leaving Current means turning off a sync — not exporting your business. We think that's the only honest way to earn a renewal.
- ＋Two systems that both claim to own a field will eventually disagree. Declaring one owner per field, up front, is what makes a durable two-way sync possible at all.
What this means field by field
The field-ownership map is the methodology made concrete. Your PSA owns everything billing-critical; Current owns only the scheduling overlay it adds on top. The map is identical whichever PSA you run — only the names change (work roles and agreements in ConnectWise, billing codes and contracts in Autotask).
| Your PSA always owns | Current adds (its own overlay) |
|---|---|
| Time entries, hours, approval status | Task start/end dates and the dependency graph |
| Billing codes/work roles, contracts/agreements, rates | Critical-path and milestone flags |
| Project, task & ticket names and statuses | Project health scoring (Current Score) |
| Companies, contacts, resources | CRM engagement layer: deals, sequences, briefings |
On every pull, the PSA's values win for PSA-owned fields — Current never argues. On every push, Current writes only Current-owned or explicitly permitted fields, and each write is confirmed by reading the record back from the PSA. Where the map genuinely can't settle a disagreement, the conflict is logged for a human to resolve — never silently overwritten.
The guardrails that enforce it
- ＋Write-back is off by default. A fresh workspace only reads. Push is enabled deliberately, per entity, by a Tenant Admin.
- ＋Read-back confirmation: after any outbound write, Current re-reads the PSA record and treats the PSA's answer as final.
- ＋Idempotent sync jobs: replaying a job can never duplicate a billing record.
- ＋Current-native projects (internal work with no PSA link) are the one place Current holds the data — because there is no PSA record to defer to. The moment you deploy one to your PSA, the ownership map takes over.