Clari Data Export and Migration Checklist

A Clari migration must preserve more than current opportunities. It must account for forecast snapshots, categories, rollups, inspection state, activity and communication context, custom mappings, CRM associations, audit history, and derived signals—within the customer’s actual contract, products, permissions, and retention terms.

This page owns Clari exit and migration. Use the Clari review for product fit, sales forecasting tools for replacement selection, and forecast accuracy for backtesting. Migration evidence cannot prove predictive quality.

Define the Clari exit boundary and rights

Start with the signed agreement, order forms, products, regions, and data roles. Record tenant, environments, Clari products/SKUs, term and termination dates, export-request window, customer-data definition, supplemental/derived-data treatment, APIs, reports, support package, fees, retention, return/deletion language, subprocessors, security evidence, and data-controller/processor roles. The buyer’s executed documents control—not a public webpage.

Clari’s public 2025 MSA says a customer may request Customer Data for export/download within a post-termination window and discusses exchange with customer third-party services. That is useful planning evidence, not a promise that every forecast snapshot, AI signal, audit event, call artifact, configuration, or relationship arrives in one portable schema.

Name business owner, finance/forecast owner, CRM admin, data owner, security/privacy reviewers, cutover commander, rollback authority, deletion approver and evidence custodian. Define what remains in CRM or email/calendar as the authoritative source and what exists only in Clari.

Inventory revenue data, configuration, and history

Create one manifest row per artifact or relationship. Inventory tenants, teams, hierarchies, users, roles, territories and permissions; accounts, contacts, opportunities and products; CRM fields, custom fields, mappings, transforms, filters, currencies, fiscal calendars and time zones; opportunity snapshots and changes; forecasts, calls/submissions, categories, adjustments, overrides, rollups, scenario inputs and hierarchy totals.

Add opportunity inspection views, notes, comments, next steps, close-date/stage changes, risks, alerts, signals, scores and AI-generated outputs; activity capture; calls, recordings where applicable, transcripts, summaries and coaching artifacts; emails, meetings, participants, calendar metadata and engagement history; audit logs, config history, admin events, integrations, API/service accounts, webhooks, exports, dashboards, saved views and reports.

For each row record source ID, CRM ID, stable business key, parent/child IDs, opportunity-account-contact-user associations, product/SKU, owner, creator, version, timestamps/time zone, snapshot/as-of date, currency, field schema, source/provenance, status, retention, permission, export path/format, checksum, target ID, transformation, validation, rollback and disposition. Apply the CRM migration controls to upstream records without treating a CRM re-sync as recovery of Clari-only history.

Label portability without assuming a complete export

Label every item documented export, support/contract-dependent, reconstructable, or unavailable. Documented means a current tenant/help/API/contract path plus a tested sample. Support-dependent means Clari must confirm scope, fields, format, delivery and cost. Reconstructable means an authoritative CRM, calendar, email or approved archive can recreate the business artifact. Unavailable means the owner accepts loss, retention, coexistence, or another plan.

Clari’s product tour spans forecast, inspection, capture, conversation intelligence, engagement, collaboration and AI workflows. That breadth expands the inventory; it does not prove equivalent export rights across products. Public sources reviewed here do not establish one complete export of all configurations, relationships, history and AI outputs. This is an evidence gap, not proof tenant tools, APIs, support, or contract cannot supply them.

A CRM opportunity can reconstruct its current fields, but not necessarily a historic Clari snapshot, submitted forecast, override rationale, inspection note, derived risk, model output or manager hierarchy as it existed then. Preserve provenance rather than flattening source and derived facts.

Request the contract and SKU manifest

Request an artifact-by-artifact manifest before cancellation. Ask Clari to map every purchased SKU to admin exports, reports, APIs, support deliveries and excluded artifacts. Require object/field dictionary, stable IDs, relationships, snapshot grain, full/incremental behavior, history window, timestamps, currency handling, user/deleted-owner behavior, pagination/limits, attachments/media, audit coverage, delivery encryption, expiry, request role, processing time, fee and support owner.

Ask how customer-provided, third-party, supplemental, calculated, aggregated, inferred and AI-generated data are classified under the agreement. Ask which artifacts can be returned, which can only be deleted, and which remain under legal or backup limitations. Do not equate privacy access, return, deletion, or CRM data exchange with application interoperability.

Freeze a snapshot and final delta

Take a versioned full snapshot, freeze changes, then capture the final delta. Record extraction tenant/environment, requester, method, filters, as-of time, timezone, fiscal period, currencies, schema/API/report version, page/file/row counts, bytes, checksums, encryption and secure location. Preserve originals beside the manifest.

Freeze hierarchy, category, field mapping, formula, filter, currency, fiscal calendar, forecast configuration, integration, user and permission changes. Log approved emergencies. Capture all records and relations changed after the snapshot: new opportunities, stage/amount/close-date changes, forecast submissions/overrides, notes, risks, activities, owner/team changes, deleted/merged records, and corrected exports.

Reconcile counts, fields, edges, and history

Reconcile counts, fields, relationships, and time-indexed history separately. Count by object, status, owner/team, fiscal period, category, currency and snapshot date. Field tests cover nulls, enums, precision/scale, currency conversion inputs, Unicode, long text, timestamps and deleted markers. Relationship tests verify opportunity-account-contact-owner-team, forecast-hierarchy, snapshot-opportunity, activity-participant, note/AI-output-source and CRM associations.

History tests confirm earliest/latest snapshots, sequence/order, version, created-versus-effective time, overrides and audit attribution. Reconcile in both directions: each manifest item has one delivered/reconstructed/accepted-loss disposition, and every delivered row/file maps back to one source object and allowed scope. List missing, duplicate, orphaned, truncated, transformed and unknown items; do not hide them inside an aggregate.

Use checksums for immutable files and stable hashes for normalized record sets where appropriate. A matching total forecast can conceal wrong opportunity membership, double currency conversion, stale hierarchy, or overwritten history. Finance and forecast owners approve business semantics, not just file readability.

Stage the target and shadow decisions

Load representative data into a non-authoritative target. Include multiple hierarchies, currencies, fiscal periods, categories, overrides, owner changes, merged/deleted CRM records, sparse and dense histories, missing fields, conflicting activity, and edge timestamps. Verify target IDs, associations, rollups, permissions, source attribution, history display, search, reports and audit.

Shadow the same frozen opportunity population and compare decisions without letting the target write to CRM or become the official forecast. Differences are investigation inputs, not automatic errors: products may implement different category, hierarchy and model semantics. Migration acceptance is accurate preservation and controlled authority; forecast quality needs its own backtest.

Cut over live authority and prove rollback

Transfer one authority at a time. Freeze final changes, capture/reconcile the delta, stop or drain Clari sync/write jobs, enable the target’s approved read scope, then forecast submission, reporting and CRM writes only after each gate. Store which system owns each field, snapshot, hierarchy, alert and decision during every phase.

The kill switch stops target writes and submissions while preserving logs. Rollback disables target jobs, restores approved Clari/CRM mappings and permissions, identifies target-created records, corrects CRM state, and replays only proven missing events. Rehearse with seeded failures. Follow the automation migration checklist for queues, retries, webhooks and duplicate actions.

Revoke, decommission, and collect deletion evidence

Revoke only after acceptance and rollback expiry. Disable users/service accounts, SSO/SCIM, APIs, OAuth, CRM/email/calendar/conversation connectors, webhooks and scheduled deliveries; rotate secrets; stop billing; update inventory, diagrams, runbooks, owners and incident contacts. Verify late callbacks cannot restore write authority.

Clari’s privacy policy describes enterprise information, retention and deletion limitations. Its DPA describes return/deletion subject to agreement and law. Confirm the executed versions, request scoped evidence for tenant data, logs, backups and subprocessors, and record exceptions. Deletion evidence is not proof of portability or instant erasure of every permitted retained copy.

Apply the worked example and calculate TCO

Synthetic example—not a Clari export result: a manifest expects 150 users/teams/config items, 2,000 opportunities, 24,000 snapshots, 600 forecast submissions/overrides, 18,000 activities/communications and 1,250 notes/risks/AI outputs: 46,000 artifacts. Delivery/reconstruction accepts 45,850; 100 are approved reference-only and 50 unresolved. Accounted rate is 45,950/46,000 = 99.9%, but an unresolved hierarchy-to-forecast edge remains a hard gate.

The manifest expects 62,000 edges and accepts 61,900: 99.8%. Report the 100 missing edges by type. Ten missing historical comment links may be accepted; one current opportunity assigned to the wrong forecast owner may block cutover. Publish severity and disposition, not only percentages.

TCO = Clari export/API/support + internal inventory/review + secure archive + reconstruction + target licenses/import + integrations + overlap + finance/security/privacy/legal + staging/reconciliation + training + incident/rollback + decommission/deletion + future exit − retired costs. Model SKU-specific export limits, extended overlap, media/storage, API volume, manual history rebuild and contract timing.

Print the Clari migration checklist

A defensible Clari exit preserves the revenue record with its provenance and relationships, moves authority deliberately, and states exactly what could not move—without converting broad contract language into an undocumented complete-export claim.