By Siddharth GangalA Nooks exit is a telephony shutdown and evidence-preservation exercise, not merely a contacts download. The source can hold active dial sessions, future tasks, callbacks, caller IDs, voicemail settings, recordings, transcripts, coaching, CRM associations, suppression, permissions, carrier state, and reporting history. If dialing or CRM logging continues during extraction, the migration begins with a moving and potentially unsafe population.
Official public documentation was reviewed August 8, 2026. Gangly did not operate a Nooks tenant, inspect an API, export recordings, or test a carrier transfer. Public documentation establishes a narrow call-data export path and several reporting/integration behaviors, but not universal portability of configuration, media, analytics, permissions, or history. Missing public evidence is a support/contract question, not proof that a path is absent.
Define the Nooks exit boundary
This route owns incumbent export, controlled dialing stop, reconciliation, cutover, rollback, and closure. Use the Nooks connect-rate test for performance validation, the sales dialer guide for category selection, and the existing comparison for product fit. None replaces an exit runbook.
Freeze workspace, contract, plan, seats, CRM/SEP, telephony relationships, numbers, target, archive, legal holds, cutoff, canary, rollback, cancellation, retention, deletion, and number-port dates. Assign Nooks, CRM, telecom, sales operations, security, privacy, legal, finance, recording, validation, target, and rollback owners.
Predeclare hard gates: no unauthorized or duplicate call; complete do-not-call and consent state; correct caller identity; accepted critical recordings and CRM associations; preserved recording/notice controls; no unowned number; visible failures; least privilege; tested rollback; and decommission evidence. An overall match rate cannot compensate for one lost suppression record.
Inventory people, numbers, calls, coaching, CRM, and governance
Inventory workspaces, floors, users, managers, teams, seats, roles, permission profiles, SSO, service identities, numbers, number pools, caller IDs, registrations, local-presence rules, carrier accounts, spam-label settings, dialing modes, line counts, AMD/virtual-assistant settings, calling hours, time zones, recording rules, voicemail scripts/drops, and audio devices.
Add lists, CSVs, Smartlists, people, accounts, opportunities, sources, enrichment, cadences, sequences, call and follow-up tasks, dispositions and mappings; attempts, connects, canceled calls, recordings, transcripts, summaries, notes, objections, coaching, scorecards, analytics, reports; CRM/SEP IDs, field maps, owners, activity IDs, write rules, errors, retries and backfills.
Record suppression, DNC source, consent evidence, recording notice/consent, complaints, opt-out history, retention, holds, deletion state, webhooks, OAuth, extensions, integrations, support exports and audit history. Each row needs stable ID, parent/edges, authority, owner, count, date range, format, portability label, source, target, legal class, validation test, and evidence. Coordinate any system-of-record change through the CRM migration checklist.
Build the portability matrix from verified paths
Use documented exportable, buyer verified, support/contract dependent, reconstruct, and unavailable. Capture URL/ticket, edition, role, path, filters, format, schema, maximum range, media/history/relationship coverage, sample result, errors, and test date.
Nooks documents that CSV-origin call data such as duration, disposition, and notes can be viewed and exported from Reporting → Team Dialing Report → Call Browser → Calls Library in its CSV dialing guide. It also says CSV prospects are user-specific and do not sync to an external system. This supports that narrow workflow, not a complete workspace export.
Default lists, people/accounts, mappings, scripts, cadences/tasks, recordings, transcripts, coaching, analytics definitions, users/teams, permissions, number/carrier/spam settings, and complete history to buyer-verified or support/contract dependent until an accepted path proves otherwise. Request a vendor manifest covering objects, stable IDs, relationships, timestamps, media, history, formats, limits, exclusions, retry, final delta, retention, and deletion.
Map IDs, relationships, authority, and reporting populations
Build edge tables for workspace→floor→team→user; user→seat/permission; number→caller ID→registration/carrier; list/sequence→task→person; person→account/opportunity; call attempt→number→user→task; call→recording→transcript→summary/disposition; call→CRM activity/object/owner; disposition→DNC/follow-up automation; and coaching/scorecard→call/user/manager.
Preserve Nooks IDs where available, plus CRM/SEP IDs, normalized numbers, UTC timestamps, owner, external call/carrier ID, attempt/result, media IDs, and authority. Use the CRM integration guide to assign write ownership. A call in both systems is not matched until person, account, owner, task, disposition, time, and outcome edges agree.
Nooks states in its reporting documentation that canceled calls from parallel dialing do not appear in Reporting. Preserve separate populations for requested tasks, initiated attempts, canceled parallel attempts, carrier attempts, completed calls, connections, recordings, CRM activities, and report rows. Never treat one report total as the universal denominator without proving inclusion rules.
Stop dialing and preserve suppression before the final delta
- Freeze users, teams, numbers, caller IDs, lists, sequences, tasks, modes, line counts, dispositions, automations, mappings, recording, permissions, and integrations.
- Record active sessions, loaded queues, callbacks, overdue/future tasks, in-progress calls, pending media/summaries, CRM logging queues, retries and errors.
- Stop new list/task ingestion and Smartlist generation. Pause new dialing, then drain or explicitly cancel attempts and callbacks in a vendor-confirmed order.
- Keep DNC, opt-out, consent withdrawal, complaint, callback, CRM logging, recording finalization, and backfill paths running until final delta capture.
- Prove source dialing is disabled with negative tests and record owner plus UTC time.
Do not deactivate numbers, carrier registration, extensions, or CRM credentials before pending records and media settle. Every queued call needs a completed, canceled, transferred, or exception state so it cannot silently reappear after rollback.
Preserve snapshot, final delta, media, and manifests
Take a pre-stop snapshot, execute the stop plan, then capture a final delta containing late outcomes, DNC changes, callbacks, recordings, transcripts, summaries, coaching, task state, CRM writes, errors and backfills. Keep read access until exports are reproducible, acceptance is signed, number moves settle, and rollback expires.
For each file/batch record workspace, path/API/ticket, filters, range, time zone, schema/version, file, format, rows, bytes, pages, media count/duration, exclusions, errors, requester, source time, and SHA-256. NIST’s Secure Hash Standard supports identity checking; a hash does not prove rows, audio, transcript turns, edges, or history are complete.
Keep raw data/media unchanged. Transform versioned copies and log mappings, code, rejects, manual edits, re-encodes, timezone conversion, disposition normalization, redaction, and speaker mapping. Secrets stay in a secret manager; the manifest references their owner and revocation evidence.
Reconcile counts, fields, media, edges, and history
- Count reconciliation = accepted artifacts ÷ eligible source artifacts per frozen population.
- Field fidelity = correctly transferred values ÷ eligible tested values.
- Media coverage = accepted playable required recordings ÷ eligible required recordings.
- Transcript fidelity = accepted speaker-linked transcripts ÷ eligible transcripts.
- Edge reconciliation = correct user, number, task, person, account, media and CRM edges ÷ eligible edges.
- History coverage = accepted required events, errors, retries and overrides ÷ eligible history.
Full-reconcile DNC/consent, caller IDs, active numbers, callbacks, critical calls, CRM mappings, permissions and held recordings. Stratify by team, user, number, mode, region, date, disposition, source, CRM, media state, result and error. A playable recording attached to the wrong person fails.
Nooks documents causes of missing calls in reporting or CRM, including mapping, authorization/permission, network and navigation behavior, and says support can often backfill missing calls. Query source, CRM and carrier populations; request scoped backfill; preserve the ticket; and rerun reconciliation before cancellation. “Often” is not a guarantee.
Stage the target and dual-run one calling authority
Build target users, roles, numbers, identity, lists, tasks, dispositions, suppression, recording rules, CRM mappings and monitoring while calling remains disabled. Seed consented golden cases for no answer, connect, voicemail, wrong number, DNC, callback, meeting, recording on/off, CRM update, duplicate, replay, late event, revoked token, changed owner, merged contact, carrier rejection and missing media.
A read-focused Nooks connector documents scoped access to users, teams, calls, transcripts and reporting plus revocation. Treat the connector documentation as a discovery clue, not a complete migration API. Verify authorization, limits, source exclusions, permitted extraction, and reproducibility.
During dual run, only one system may originate production calls, create callbacks, write dispositions, or mutate the same CRM activity. The other runs disabled golden tests or shadow comparison. Compare suppression, number/caller identity, task selection, associations, media, errors, operator effort and cost.
Cut over with hard gates and prove rollback
Approve a canary only when Nooks dialing tests disabled; the final delta and critical media are accepted; DNC/consent is complete; caller identity and number authority are approved; CRM/media edges reconcile; target golden cases pass; monitoring works; and rollback is rehearsed. Start with a small, consented, low-risk list and named reps.
The runbook states source stop, delta cutoff, target activation, number/carrier/provider changes, CRM transfer, canary size, validation query, monitoring interval, abort owner, and rollback deadline. Rollback stops target dialing first, preserves target-only calls/DNC/callbacks, restores approved source configuration, imports new suppression, and blocks replay.
Stop for unauthorized/duplicate dialing, lost DNC, misleading caller ID, unapproved recording, wrong CRM association, missing required media, invisible failure, unowned number, or untested rollback. Coordinate legal review with the recording-consent guide; rules vary and this is not legal advice. Give reps a bounded execution path through the cold-call checklist after the target passes its controls.
Decommission numbers, connectors, access, and data
After acceptance and hold review, remove dialing rights; port, release, or park numbers under written ownership; disable source routing; disconnect CRM/SEP, enrichment, calendar and AI connectors; revoke OAuth, API keys, webhooks, extensions, SSO, service users and vendor support access; rotate secrets; remove allowlists; and test access fails.
Submit a contract/DPA-governed return/deletion request covering people/accounts, lists, calls, recordings, transcripts, summaries, coaching, analytics, CRM mappings, DNC/consent, logs, exports, support artifacts, subprocessors, caches, backups, holds and exceptions. Accessible documentation did not establish universal retention/deletion timing. Obtain written scope, retained exceptions, protection/expiry, and completion evidence. Cancellation or number porting is not deletion.
Apply the worked example and calculate TCO
This fictional arithmetic is not a Nooks result. A team accepts 11,760 of 12,000 eligible completed call rows; 3,840 of 4,000 required playable recordings; 17,280 of 18,000 critical edges; all 1,200 DNC records; and 475 of 500 reporting/CRM exceptions.
| Control | Calculation | Result |
|---|---|---|
| Call rows | 11,760 ÷ 12,000 | 98% |
| Required media | 3,840 ÷ 4,000 | 96% |
| Critical edges | 17,280 ÷ 18,000 | 96% |
| DNC | 1,200 ÷ 1,200 | 100% |
| Exceptions | 475 ÷ 500 | 95% |
Do not average controls. DNC passes its hard gate; media/edge gaps remain exceptions or blockers. TCO = source overlap/exit support + target license/setup + number/carrier porting + export/support + media storage/transfer + reconstruction + CRM/telecom engineering + security/privacy/legal + testing + monitoring + rollback + archive + deletion. Use written quotes and measured labor.
Print the Nooks migration checklist
| Control | Evidence | Status |
|---|---|---|
| Scope, numbers, holds, owners and cutoff frozen | Signed charter | □ |
| Users, lists, tasks, calls, media, CRM and governance inventoried | Artifact/edge register | □ |
| Portability labels accepted | Docs, tickets, sample | □ |
| Dialing stopped; DNC/callback capture safe | UTC log/negative tests | □ |
| Snapshot, delta, media and manifests preserved | Counts/hashes/exceptions | □ |
| Reporting, CRM and carrier populations reconcile | Signed report/backfill | □ |
| Disabled stage, one-authority canary and rollback pass | Golden-case logs | □ |
| Numbers, credentials, connectors and accounts closed | Port/revoke tests | □ |
| Deletion scope and exceptions evidenced | Closure pack | □ |
Gangly is not a dialer, carrier, number host, or destination for Nooks configuration/media. If used around a replacement calling tool, evaluate its rep workflow independently; do not treat it as proof that Nooks data or telephone authority transferred.