Helpdesk migration
Field-level mapping, validation, and rollback between ConnectWise PSA and Intercom. We move data and schema; workflows are rebuilt natively in Intercom.
ConnectWise PSA
Source
Intercom
Destination
Compatibility
12 of 12
objects map 1:1 between ConnectWise PSA and Intercom.
Complexity
CModerate
Timeline
48–72 hours
Overview
ConnectWise PSA is a relational PSA platform built around Companies, Contacts, Service Tickets, Time Entries, Configurations, and project-linked workflows across multiple service boards. Its data model is deeply relational — tickets carry billable time, SLA breach timestamps, work notes, and configuration associations that span dozens of linked records. Intercom is a conversation-first customer messaging platform organized around Contacts, Conversations (tickets), Admins, Teams, Articles, and Custom Objects. Its data model is flatter and chat-oriented, which means several ConnectWise PSA concepts have no native equivalent and require custom attribute workarounds. FlitStack AI extracts ConnectWise PSA data via the REST API (rate-limited at ConnectWise cloud; unlimited on-prem), transforms it to match Intercom's object schema, creates Inbox Teams from service boards, and loads via Intercom's bulk API. We preserve original create and closed timestamps as custom attributes, store SLA tier and breach time as custom conversation fields, and flag ConnectWise Automate workflow definitions for export so your Intercom admin can rebuild them in Rule Builder. Billable time entries migrate as custom attributes on the linked conversation rather than a native object. The core migration challenge is the data-model divergence: ConnectWise PSA's relational structure (configurations, projects, multi-location contacts, agreements) has to be flattened or stored as custom attributes in Intercom, and all automation logic requires manual rebuild. We surface this clearly in the migration plan so there are no surprises at cutover.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a ConnectWise PSA object lands in Intercom, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
ConnectWise PSA
Company
Intercom
Contact (company attribute)
1:1ConnectWise Company records carry business name, address, website, phone, and territory. Migrates to Intercom Contact where the company name becomes a Contact attribute. Multi-location support in ConnectWise (site-level addresses) collapses to one primary address per Contact in Intercom; additional locations stored as custom text. Territory and type flags migrate as custom attributes.
ConnectWise PSA
Contact
Intercom
Contact
1:1ConnectWise Contact fields (first name, last name, email, phone, title, type) map directly to Intercom Contact fields. Multiple contact locations per record in ConnectWise (site-level) require consolidation: one location becomes the Intercom primary address; remaining locations stored as a custom text attribute listing site labels and addresses.
ConnectWise PSA
Service Ticket
Intercom
Conversation
1:1ConnectWise Service Tickets are the primary migration object. Summary becomes Conversation subject; ticket body becomes the opening comment; work notes append as internal comments. SLA terms, billable time summary, and priority level migrate as custom attributes. Original ticket ID stored as a custom attribute for traceability. Service board becomes Inbox team assignment. Status mapped to Intercom open/closed state.
ConnectWise PSA
Time Entry
Intercom
Conversation custom attributes + internal comment
1:1ConnectWise Time Entries carry billable hours, hourly rate, work description, and the member who logged time. Since Intercom has no native time-tracking object, each time entry attached to a ticket becomes a custom attribute pair on the linked Conversation (hours, rate, description) plus an internal comment entry with the technician name and time summary. Time entry records themselves are not individually surfaced in Intercom's object model.
ConnectWise PSA
Configuration (CI)
Intercom
Contact custom attributes
1:1ConnectWise Configuration Items (devices, software, cloud assets) link to Companies and Contacts. Intercom has no native asset or CI management concept. We store CI type, serial number, and last-contact date as custom attributes on the associated Contact or Conversation. Full CI relationship graphs (parent-child, dependency chains) cannot be preserved — the most relevant CI summary attaches to the ticket-level conversation.
ConnectWise PSA
Service Board
Intercom
Inbox Team
1:1ConnectWise Service Boards organize tickets by team and routing rules. Each board maps to an Intercom Inbox Team so that ticket ownership and queue routing reflect the original structure. Subtypes and board-level priorities require custom attributes since Intercom teams have no native subtype concept. Board-level SLA configurations need separate custom field creation per conversation.
ConnectWise PSA
SLA Term
Intercom
Conversation custom attributes
1:1ConnectWise SLA Terms define breach time, business hours flag, and priority tier per service board. Intercom has no native SLA term object — only basic SLA rules per team. We create custom attributes on each Conversation: SLA_Tier__c, SLA_Breach_Time__c, and SLA_Business_Hours__c to preserve the original SLA context. SLA response-time performance tracking must be rebuilt using Intercom SLA Rules and reporting.
ConnectWise PSA
Project (ticket association)
Intercom
Conversation custom attribute
1:1ConnectWise Projects link multiple tickets under a single project record with billing and milestone tracking. Intercom has no project concept. We store the project name and ID as a custom attribute on each linked Conversation. Project-level billing, milestones, and financial tracking cannot migrate — those must be managed in a project management tool post-migration.
ConnectWise PSA
Agreement
Intercom
Contact custom attributes
1:1ConnectWise Agreements (recurring service contracts, SLAs, and billing schedules) link to Companies and Contacts. Intercom has no native agreement object. Agreement type, start/end dates, and SLA tier migrate as custom Contact attributes. Recurring billing amounts and margin data have no Intercom equivalent — stored as custom text notes for reference only.
ConnectWise PSA
Custom Field / Custom Table
Intercom
Contact or Conversation custom attribute
1:1ConnectWise PSA supports extensive custom fields on tickets, contacts, and companies, plus custom tables for specialized MSP data. Intercom supports custom attributes on Contacts and Conversations, and Custom Objects for richer data. Each custom field is evaluated individually: text/date/number fields migrate directly as Intercom custom attributes; pick-list fields require value-by-value mapping; multi-select fields may collapse to comma-separated text depending on Intercom's attribute type support.
ConnectWise PSA
Attachment / File
Intercom
Conversation comment (URL reference)
1:1ConnectWise ticket attachments (documents, screenshots, exported logs) migrate as comment attachments in Intercom if they are accessible via URL from ConnectWise's hosted file storage. Files exceeding Intercom's attachment size limits (10MB) are noted and links are provided in the conversation comment. Inline images in ticket notes download and re-upload to Intercom's file hosting.
ConnectWise PSA
Audit / System IDs
Intercom
Custom attributes on all records
1:1ConnectWise PSA internal record IDs, create timestamps, and last-modified timestamps are preserved as custom attributes on each Intercom record (Source_Ticket_ID__c, Original_Create_Date__c, Source_System__c). This supports field-level diff during validation, delta-run de-duplication, and reconciliation against ConnectWise PSA for audit purposes. Cross-field validation rules and record-level change tracking support compliance reporting and historical analysis requirements.
| ConnectWise PSA | Intercom | Compatibility | |
|---|---|---|---|
| Company | Contact (company attribute)1:1 | Fully supported | |
| Contact | Contact1:1 | Fully supported | |
| Service Ticket | Conversation1:1 | Fully supported | |
| Time Entry | Conversation custom attributes + internal comment1:1 | Fully supported | |
| Configuration (CI) | Contact custom attributes1:1 | Fully supported | |
| Service Board | Inbox Team1:1 | Fully supported | |
| SLA Term | Conversation custom attributes1:1 | Fully supported | |
| Project (ticket association) | Conversation custom attribute1:1 | Fully supported | |
| Agreement | Contact custom attributes1:1 | Fully supported | |
| Custom Field / Custom Table | Contact or Conversation custom attribute1:1 | Fully supported | |
| Attachment / File | Conversation comment (URL reference)1:1 | Fully supported | |
| Audit / System IDs | Custom attributes on all records1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
ConnectWise PSA gotchas
API export restriction blocks migrations to competing PSAs
Onboarding delays can stretch 4-6 months before credentials
Service Board and SLA configuration is customer-specific
Knowledge base is company-nested, not flat
First-year pricing includes bundled implementation costs
Intercom gotchas
S3 JSON export omits conversation transcripts
Workspace isolation prevents workflow migration
Fin AI resolution fees compound with automation success
Two-year conversation history limit on historical export
Private app rate limits share workspace quota
Pair-specific challenges
Migration approach
Extract ConnectWise PSA data via REST API
FlitStack AI authenticates against the ConnectWise PSA REST API using an API member account with read permissions on Companies, Contacts, Service Tickets, Time Entries, Configurations, and custom tables. We paginate through results respecting rate-limit headers (ConnectWise cloud enforces request throttling; on-prem deployments have no rate limit). Data is exported as structured JSON organized by object type, with timestamps, owner IDs, and system IDs preserved. We capture the full ticket history including work notes and closed-by member for each ticket.
Transform ConnectWise PSA records to Intercom object schema
Each ConnectWise PSA object is mapped to its Intercom equivalent using the field-level mapping plan. Service Tickets become Conversations with custom attributes for SLA tier, breach time, priority, and billable hours. Work notes append as internal Intercom comments. Time entries aggregate into custom attributes on the linked conversation. ConnectWise Automate workflow definitions are exported as a separate JSON reference file. Custom fields from ConnectWise PSA are dynamically translated to Intercom custom attributes on the appropriate object (Contact or Conversation) based on field type.
Create Inbox Teams and custom attributes in Intercom
Before data loads, FlitStack AI creates Inbox Teams in Intercom corresponding to each ConnectWise PSA service board so that team assignment is available at migration time. Custom attributes for SLA tier (pick-list), SLA breach time (date), SLA business hours (boolean), billable hours (number), billable rate (currency), priority (pick-list), and source ticket ID (text) are created on the Conversation object. Custom attributes for source contact ID and source company ID are created on the Contact object. Admin email matching maps ConnectWise PSA members to Intercom admins for assignment.
Run sample migration with field-level diff
A representative sample of 100–200 records — spanning multiple service boards, open and closed tickets, contacts with multiple locations, and tickets with time entries — migrates to a staging Intercom workspace. FlitStack AI generates a field-level diff comparing source values against the destination Intercom records, showing the resolved owner, mapped SLA tier, aggregated billable hours, and original timestamp preservation. You review the sample results, confirm SLA mapping, and approve the full migration scope before the production run.
Execute full migration with delta-pickup window and rollback
Full migration runs against the production Intercom workspace using Intercom's bulk import API, with real-time progress reporting. ConnectWise PSA remains fully operational — FlitStack AI uses scoped read access only, so your team keeps working without interruption. A delta-pickup window (24–48 hours after the main run) captures any tickets, contacts, or time entries modified during the cutover window. An audit log records every operation. One-click rollback reverts the Intercom workspace to its pre-migration state if reconciliation uncovers data integrity issues.
Platform deep dives
ConnectWise PSA
Source
Strengths
Weaknesses
Intercom
Destination
Strengths
Weaknesses
Complexity grading
Moderate Helpdesk migration. 3 of 7 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across ConnectWise PSA and Intercom.
Object compatibility
3 of 7 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
7-object category — typical timelines run 2–7 days end-to-end.
API constraints
ConnectWise PSA: On-Prem deployments do not enforce rate limits; cloud API rate limits are not publicly documented.
Data volume sensitivity
ConnectWise PSA doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during ConnectWise PSA to Intercom migration scoping. Not seeing yours? Book a call.
Walk through your ConnectWise PSA to Intercom migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave ConnectWise PSA
Other ways to arrive at Intercom
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.