Current + Rev.io integration

Rev.io became Current's fifth PSA in October 2026, beside Autotask, ConnectWise, HaloPSA and Syncro. Customers, contacts, notes, projects and time sync in both directions with the Rev.io PSA, and ticket status changes go back to Rev.io. Rev.io stays your system of record for tickets, time, invoicing and agreements, while Current adds the delivery layer on top: dependency-aware scheduling, a native critical-path engine, Kanban and Gantt boards, milestones, and a partner portal with database-level financial isolation. One PSA connects per workspace. Rev.io support is new; a few behaviours are still being confirmed against a live Rev.io account.

What the integration does

Rev.io has real projects, with phases, milestones and work items. A Rev.io project becomes a Rev.io-synced project in Current, and building a project from Current creates it in Rev.io, with task dates, status and assignee kept in step both ways. Time logged in Current lands as a Rev.io ticket time log against the time log reason the technician picks, so billing stays where it belongs. Projects that do not belong in the PSA run Current-native and never make a Rev.io API call.

What data flows

• Customers, contacts and customer notes, kept in step with Current's CRM so your book of business matches Rev.io.
• Tickets join each company's ticket list, and ticket status, and notes on project tickets, go back to Rev.io from Current.
• Projects, phases, milestones and work items come in, and a project built in Current is created in Rev.io with them. After that, task and milestone changes and project and phase end dates go back, with last-editor-wins arbitration on the shared fields.
• Time entries: time logged in Current is sent to Rev.io once for billing, and corrections afterwards are made in Rev.io.
• Agreements and services drive each company's MRR, priced per line on that line's own billing interval.
• Invoices feed account profitability, with no cost from Rev.io ever mirrored.
• Opportunities and quotes appear on the company record to read.

Which system owns what

Rev.io remains the source of truth for time, billing, invoicing and agreements. Current owns scheduling, dependencies and the critical path, and pushes the resulting dates back. Nothing Current does can change a customer's invoice or a rate, and Current deletes nothing in Rev.io except a customer note you delete in Current.

What is not included yet

Opportunities and quotes are read-only, so a won Rev.io quote is not converted in Current yet. Attachments, leads, holidays and time off are not synced. Current found no survey endpoint in Rev.io's PSA API, so CSAT in Current comes from CrewHu or SimpleSAT. Rev.io's API publishes no rate limit and no webhooks, so Current checks projects and tasks every 5 minutes and tickets and CRM records about every hour, paces itself, and a large first sync can take longer than on other PSAs.

Push is a setting

Writing back to Rev.io is gated. CRM write mode starts off and gates every write, time included, with a test mode in between that only touches customers named for testing, and two-way sync additionally controls project, task, ticket and CRM edits. An evaluation is read-only until you decide otherwise.

Getting set up

You need a Rev.io PSA API key, created in Admin, API Management while signed in as a dedicated user whose role can read the areas above and edit the ones you want written back. It is a key for the Rev.io PSA API, not for Rev.io's separate billing REST API. The connection test proves the key and names any area its role cannot read before anything is stored. One PSA per workspace.