ConnectWise to HaloPSA migration: what ticket history comes across and what to preserve

What moves and what stays behind when an MSP switches PSA tools?

When an MSP moves from ConnectWise or Autotask to HaloPSA, the current state of the business usually moves: clients, contacts, contracts, assets and open tickets. What often stays behind or arrives flattened is the history: ticket time entries, internal notes, status changes, attachments, SLA timers and the links between tickets, projects and agreements. That left-behind history is the part worth preserving before the old subscription ends.

This guide is for MSP owners and operations leads. It sets out how to plan the migration so the history survives, and why a preserved archive may also have licensing value. It does not claim details about any vendor's migration tool, so use each vendor's current documentation and a test import to confirm.

Which records matter in a PSA?

Treat any cell marked "varies" as an open test question, not an assumption.

The six-step plan to preserve history before the switch

1. Inventory the old system. List every record type above, the years each covers and the approximate counts. The data inventory builder gives a structure for listing systems without describing content.
2. Decide what must live in the new system. Not every closed ticket needs to be searchable in HaloPSA. Choose a cut-off year.
3. Run a pilot import. Migrate one client's history and compare ticket counts, notes, time entries and attachments against the source.
4. Export the remainder to a native archive. Use the old tool's export or API to capture what the import does not carry, and store it with access controls.
5. Write the retention terms. Record how long the old subscription stays readable after cutover and the date the archive becomes the only copy.
6. Name an owner. Someone, not "IT", holds the archive and the instructions to read it.

Dates matter. Contract end dates and the first billing cycle in the new tool create a short window in which the old system is still usable; schedule the archive inside it.

How do the three tools compare for history?

Do not take a general claim about any of them as settled. Ask each vendor, and test.

The point of the table is the same four tests on every platform, not a ranking. The Opsgenie retirement page applies the same logic to on-call history.

Which checks should run before the old PSA is switched off?

• Ticket counts per year match between source and archive for the pilot client.
• A sample of long tickets shows every note and time entry in order.
• Attachments open from the archive, not only from the old system.
• Someone other than the person who ran the export has read the archive.
• The retention date and the archive owner are written down and shared with the owner.

Why is the left-behind history interesting for licensing?

A PSA holds repeatable service workflows: a user reports a problem, a technician triages, escalates, fixes and closes with notes and time. AI buyers training and evaluating IT support agents look for that structure, and long histories across many clients show variety.

The client-data caveat is serious. Tickets describe client environments, and an MSP's contract with each client decides who may use them.

• Check master service agreements for data use and confidentiality clauses.
• Tickets that mention client staff, systems and credentials carry personal and security data.
• Records created for the MSP's own internal IT are cleaner than client-facing ones.
• Any license discussion needs the MSP owner as sponsor, and client consent where contracts require it.

SourceX and the company set scope, redaction and consent requirements together before any work begins. Nothing is delivered without a signed agreement and authorization.

A fictional example

Illustrative: a managed IT firm with about 90 staff has used its PSA for eight years and decides to switch. During planning, its operations lead runs a pilot import for one client, finds notes arrive but status history is flattened, and archives the full source export before the old contract ends. Later, the owner asks whether the archived internal-IT tickets could qualify for a licensing introduction. The firm, not the partner, runs every export.

What to say to an MSP owner

The managed service provider overview covers where else the topic comes up, and the Pipedrive export guide shows the same pattern in a CRM.

How the introduction and rewards work

You introduce the company; SourceX qualifies it against the baseline of 50+ full-time employees at peak (contractors excluded), years of documented operations and rights; the company completes an inventory; price and terms are agreed; buyers review; and the deal closes before delivery. The who qualifies page has the detail.

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company, payable only after the buyer pays and SourceX receives its fee. No reward is guaranteed.

Common mistakes

Next step

If an MSP you work with is switching PSA tools, register as a partner and introduce the owner, or have them apply at sourcex.si/apply with your referral link. Preserve the history first.