TL;DR
- Cancel after proving that the destination can use the exported records, relationships, files and operating logic. A successful CSV download is only one part of an exit.
- Treat customer-owned CRM data, licensed enrichment and platform configuration separately. Their export routes and retention rights can differ.
- Use native exports for a simple, well-understood estate. Add migration tooling or specialist support when relationships, files, custom objects or downtime make the transfer materially harder.
- Budget for overlapping subscriptions, validation and a final change capture. Preserve suppression rules and evidence behind account decisions before switching automation on.
Define what must survive the exit
The useful question is not whether a vendor has an Export button. It is whether the team can continue the business process after access ends. A contact table without its account associations, opt-out history and open tasks may be technically portable while being operationally incomplete.
Build an exit inventory with five classes. Records include accounts, people, deals and custom objects. Relationships explain which person belongs to which buying entity and which opportunity owns an activity. Evidence includes source URLs, consent records, documents and dates. Logic includes filters, scoring, workflow conditions and field mappings. Access includes user roles, delegated connections and credential ownership.
Assign an owner and destination to every class. Do not put credentials themselves in the inventory. Record the secret store, authorised administrator and rotation procedure. Exported role names also need interpretation: a permission set in one application may have no direct equivalent in the destination.
Licensed enrichment needs its own decision. The fact that a field exists in your CRM does not establish unlimited rights to redistribute it, sell it or use it for a different purpose. Retain the provider and relevant contractual basis so the team can distinguish customer-entered information from licensed third-party information. This is contract due diligence, not a universal legal conclusion about all exports.
What the native export routes provide
Salesforce: schedule and scope the extraction
Salesforce's Data Export documentation describes weekly or monthly backup export availability depending on edition. For an exit, check the organisation's actual permission, schedule and selected object/file options rather than assuming that a report export contains the entire estate.
Native export is attractive where the administrator understands the object model and can map it to the destination. Keep original IDs alongside new IDs, and retain the field definitions needed to interpret custom fields. Validate separately that files, versions and object relationships required for the business process arrived.
A native backup is weaker as a complete migration service. It does not decide how a custom Salesforce object should become a destination object or rewrite the team's automation. Price extraction, transformation and destination loading separately. A tool that downloads files efficiently may still leave the hardest work, semantic mapping, with your administrator.
HubSpot: export by asset, then rebuild deliberately
HubSpot's content and data export guide describes separate routes for different assets and notes that moving between accounts can require importing objects or recreating data. That matters for an exit: records, website assets and operating configuration should not be assumed to travel as a single restorable package.
Native exports fit a team with a bounded set of standard records and a clear destination schema. Define the required associations, custom properties, activities and files before requesting the export. Keep original identifiers and association labels where available, and compare a known complex account in both systems.
Avoid pricing the move as “download contacts and upload contacts” if the marketing programme depends on lists, workflows or asset-specific behaviour. Recreating those assets is implementation work. Check permissions and exact export options in the account's edition; this article does not establish that every asset or association has identical availability in every HubSpot subscription.
Apollo: distinguish retained data from continued platform access
Apollo's current terms distinguish ending platform access from retaining certain Business Contact Information incorporated into your own records during the subscription, subject to its licence and restrictions. They also describe subscription-term and payment conditions. Read the applicable order form and terms together before assuming cancellation creates a refund or continued access.
For a data platform, preserve the records you are permitted to retain, the licence provenance and any downstream hygiene responsibilities. Do not treat a perpetual data licence as a perpetual live connection or a promise of refreshed data. Lists and workflows may depend on platform functions that disappear with access.
Apollo's removal-request guidance highlights the problem of previously exported data remaining in external systems. Include the ongoing suppression and update process in your replacement design. A retained record is not an instruction to keep contacting someone indefinitely.
Choose native transfer or specialist help
| Route | Suitable estate | Costs beyond the obvious fee | Reason to avoid it |
|---|---|---|---|
| Native exports and imports | Standard objects, clear mapping, manageable volume | Administrator time, overlap, validation | Complex histories or relationships exceed the team's skills |
| API or migration tooling | Repeated extraction, change capture, custom mapping | API quotas, connector subscription, engineering | A connector cannot represent the destination's missing object type |
| Specialist migration project | Complex customisation, low downtime tolerance, high-value history | Discovery, transformation, testing, cutover support | Scope and acceptance are undefined, leaving every exception chargeable |
Buy specialist help for a defined risk, not simply because there are many rows. A hundred thousand clean contact records can be easier than a few thousand deals with intricate custom relationships. Require a scoped statement of work naming objects, attachments, history, excluded assets, reconciliation and rollback support. The price basis may be fixed project, time and materials or a tool licence; no universal migration tariff is established here.
A reusable connector is worthwhile when the old and new systems will coexist or the same mapping must run repeatedly. For a one-time exit, a temporary extraction script may be sufficient. The key test is whether it can resume after a partial failure without creating duplicate records or skipping a page of results.
Move five systems without losing the account history
Consider a hypothetical estate with 100,000 customer/contact records spread across CRM, enrichment, outreach, support and an orchestration platform. Begin by identifying the authoritative record for each field. The CRM may own account ID, the support system owns ticket history and the outreach tool holds suppression state. Taking the newest value from every system is not a meaningful conflict policy.
Run a trial on 1,000 records including ordinary accounts and difficult cases: merged companies, multiple subsidiaries, deleted contacts, attachments and open opportunities. Preserve old IDs in an immutable crosswalk. A new contact should point to its new account through that crosswalk, rather than a fuzzy name match.
Rebuild one representative workflow before bulk migration. For example, an accepted account enters enrichment, receives a researched fit assessment and becomes a sales task only if it is not suppressed. Recreate the conditions and prove that an opted-out record remains blocked. Use the ABM Account Scoring Template to preserve the reasons behind prioritisation, not merely the final numeric score.
During cutover, freeze nonessential changes or capture a final delta after the bulk transfer. Record a boundary timestamp per system and the last processed event. If the outreach platform continues sending during migration, reconcile messages and suppression changes before re-enabling the destination. A single global timestamp can be misleading when systems have different clocks and asynchronous updates.
Keep the old system available until the destination passes acceptance, subject to the contract. Do not rely on an assumed grace period after termination. Confirm the last accessible day and download deadlines in writing while there is time to resolve a missing asset.
Price the exit before the cancellation deadline
Suppose the replacement work needs 80 hours at an assumed loaded $75 per hour, $600 of temporary tooling and $1,200 for one month of overlapping subscriptions. The hypothetical exit costs $7,800 before any specialist quote or exceptional data repair.
If leaving saves $900 a month in steady-state software fees, the simple payback is 8.7 months, rounded. That is $7,800 divided by $900. It ignores financing, tax and any operational improvement. If the replacement requires another $300 a month of support, the net saving falls to $600 and payback becomes 13 months.
Check the notice deadline, remaining committed fees, minimum term and auto-renewal clause early. A migration that finishes after the notice window may trigger another term even though the technical transfer succeeds. Obtain prices for read-only access or temporary overlap where offered; do not assume those commercial options exist.
Separate exit cost from the future stack's operating budget. A cheaper destination can still be a poor decision if it removes reporting or requires permanent manual reconciliation. The B2B data API guide provides context for the continuing synchronisation work after the move.
Prove that the new estate works
Reconcile counts by object and segment, but also test meaning. Open a known account and inspect its contacts, relationship labels, files, activity chronology and open work. Confirm that historical dates remain historical and that migration timestamps have not overwritten the event dates used for reporting.
Check permissions with ordinary users, not only the administrator who performed the import. Re-run suppression and routing cases. Generate the key reports from both systems and explain discrepancies before treating the new number as authoritative. Keep a rollback decision owner and a deadline, because indefinite dual operation creates its own conflicts.
The strongest exit outcome is an accepted destination plus a compact archive of necessary evidence and mappings. Keep only data you have a valid reason and basis to retain, with appropriate access. Our bulk-export guide and CRM data cleaning guide address adjacent purchases.
FAQ
Is a full CSV export enough to cancel safely?
Only if the business process needs nothing beyond the exported fields and the destination can reconstruct the required relationships. Test files, activities, custom objects, suppression and workflow logic separately. A readable spreadsheet proves extraction, not that the replacement can run the programme.
Can we keep third-party enrichment after cancellation?
The applicable licence and order form determine that. Some licences permit certain retained internal uses while restricting sharing, resale or other uses. Keep provenance and obtain a clear contractual answer for the intended destination and purpose. Do not infer retention rights from the fact that a download is technically possible.
Should we migrate every historical activity?
Preserve what supports ongoing work, reporting and required evidence. A searchable archive may be better than importing years of low-value events into the active CRM. Agree the retention and accessibility rules with the owners before excluding history, and prove that important deal context can still be retrieved.
When should we revoke the old integrations?
After the final delta, reconciliation and cutover acceptance, according to the change plan. Revoke delegated connections and rotate shared credentials that remain in use elsewhere. Keep a record of the revocation and destination owner so that old jobs cannot silently resume or continue writing after the exit.
