Add-on integration checklist: the records section most plans miss

Why do integration plans miss records?#

Integration plans miss records because they are organized by function, and records belong to every function at once. Finance owns the chart of accounts, HR owns payroll, IT owns identity and devices, and sales owns the CRM, but nobody owns the help desk history of an add-on being folded into a shared service team.

The usual trigger is a synergy line. Procurement lists the add-on's duplicate subscriptions, the platform cancels them at renewal, and the vendor eventually deletes the account. By the time someone asks for the history of a key customer, the only copy left sits in a departed employee's downloads folder.

Admin access is the other weak point. At a company of a few hundred people, the account that owns Zendesk, HubSpot or Jobber often belongs to a founder or office manager who leaves after the deal. Without that login, even a willing team cannot export what it needs.

The records section, step by step#

The records section is a short sequence that runs alongside the rest of the integration and gates every system cancellation. Add it to the plan as its own workstream with one named owner who can stop a cancellation.

• 1Freeze: pause retention policies and auto-delete rules in email, chat, help desk and file storage on day one.
• 2Access: move admin credentials, billing ownership and recovery emails for every SaaS tool to platform-controlled accounts.
• 3Inventory: list each system, its record families, the years of history it holds and its business owner.
• 4Contracts: capture signed customer agreements, standard terms, privacy notices and vendor contracts in force at close, with dates.
• 5Export: run full exports, including notes, attachments and logs, from any tool on the cancellation list.
• 6Verify: compare record counts, open sample records with their attachments, and confirm the export reads without the tool.
• 7Store: put each archive in a named location with an owner, an access list and a retention rule.
• 8Release: the records owner signs off before procurement cancels the subscription.

What a full export includes, system by system#

A full export includes every object that explains how work was done, not only the headline records a migration tool picks up. The table shows what is commonly left behind in each type of system.

Export capabilities differ by vendor and plan, and some tools limit how far back an export reaches or leave out certain objects. Check the vendor's documentation and the add-on's plan level early, because briefly upgrading a plan to reach export features is far cheaper than losing the history.

Two vendor examples show why timing matters. Slack says exports of private channels and direct messages are not offered on its Free or Pro plans, are available on Business+ and Enterprise, and must be applied for by a Workspace or Org Owner; on a Free workspace, messages and files more than one year old are permanently deleted. HubSpot's Product Specific Terms strongly recommend retrieving customer data before the subscription term ends and, for hubs such as Sales and Service, provide no access after termination.

Capture the contract versions in force at close#

Contract versions matter because the terms in force when records were created shape what the platform can later do with them. A help desk archive built under the add-on's customer terms may carry different permissions than tickets created after the platform rolls out its own paper.

Click-through terms are the easiest to lose, because the website that displayed them is usually redirected soon after close. Save dated copies of each document below and note where the signed originals live.

Which mistakes cost the most history?#

The mistakes that cost the most history are timing mistakes: exporting after a tool has already dropped to read-only mode, closing the email tenant during identity migration, or letting a reseller decommission a server before anyone checks what was on it. Each one turns a routine export into a recovery project.

Two quieter mistakes are just as common. Teams export the main objects but not the attachments, so tickets survive without the photos or documents they refer to. And archives are stored without an owner, so nobody knows later whether a folder of exports is complete, who may access it, or when it can be deleted.

One rule prevents most of this: no export counts as finished until someone has opened sample records from the archive, attachments included, on a machine that never had the original tool installed.

Illustrative: a restoration add-on on Jobber#

Illustrative: a fictional buy-and-build platform of roofing and restoration contractors acquires a regional restoration company that runs Jobber, a Google Workspace tenant and a hosted phone system that records calls. The integration plan moves the add-on onto the platform's ServiceTitan instance and cancels everything else.

The integration lead adds the records section. On day one the mail retention rule is paused and the Jobber admin login moves from the departing owner to a platform account. Before cancellation, the team exports jobs, estimates with revisions, invoices, technician notes and photos, plus the call recordings, and saves the homeowner agreement and work authorization forms in use at close.

The history survives the cutover. A later review treats homeowner photos and call recordings as personal data needing careful handling, while estimate revisions and job notes become the core of a possible license scope.

How SourceX works with an add-on's archive#

SourceX starts from the inventory the records section produces. In the Supply step of the SourceX five-step transaction, a metadata-only fit check uses system names, record families and years of history, so no exports leave the platform while the add-on is assessed.

If the records proceed, the archive's chain of custody becomes part of the provenance in the SourceX Evidence Packet, alongside licensing rights, permitted use, the privacy record and release authorization. Dated contract versions captured at close make the Rights step faster, and the platform approves every step.