Salesken Data Export and Migration Checklist

A Salesken migration is complete only when the buyer can prove which conversation and coaching artifacts were returned or archived, which CRM and user relationships survived, what remains subject to retention, and which source credentials and access were revoked. A dashboard export or CRM note does not establish custody of audio, transcripts, speaker turns, scorecard history, permissions, or consent evidence.

Accessible official Salesken pages were reviewed August 8, 2026. Gangly did not execute a Salesken export or receive private API documentation. An inaccessible or absent public page is not evidence that a capability is absent. Bind each path to the signed order form, terms, DPA, plan, permissions, vendor ticket, live tenant, and an accepted sample result.

Define the Salesken exit boundary

This page owns incumbent export, cutover, rollback, and closure. Use the sales coaching tools guide for target selection, the CRM migration checklist when CRM authority changes, the Gong checklist for Gong, and the conversation-intelligence integration guide for ongoing CRM authority.

Freeze tenant, contracts, seats, administrators, integrations, capture channels, storage, retention, legal holds, target, archive, snapshot, capture cutoff, rollback window, cancellation, and deletion dates. Name program, Salesken, data, CRM, telephony/conferencing, security, privacy/legal, target, finance, validation, rollback, and destruction owners.

Pre-register hard gates: zero unauthorized recordings or shares; accepted custody of critical eligible media and transcripts; preserved consent and hold state; complete critical CRM edges; correct permissions; one capture and write authority; visible extraction failures; tested rollback; revoked credentials; and documented deletion exceptions.

Inventory conversations, coaching, CRM, and governance artifacts

Inventory conversations, calls, and meetings; raw audio and video; transcripts, turns, timestamps, languages, and speakers; summaries, actions, owners, due dates, and completion state; topics, keywords, trackers, and moments; coaching prompts, recommendations, and feedback; scorecard and rubric definitions, versions, evaluations, manager notes, and history.

Add users, managers, teams, roles, inactive owners, and service identities; CRM account, contact, lead, opportunity, activity, and event IDs; custom fields, mappings, sync direction, and write authority; telephony, calendar, conferencing, and dialer IDs; permissions, shares, consent and notice evidence, retention, holds, deletion state, API clients, webhooks, SSO, audit history, errors, integrations, and support-created exports.

For every row record stable source ID, parent and edge IDs, owner, eligible count, authority, sensitivity, plan/right, extraction path, format, target disposition, retention, acceptance test, exception owner, and evidence URL. Preserve meeting-to-speaker, meeting-to-CRM, action-to-owner, and evaluation-to-rubric-version edges. A summary that names a task does not recreate structured action ownership.

Use the CRM data-quality framework to define field-level acceptance before any imported conversation output can influence reports or workflows.

Build an evidence-gap portability matrix

Use five labels: documented exportable, buyer verified, support/contract dependent, reconstruct, and unavailable. Since no accessible official complete export schema was verified, begin every Salesken-specific artifact as support/contract-dependent or unavailable. Upgrade a label only when Salesken supplies current documentation and the buyer reproduces a representative result.

Store the official URL or vendor ticket, plan, permission, filters, format, schema, pagination, limit, media expiry, relationship and history coverage, test date, and checksum. Product material about CRM integration does not prove export direction, stable IDs, retry history, or complete relationship portability.

Salesken’s terms and conditions identify Customer Data, state that customers retain ownership, and describe return or secure destruction of proprietary information on written request. Those provisions are contract-review inputs, not a self-service bulk-export specification.

Request the vendor object and relationship manifest

Before notice or cancellation, ask Salesken for a signed manifest listing every available object, field, stable identifier, relationship, version/history, eligible count, media format, permission, extraction method, rate and size limit, generation time, download expiry, assistance fee, exclusion, retention rule, backup treatment, subprocessor, and deletion evidence.

Ask explicit yes/no questions for raw audio/video; transcript turns and speakers; summaries and actions; topics and trackers; live or post-call coaching artifacts; scorecard versions and evaluations; comments; users and teams; custom fields; CRM associations; permissions; consent/notice; audit logs; and deleted records. Record “not supplied” instead of assuming reconstruction.

Require a sampled export before approving the runbook. Include private and shared conversations, multiple capture sources, more than one language, an inactive owner, edited scorecard, merged CRM contact, several opportunity associations, incomplete action, held media, and an artifact near any retention boundary. Compare vendor counts and files against the source UI.

Freeze capture and preserve snapshot plus final delta

1. Freeze users, teams, rubrics, topics, custom fields, mappings, permissions, recording rules, sharing, retention, and deletion.
2. Count scheduled, active, processing, failed, uploaded, held, and deleted conversations; define treatment for calls completing after cutoff.
3. Preserve configuration before stopping telephony, conference, calendar, dialer, upload, API, and CRM writers in a rehearsed order.
4. Record snapshot start and end in UTC, extraction identifiers, counts, files, errors, and exclusions. Log every approved post-snapshot change.
5. Capture a final ordered delta, including late transcripts, media, feedback, scorecards, and CRM writes. Keep source access until acceptance and rollback expiry.

During a controlled dual window, one system owns participant notice and capture, and only one writes CRM or sends downstream coaching events. Avoid duplicate assistants, recordings, activities, and notifications.

Preserve immutable files and reconcile counts, media, edges, and history

Preserve raw JSON, CSV, audio, video, transcripts, the vendor manifest, configuration evidence, and tickets unchanged in encrypted storage. Manifest tenant, operation or endpoint, filters, requester, UTC start/end, schema, filename, rows, bytes, media duration, errors, retries, exclusions, and SHA-256 digest. NIST’s Secure Hash Standard supports reproducible digests; a matching digest proves file identity, not semantic accuracy.

• Conversation reconciliation = accepted target or archive conversations ÷ eligible source conversations.
• Media reconciliation = playable and correctly linked media ÷ eligible media.
• Field fidelity = correct tested required values ÷ eligible tested values.
• Edge reconciliation = correct speaker, artifact, user/team, CRM, action-owner, and rubric edges ÷ eligible edges.
• History coverage = accepted required versions and events ÷ eligible documented history.
• Duplicate rate = unintended extra target objects ÷ eligible source objects.

Report denominators, exclusions, and results by team, owner, source, language, privacy, media type, CRM association, hold, and deletion state. Full-reconcile held media, permissions, consent, and critical CRM edges. A transcript without speaker/timestamp edges or an evaluation without its rubric version is incomplete.

Stage the target and run controlled dual capture

Load users, teams, roles, permissions, source-ID crosswalks, and CRM identities before conversations, media, transcripts and speakers, associations, and supported derived artifacts. Keep target capture, sharing, notifications, coaching automation, and CRM writes disabled during import.

Seed private calls, external shares, inactive owners, duplicate contacts, merged accounts, multiple opportunities, missing speakers, long media, languages, incomplete actions, edited rubrics, held calls, revoked tokens, and late processing. Replay an import for idempotency; interrupt media, duplicate or omit a page, reverse events, and deliver a late delta. Failures must be visible and recoverable.

Dual-capture only a bounded, consented meeting set with one CRM writer. Compare capture eligibility, participant notice, media, transcript structure, speakers, coaching artifacts, CRM association, permissions, retention, export, and deletion. This verifies transition mechanics, not destination superiority.

Cut over or roll back with hard gates

Write the exact sequence for source stop, final delta, manifest closure, transformation, target import, reconciliation, target activation, and monitoring. Name abort authority and decision deadline. Preserve the source read-only until critical gates pass.

Rollback disables target capture, sharing, notifications, and writes; exports target-only deltas; preserves conversations captured after cutover; restores only approved source connections; prevents duplicate bots, recordings, CRM activities, and coaching events; and notifies affected users. Rehearse rollback before production.

Stop on unauthorized recording or sharing, critical media loss, permission leakage, lost consent or legal-hold state, unacceptable CRM-edge loss, destructive duplication, invisible extraction failure, uncontrolled dual capture, or untested rollback. No average reconciliation score overrides these failures.

Decommission, revoke, and collect deletion evidence

After acceptance and hold review, revoke API keys, webhooks, OAuth, telephony, conference, calendar, dialer and CRM connections, SSO, service identities, public shares, guest access, user/admin access, and support access. Record timestamps and prove credentials and links fail.

Salesken’s terms publish an offboarding retention process for customer-collected data, including active-storage and backup/archive periods. Verify the exact current signed terms and DPA rather than relying on a summary. Submit a scoped return/destruction request listing raw and derived artifacts, integrations, logs, exports, subprocessors, backups, support copies, legal holds, and retention exceptions.

Collect request and ticket IDs, scope, dates, exceptions, expected backup expiry, and closure evidence. “Subscription canceled” is not equivalent to “governed customer artifacts deleted.” Apply privacy and minimization controls using an appropriate framework such as the NIST Privacy Framework and applicable counsel.

Apply the worked example and calculate TCO

This fictional arithmetic demonstrates the controls; it is not a Salesken result. Of 1,000 eligible conversations, 970 reconcile. Of 500 eligible media files, 480 play and link correctly. Of 2,000 critical edges, 1,920 reconcile. Of 800 required history events, 760 remain. Five unintended duplicate target conversations appear.

Missing held media or consent and critical CRM edges remains a hard stop. Migration TCO = source overlap + target setup and licenses + vendor export/support + engineering + media transfer/storage + mapping and validation + privacy/security/legal + training + monitoring/remediation + rollback + archive + decommission/deletion.

Print the Salesken migration checklist

Gangly does not make Salesken artifacts portable and is not the presumed target. If evaluated as a workflow layer, preserve CRM authority, consent, human review, permissions, idempotency, reconciliation, and failure recovery.