Helpdesk migration

Migrate from ConnectWise PSA to Intercom

Field-level mapping, validation, and rollback between ConnectWise PSA and Intercom. We move data and schema; workflows are rebuilt natively in Intercom.

ConnectWise PSA logo

ConnectWise PSA

Source

Intercom

Destination

Intercom logo

Compatibility

100%

12 of 12

objects map 1:1 between ConnectWise PSA and Intercom.

Complexity

CModerate

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

ConnectWise PSA logo

ConnectWise PSA

What's pushing teams away

  • Onboarding timelines frequently extend 4-6 months before the platform is fully operational, with discovery calls, specialist assignment, and iterative configuration consuming significant internal resources before any value is realized.
  • ConnectWise pricing is quote-based and opaque; first-year costs commonly run 40-80% above base licensing once implementation, training, and bundled product costs are factored, leading to sticker shock at renewal.
  • Community and Reddit reports consistently cite contract inflexibility and difficulty exiting, with customers describing situations where they felt locked into multi-year commitments with limited negotiation leverage.
  • The learning curve is steep enough that many MSPs report 30-40% reduced technician productivity during the first 3-6 months of adoption, which erodes the ROI justification during the ramp period.
  • ConnectWise's 2024 API terms of service change that prohibits data export to competing PSA platforms fundamentally undermines exit planning, making it difficult to move data to alternatives like HaloPSA or Syncro.

Choosing

Intercom logo

Intercom

What's pulling them in

  • Instant chat and message threading on websites and apps gives support teams a single inbox without context-switching, according to reviewers on Capterra and G2 who highlight fast response times as a primary benefit.
  • Fin AI handles repetitive inbound queries automatically, reducing agent workload measurably — G2 reviewers report fewer escalations and faster first-response times once Fin is configured.
  • Automation workflows (Outbound, Operator, and custom bots) allow teams to qualify leads and route tickets without manual intervention, appealing to growth-stage SaaS companies managing high ticket volumes.
  • Help center articles and self-service deflection are natively integrated, so knowledge base content and chat conversations live in the same workspace, simplifying reporting.
  • Multi-channel support (live chat, email, SMS, WhatsApp, Phone) consolidates customer touchpoints into one inbox, reducing the operational overhead of managing separate tools.

Object mapping

How ConnectWise PSA objects map to Intercom

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

maps to

Intercom

Contact (company attribute)

1:1
Fully supported

ConnectWise 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

maps to

Intercom

Contact

1:1
Fully supported

ConnectWise 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

maps to

Intercom

Conversation

1:1
Fully supported

ConnectWise 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

maps to

Intercom

Conversation custom attributes + internal comment

1:1
Fully supported

ConnectWise 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)

maps to

Intercom

Contact custom attributes

1:1
Fully supported

ConnectWise 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

maps to

Intercom

Inbox Team

1:1
Fully supported

ConnectWise 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

maps to

Intercom

Conversation custom attributes

1:1
Fully supported

ConnectWise 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)

maps to

Intercom

Conversation custom attribute

1:1
Fully supported

ConnectWise 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

maps to

Intercom

Contact custom attributes

1:1
Fully supported

ConnectWise 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

maps to

Intercom

Contact or Conversation custom attribute

1:1
Fully supported

ConnectWise 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

maps to

Intercom

Conversation comment (URL reference)

1:1
Fully supported

ConnectWise 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

maps to

Intercom

Custom attributes on all records

1:1
Fully supported

ConnectWise 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.

Gotchas + challenges

What specifically takes care here

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 logo

ConnectWise PSA gotchas

High

API export restriction blocks migrations to competing PSAs

High

Onboarding delays can stretch 4-6 months before credentials

Medium

Service Board and SLA configuration is customer-specific

Medium

Knowledge base is company-nested, not flat

Medium

First-year pricing includes bundled implementation costs

Intercom logo

Intercom gotchas

High

S3 JSON export omits conversation transcripts

High

Workspace isolation prevents workflow migration

Medium

Fin AI resolution fees compound with automation success

Medium

Two-year conversation history limit on historical export

Low

Private app rate limits share workspace quota

Pair-specific challenges

  • ConnectWise ticket numbers cannot be preserved as Intercom conversation IDs

    ConnectWise PSA assigns sequential ticket numbers that appear in reporting, emails, and client references. Intercom assigns its own sequential conversation IDs at the point of creation and does not expose a writeable ID field during import. This means that after migration, the Intercom conversation URL and inbox reference will use Intercom's own ID — not the original ConnectWise ticket number. Clients referencing a ticket by number will not find it without a cross-reference. We store the original ConnectWise ticket number as a custom attribute (Source_Ticket_ID__c) on every conversation so your team can search and cross-reference by the original number.

  • ConnectWise Automate workflows do not migrate — automation logic must be rebuilt manually

    ConnectWise Automate (part of the ConnectWise PSA ecosystem) stores workflow definitions as a logic tree of triggers, conditions, and chained actions that execute across tickets, members, and integrations. Intercom's Rule Builder handles simple if-this-then-that automations — action-reaction rules on conversation events. The underlying ConnectWise Automate logic trees cannot be parsed, translated, or imported into Intercom. FlitStack AI exports your ConnectWise Automate workflow definitions as a documented reference that your Intercom admin can use to manually rebuild equivalent rules in Intercom's Rule Builder. This is always a manual step and is scoped separately from the data migration.

  • SLA terms have no native Intercom equivalent — custom fields are required and monitoring must be rebuilt

    ConnectWise PSA SLA Terms define breach time, business hours calendar, and priority response tier per service board. Intercom's SLA Rules operate at the Inbox Team level and use a single workspace-level business-hours setting — they do not support per-conversation SLA terms with tiered response windows. When migrating from ConnectWise PSA, we create three custom attributes on each conversation (SLA_Tier__c, SLA_Breach_Time__c, SLA_Business_Hours__c) to preserve the SLA context. However, Intercom's built-in SLA breach notifications and reporting cannot consume these custom fields directly — SLA performance tracking must be rebuilt using Intercom SLA Rules configured per team.

  • ConnectWise PSA time entries have no native Intercom home — financial reporting requires a separate tool

    ConnectWise PSA time entries carry billable hours, hourly rate, work description, and the member who logged time, all linked to tickets and integrated with ConnectWise billing and agreement margin reporting. Intercom has no native time-tracking object and no financial reporting layer. FlitStack AI migrates the hours, rate, and description as custom attributes on the conversation, but Intercom's reporting dashboard cannot aggregate billable utilization or calculate margin. If time tracking and billing reporting are critical to your operations, this data must flow to a separate PSA or accounting tool post-migration.

  • ConnectWise PSA configuration items and asset relationships have no direct Intercom equivalent

    ConnectWise PSA stores configuration items (devices, software, cloud assets) with parent-child hierarchies, dependency chains, and warranty/contract associations linked to Companies and Contacts. Intercom's data model supports Contacts, Conversations, and Custom Objects but has no native asset or configuration management concept. We store the most relevant configuration summary (type, serial, last-seen date) as custom attributes on the linked Contact. Full CI relationship graphs and warranty data have no Intercom home — your team should evaluate a dedicated IT asset management tool if configuration tracking is critical post-migration.

Migration approach

Six steps for a successful ConnectWise PSA to Intercom data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

ConnectWise PSA logo

ConnectWise PSA

Source

Strengths

  • Deep ecosystem integration with ScreenConnect, ConnectWise RMM, and 100+ marketplace apps provides a unified MSP stack.
  • Cloud billing consolidates multi-vendor Microsoft, Cisco, and Azure invoices into a single per-client billing engine.
  • Customer Portal supports per-company white-label portals with domain-branded helpdesk access and company-specific KBs.
  • Comprehensive PSA feature set from ticketing through project billing reduces the number of separate vendor tools an MSP must maintain.
  • REST API with Client ID authentication enables programmatic access for integrations and reporting.

Weaknesses

  • Onboarding complexity and timeline frequently exceeds 4-6 months before operational readiness, consuming internal IT resources.
  • API terms of service prohibit exporting data to competing PSA platforms, forcing CSV-based migrations for any platform exit.
  • Pricing is opaque and quote-based with no public tier matrix; first-year costs commonly run 40-80% above stated licensing.
  • The underlying database schema spans 760+ tables, making ad-hoc exports and custom reporting difficult without deep platform expertise.
  • Contract inflexibility and exit friction are commonly cited pain points in MSP community discussions.
Intercom logo

Intercom

Destination

Strengths

  • Integrated AI agent (Fin) for automated resolution with per-resolution billing that rewards high automation rates.
  • Multi-channel inbox consolidating live chat, email, SMS, WhatsApp, and Phone into a single threaded view.
  • Native help center with articles, collections, and self-service deflection capabilities.
  • Workflow automation for routing, qualification, and proactive outbound messaging across channels.
  • Strong API ecosystem with 10,000 req/min rate limits for private apps enabling high-throughput migration pipelines.

Weaknesses

  • Pricing model compounds with seat count, AI resolution fees, channel costs, and multiple add-ons, making total cost hard to predict.
  • Workspace-level isolation prevents moving workflows or content between environments, requiring manual rebuilds.
  • S3 JSON export deliberately excludes conversation transcripts, necessitating REST API calls for full message history.
  • Outages are reported as frequent enough to be a concern for always-on support operations.
  • Setup complexity means teams often require internal guidance or professional services to configure bots and automation correctly.

Complexity grading

How hard is this migration?

Moderate Helpdesk migration. 3 of 7 objects need a mapping; the rest are 1:1.

C

Overall complexity

Moderate migration

Derived from compatibility, mapping clarity, API constraints, and data volume across ConnectWise PSA and Intercom.

  • Object compatibility

    C

    3 of 7 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    7-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    ConnectWise PSA: On-Prem deployments do not enforce rate limits; cloud API rate limits are not publicly documented.

  • Data volume sensitivity

    B

    ConnectWise PSA doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your ConnectWise PSA to Intercom migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about ConnectWise PSA to Intercom data migrations

Answers to the questions buyers ask most during ConnectWise PSA to Intercom migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most ConnectWise PSA to Intercom migrations complete within 48–72 hours of migration clock time for setups under 50,000 tickets. Larger environments with 200,000+ records, multiple service boards with custom subtypes, or extensive time-entry data extend to 5–10 days. The longest planning step is mapping ConnectWise PSA service boards to Intercom Inbox Teams and defining custom attribute creation for SLA terms and billable time. A representative sample migration with field-level diff typically runs within the first 24 hours.

Adjacent paths

Related migrations to explore

Ready when you are

Move from ConnectWise PSA.
Land in Intercom, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day