ConnectWise sync: the complete field-mapping reference
Every synced ConnectWise entity and field, what it becomes in Current, sync direction, and who wins on conflict.
On this page · 14 sections
- How instance discovery works
- How the delta sync works
- Companies
- Which statuses mean inactive
- Contacts
- Agreements and additions (your contracts)
- Opportunities (your pipeline)
- Projects, phases, and project tickets
- Service tickets
- Members (your staff)
- Time entries
- Board statuses: how done means done
- Holidays and time off (PTO)
- What's deliberately not synced
If you run ConnectWise, you already know its entity model: Companies, Contacts, Agreements, Opportunities, Projects, Phases, Project Tickets, Members, and Time Entries. This page is the field-level reference for exactly how each maps into Current, which direction data flows, and who wins when both sides have touched the same record. Bookmark it. You'll come back to it.
For the plain-language version of how the connection is set up, see "Connect ConnectWise PSA and choose what syncs". For what triggers a write back (and the gates in front of every write) see "What Current writes back to ConnectWise (and when)".
How instance discovery works
ConnectWise instances don't share one API address, your company runs on a specific host and a versioned path that ConnectWise moves during upgrades. When you connect, Current calls ConnectWise's public site-discovery endpoint with your site URL and company ID, learns the right API host and version path, and stores them alongside the connection (they're not secrets). If ConnectWise relocates your instance later, Current notices the old path failing and re-resolves automatically, no manual URL maintenance, ever.
How the delta sync works
Every ConnectWise record carries a last-updated timestamp, and Current's 5-minute poll asks only for records updated since its last pass, per entity, each with its own cursor. Writes made by Current come back stamped with the API Member's identity, and Current skips those, so its own pushes are never re-imported as changes.
Companies
| ConnectWise field | Becomes in Current | Direction | Who wins |
|---|---|---|---|
| Companies.id | ConnectWise company link (id) | pull only | ConnectWise |
| Companies.name | Company name | pull only | ConnectWise. Unless you've renamed the company in Current and that rename hasn't synced back yet, in which case your edit is protected until it does |
| Companies.status | Active / inactive | pull only | ConnectWise's own inactive statuses, unless a tenant admin saves a list in Current, which then decides (see Which statuses mean inactive below) |
| Companies.types | Company type (the first type) | pull + push | ConnectWise. A type you change in Current is sent as the company's first type, and its other types are kept |
| Companies.phoneNumber / website | Phone / Website | pull + push | ConnectWise |
| Companies.addressLine1 / addressLine2 / city / state / zip | Address fields | pull + push | ConnectWise |
| Companies.market | Market / industry | pull only | ConnectWise when the field is set, never cleared to blank once Current has one |
| Companies.parentCompany | Customer group (the parent is the group's main company) | pull + fill when empty | ConnectWise. Current writes it only when it is empty, and never overwrites or clears it |
| Companies.territoryManager (Territory Manager) | Account manager | pull + push | ConnectWise's Territory Manager is the account manager. If Current's account manager is empty, the Territory Manager fills it; if a manager reassigns the account in ConnectWise, that wins. An in-app AE claim or leadership reassignment made in Current is never overwritten, and when you push a company its account manager is written back as ConnectWise's Territory Manager (the person must be linked to a ConnectWise member). |
The Territory Manager becomes the account manager (chosen for ConnectWise on Jul 18, 2026). Auto-matching links by the member's email, so an account manager only fills once that person is linked to a Current user on Users & roles. If ConnectWise names a Territory Manager who isn't linked, the account simply shows no manager (and a company push fails loudly rather than guessing).
A company whose Parent Company is set in ConnectWise joins a customer group named after the parent. When you group sites in Current and pick a main company, Current sets each site's empty Parent Company to that main company and reads it back to confirm. A site that already has a different Parent Company is left alone and flagged on the group's site list. Removing a site or deleting a group leaves ConnectWise unchanged. Every write follows your CRM write mode, so in Test mode only ZZ-Current Test companies are written. Current is still confirming this write in ConnectWise, so for now only ZZ-Current Test companies are written, in every mode. See "Customer groups: one customer with several sites".
With CRM write mode on, an edit you make to a linked company in Current is sent back to ConnectWise for the fields marked pull + push, together with its custom field values; the company name and status stay ConnectWise's. Current-only fields on the company record (total MRR, MRR at risk, lead source) have no ConnectWise equivalent and are never pushed.
Which statuses mean inactive
ConnectWise keeps a company's active or inactive state on its status, not on the company itself. Until a tenant admin saves a list, a status counts as inactive when ConnectWise marks it inactive. Many workspaces also use a status named Inactive that ConnectWise does not mark that way, and until you choose it, every company on it shows as active in Current.
- Open Settings, then Integrations, then ConnectWise PSA, and press Manage. A tenant admin sees Which statuses mean inactive, with each of your ConnectWise company statuses and how many companies are on it.
- Until you save, the section reads Using ConnectWise's own inactive flags, and the statuses ConnectWise marks inactive are ticked.
- If you have a status named Inactive that ConnectWise doesn't mark, Current suggests it. Press Count it as inactive to choose it. Current never chooses it for you.
- Tick every status that means a company is no longer active and untick the rest, then press Save. You can untick a status ConnectWise marks inactive: its companies then count as active in Current. What you save is the whole list, so if you untick every status, no company counts as inactive.
- Once a list is saved, a line names any status Current treats differently from ConnectWise.
- To go back, press Use ConnectWise's own flags. Current then follows ConnectWise's inactive statuses again.
- The next company sync applies your choice: inactive companies drop off the Companies list under Status: Active, and a campaign audience set to active companies leaves them out. Nothing is changed in ConnectWise.
Current reads your statuses at the start of each company sync. If that read doesn't finish, active and inactive stay as they were for that sync instead of being guessed, and the section says so. A company on a status Current hasn't read yet also stays as it was. A status you saved as inactive keeps counting as inactive even if ConnectWise no longer lists it. Company counts are refreshed about once a day.
Contacts
ConnectWise stores a contact's email and phone numbers as a list of communication items rather than flat fields. Current flattens that list on the way in: the default email item becomes the contact's email, the default phone becomes phone, and a mobile item becomes mobile. On push, Current writes the same structure back, so ConnectWise stays canonical.
| ConnectWise field | Becomes in Current | Direction | Who wins |
|---|---|---|---|
| Contacts.id | Contact link (id) | pull + push (new contacts) | Not applicable |
| Contacts.firstName / lastName | First name / Last name | pull only | ConnectWise |
| Contacts.title | Title | pull only | ConnectWise |
| communicationItems (default Email) | pull only | ConnectWise | |
| communicationItems (Phone / Mobile) | Phone / Mobile phone | pull only | ConnectWise |
| Contacts.defaultFlag | Primary contact flag | pull only | ConnectWise |
| Contacts.inactiveFlag | Active | pull only | ConnectWise |
| Contacts.addressLine1 / addressLine2 / city / state / zip | Street, suite or floor, city, state, postal code | pull + push | ConnectWise, except an edit made in Current that hasn't been sent yet |
| Contacts.country | Country (ConnectWise's country name) | pull + push | ConnectWise; a country name ConnectWise doesn't list is not sent |
Contact addresses follow the same rules as on Autotask. A ConnectWise contact with no address never clears one Current already holds. Saving a contact in Current sends it to ConnectWise right away: its name, email, title, phone numbers and address all go together, and until they reach ConnectWise the next sync keeps your changes rather than putting ConnectWise's old values back. An address field you clear in Current is not cleared in ConnectWise. A country is sent only when its name matches a country in your ConnectWise list; otherwise it stays in Current and the push says so. A new contact created from Current with no address of its own is created in ConnectWise with its company's address.
To fill the address of existing ConnectWise contacts, a tenant admin opens Integrations, ConnectWise, Sync behavior, and uses "Contacts · fill blank addresses from the company". Preview lists every active contact with no address at all that would get its company's ConnectWise address, and every contact skipped because its company has no street or city. A contact with any part of an address is left alone. Fill stays off until Current has seen one ConnectWise contact that has a street and a postal code, which is how it confirms where ConnectWise keeps a contact's address. Filling asks you to type FILL, reads each contact from ConnectWise again just before changing it, follows your CRM write mode (in Test mode, only ZZ-Current Test companies), and records every change in the audit log.
Agreements and additions (your contracts)
Agreements come in from ConnectWise to power MRR, seat counts, customer status, and the whitespace grid. The one write is a workspace admin's change to an addition's quantity or unit price from the company page (Change units or price), sent once and read back; Current never edits anything else on an agreement. An agreement counts as active and recurring when its status resolves to active, it isn't cancelled, and its type and billing cycle read as recurring.
| ConnectWise field | Becomes in Current | Direction | Who wins |
|---|---|---|---|
| Agreements.name / type | Contract name / type | pull only | ConnectWise |
| Agreements.startDate / endDate | Start / end date | pull only | ConnectWise |
| Agreements.agreementStatus / cancelledFlag | Contract status | pull only | ConnectWise |
| Agreements.billingCycle | Billing period + recurring flag | pull only | ConnectWise |
| Additions.product (catalog item) | Service line name | pull only | ConnectWise |
| Additions.quantity | Unit count (seats) | pull, plus a workspace admin's change | ConnectWise |
| Additions.unitPrice | Unit price | pull, plus a workspace admin's change | ConnectWise |
Opportunities (your pipeline)
Opportunities pull into your pipeline, and opportunity pushes go the other way once CRM write mode allows them. ConnectWise separates an opportunity's stage (where it sits in the pipeline) from its status (open, won, lost). Current reads both: the stage maps through the stage mapping in your Manage drawer, and won/lost comes straight from the status record's own won and lost flags, so there's no label guessing.
- 1Open the stage mappingSettings › Integrations → ConnectWise PSA → Manage → “Opportunity pipeline & stage mapping”. The badge there shows how many of your pipeline stages are still unmapped.
- 2Map each Current stage to a ConnectWise stageOpen the editor and pick the ConnectWise opportunity stage each of your Current pipeline columns corresponds to. Won and lost aren't mapped here. They come straight from the ConnectWise status's own won/lost flags.
- 3Why it mattersAn opportunity only pushes its stage to ConnectWise once that stage is mapped. An unmapped stage fails closed and never writes, so a half-mapped pipeline silently won't push. Map every active column you want to sync.
| ConnectWise field | Becomes in Current | Direction | Who wins |
|---|---|---|---|
| Opportunities.id | Opportunity link (id) | pull + push (new opportunities) | Not applicable |
| Opportunities.stage | Pipeline stage (via your stage mapping) | two-way | the side that moved it last |
| Opportunities.status (wonFlag / lostFlag) | Won / lost outcome | pull only | ConnectWise |
| Opportunities.expectedCloseDate | Expected close date | pull only | ConnectWise |
| Opportunities.primarySalesRep | Opportunity owner (via the member ↔ user link) | pull only | ConnectWise |
| Opportunities.company | Linked company | pull only | ConnectWise |
Projects, phases, and project tickets
A ConnectWise project imports as a ConnectWise-synced project, ConnectWise stays the source of truth for time and billing on it, and Current owns the schedule. ConnectWise's project tickets are the work items inside a project, so they become Current tasks.
| ConnectWise field | Becomes in Current | Direction | Who wins |
|---|---|---|---|
| Projects.name | Project name | pull only | ConnectWise |
| Projects.status (project board status) | Project status | pull only | ConnectWise |
| Projects.company | Linked company | pull only | ConnectWise |
| Projects.manager | Project manager (via the member link) | pull only | ConnectWise |
| Projects.estimatedStart / estimatedEnd | Project dates | pull only | ConnectWise |
| Projects.estimatedHours | Budget hours | pull only | ConnectWise |
| Phases.description | Phase name | pull only | ConnectWise |
| Phases.scheduledStart / scheduledEnd | Phase dates | pull only | ConnectWise |
| Project tickets.summary | Task name | pull only | ConnectWise |
| Project tickets.status (board status) | Task status (backlog/in progress/review/done) | two-way (see below) | depends on your two-way sync setting |
| Project ticket dates | Task start / end dates | two-way | Current, after the first import, Current's scheduler owns task dates and pushes changes out |
| Project tickets.budgetHours | Estimated hours | pull only | ConnectWise |
| Project tickets.wbsCode | Work-breakdown position | pull only | ConnectWise |
Service tickets
Service tickets with no project attached feed the read-only company ticket history behind account insight, sentiment, and SBR statistics. Grouped by service board, which is where the board-noise toggles apply. They never become project tasks. Current changes a service ticket only where you ask it to: a post-sale ticket from a won quote, a billing ticket for a contract change, and, with the service desk's ticket and time sync on, the ticket linked to a desk ticket.
Members (your staff)
| ConnectWise field | Becomes in Current | Direction | Who wins |
|---|---|---|---|
| Members.identifier | Member link | pull only | ConnectWise |
| Members.firstName + lastName | Name | pull only | ConnectWise |
| Members.email | Email, the link key to a Current login | pull only | ConnectWise |
| Members.inactiveFlag | Active | pull only | ConnectWise |
Time entries
A ConnectWise time entry charges to something, for project work, that's the project ticket. Current logs time against the task and submits it as a time entry charged to that ticket, with the work role, work type, and agreement you picked. The vocabulary differs from Autotask (work role where you'd say billing code, agreement where you'd say contract), and Current's time dialog labels follow the PSA you run.
| ConnectWise field | Becomes in Current | Direction | Who wins |
|---|---|---|---|
| TimeEntries.id | Time entry link (id) | two-way | Not applicable |
| TimeEntries.member | Logged-by user | two-way | Not applicable |
| chargeToId / chargeToType | Linked task (project ticket) | two-way | Not applicable |
| timeStart / timeEnd / actualHours | Date, times, and hours | two-way | ConnectWise |
| workRole / workType / agreement | Work role / Work type / Agreement | push, then mirrored back | ConnectWise |
| billableOption | Billable flag | two-way | ConnectWise |
| Time status + invoice linkage | Approval / invoiced status | pull-back after push (read-back) | ConnectWise. An invoiced entry can never be edited from Current |
Board statuses: how done means done
ConnectWise statuses live per board, and each status carries its own closed flag. Current builds its status map from your boards' live lists: a status ConnectWise flags as closed maps to done, and the rest map to Current's simplified stages by their labels. The original ConnectWise status id is always kept alongside the simplified stage, so nothing is lost in translation, and the board/status mapping in the Manage drawer lets you correct any board whose labels don't say what they mean.
Holidays and time off (PTO)
Current keeps your scheduler accurate by reading two things from ConnectWise's schedule area: company holidays and member time off.
- Holidays come from your ConnectWise holiday lists. Every date across every list pulls in as a read-only company holiday, and the dependency and cascade scheduler skips those days (just like weekends), so task dates never land on a day no one is working. You can still add holidays by hand on the Holidays admin page; a ConnectWise-synced one you delete there reappears on the next sync (remove it in ConnectWise to make it stick).
- Time off comes from ConnectWise schedule entries whose type reads like PTO (vacation, sick, out of office, and the like). Each becomes per-day PTO for that member in Current, so the Timeline, dependency map, and what-if scenarios all schedule around real absence. Only members linked to a Current user produce PTO rows.
Both pulls are read-only and self-healing: a cancelled holiday or a shortened time-off request disappears on the next sync. If your API member can't read the schedule area, Current skips these pulls with a note rather than failing your whole sync, and sends no alert or email about it. Add holidays and PTO by hand in the meantime. The lines that open them are optional: Schedule → Schedule Entries for time off (on older or on-premise ConnectWise, Service Desk → Resource Scheduling), and System → Table Setup with Holiday List allowed for holidays.
What's deliberately not synced
- ConnectWise appointments and other non-time-off schedule entries don't pull, only company holidays and PTO-type time off feed the scheduler.
- Ticket attachments aren't downloaded. Attachment handling for ConnectWise is a planned follow-on.
- Project health scores, total MRR, and MRR at risk are computed in Current and never pushed to any ConnectWise field.
- Agreements and the product catalog are not edited, apart from a workspace admin's change to an addition's quantity or price. Current never edits the rest of your billing structures.
- Current polls; it does not register ConnectWise callbacks. The 5-minute delta covers change detection without a webhook's failure modes.
