Move your team from Spellbook to Harvey.
Each person gets a short interview, then a personalized step-by-step guide showing exactly where their saved work, prompts, and projects land in Harvey — and the few things that need a manual step, walked through. You send one invite; nobody becomes the help desk, and nothing in Spellbook is changed or cancelled. Want to see where you’re paying for both first? Run the free audit.
Harvey Agents execute end-to-end multi-step legal workflows (due diligence data room review, fund formation document prep) without manual handoffs between steps. Spellbook Associate handles multi-document tasks such as cross-document redlining and research autonomously across related contracts. To move from Harvey to Spellbook: identify the Harvey agent workflows your team uses most (e.g., due diligence data room review) and map each to Spellbook Associate tasks — upload the document set to Associate and configure the task prompt to match the output Harvey was producing. To move from Spellbook to Harvey: replace Associate multi-document jobs with Harvey Agent templates; Harvey's pre-built agent templates for due diligence and deal management cover similar ground, and custom agents can be configured through the platform's enterprise configuration panel. In both directions, agent output formats differ — plan time to adapt any downstream templates or reporting formats before cutover.
- Warning: Harvey Agents include pre-built templates for due diligence and fund formation; Spellbook Associate is more general-purpose and does not publish named workflow templates, so comparable workflows must be configured via task prompts.
- Warning: Harvey Agent customization is an enterprise-tier feature and depends on firm-level configuration agreements; Spellbook Associate is bundled with the Suite plan (Law Firm and In-House) but requires teams of 10+ for dedicated support.
- Warning: Harvey Agents chain document retrieval, analysis, drafting, and output packaging across connected DMS sources; Spellbook Associate requires documents to be uploaded to its own interface and does not pull from iManage or NetDocuments directly.
Harvey's AI Assistant handles document drafting via freeform prompts in the web app or Word/Outlook add-ins, drawing on firm precedents from connected DMS sources. Spellbook's Draft feature (inside the Word Add-In) generates clauses and full documents from natural-language prompts against the team's saved precedent library. To move from Harvey to Spellbook: upload or link your key precedent documents into Spellbook's precedent library via the admin panel so the Draft feature has firm-standard language to draw from; then switch drafting workflows to the Spellbook Word Add-In. To move from Spellbook to Harvey: connect Harvey to the same SharePoint, Google Drive, iManage, or NetDocuments source holding your precedents, then use the Harvey web app or Word add-in to prompt for new drafts — Harvey's assistant retrieves grounded firm language from the connected corpus. In both directions, save accepted output as new precedents in the destination system before decommissioning the source.
- Warning: Harvey's drafting assistant is accessible via web app, Word, Outlook, browser extension, and mobile; Spellbook Draft is Word-only, so drafting on mobile or in non-Word workflows is not possible on Spellbook.
- Warning: Spellbook's precedent library is explicitly curated by an admin; Harvey pulls from connected DMS repositories directly, which means Harvey can surface more documents but with less curation control.
- Warning: Spellbook supports clause-level iteration (rapid revision prompts); Harvey's assistant handles freeform multi-turn conversation, so iterative drafting feels different and may require workflow habit changes.
Harvey's AI Assistant answers freeform legal questions about uploaded or DMS-linked documents with cited, grounded responses. Spellbook's Ask feature (inside the Word Add-In) answers natural-language questions about the open document and returns answers with specific clause citations. To move from Harvey to Spellbook: teams running deal-review Q&A in Harvey's web app should shift those workflows to opening the target contract in Word and using the Spellbook Ask panel; answers reference exact clauses and page numbers, matching Harvey's citation practice. To move from Spellbook to Harvey: upload the contract to Harvey's web app or pull it from a connected DMS, then ask questions in the assistant chat — Harvey returns cited answers with source document references. In both directions the Q&A history is not transferable; capture key findings in a memo or matter management system before switching tools.
- Warning: Harvey's assistant can answer multi-document questions spanning several uploaded files simultaneously; Spellbook Ask operates on the single document currently open in Word.
- Warning: Harvey Knowledge connects to LexisNexis and 500+ legal databases for regulatory and case-law context in Q&A answers; Spellbook Ask is limited to the content of the open contract and does not pull external legal authority.
- Warning: Spellbook Ask requires Microsoft Word to be running on desktop; Harvey supports web, mobile, and browser extension for Q&A, offering more flexibility for attorneys working outside of Word.
Both products analyze contracts clause-by-clause against a configurable playbook and return risk flags and redline suggestions. To move from Harvey to Spellbook: export any firm playbook positions documented in Harvey (typically maintained as Word or PDF standards), then re-configure them in Spellbook's playbook admin UI before your first review. Open contracts in Microsoft Word with the Spellbook Add-In and run Review — the playbook comparison and inline redlines replace Harvey's Contract Intelligence output. Moving the other way (Spellbook to Harvey): Harvey ingests DOCX files uploaded directly to the web app or pulled from iManage/NetDocuments/SharePoint; configure Harvey's playbook templates to match the standards you had in Spellbook, then use the Word add-in or web app for review. In both directions, historical redline runs are not portable — capture accepted positions in the destination playbook before cutover.
- Warning: Harvey's Contract Intelligence also supports bulk portfolio analysis via Vault; Spellbook's review is single-document at a time in Word, so bulk pipeline workflows require a different approach on Spellbook.
- Warning: Spellbook operates exclusively inside Microsoft Word (DOCX); Harvey additionally supports a browser-based web app, so teams not standardized on Word lose interface flexibility when moving to Spellbook.
- Warning: Playbook configuration in Spellbook is per matter type and managed by an admin — re-building the equivalent of Harvey's firm playbooks takes upfront setup time before the switch is live.
Harvey Vault acts as a centralized, searchable corpus of the firm's documents — uploaded files are encrypted at rest, semantically indexed, and made available to the AI assistant and agents for grounded answers and drafting. Spellbook's precedent library in the Draft feature serves an analogous purpose for drafting: saved precedents act as the firm's curated document corpus that the AI draws on when generating new clauses or documents. Migrating from Harvey to Spellbook: before decommissioning Harvey Vault, export key precedent documents (NDAs, MSAs, SoW templates, etc.) from Vault via download or your connected DMS (SharePoint/Google Drive/iManage), then upload and tag them in Spellbook's precedent library via the admin panel. Migrating from Spellbook to Harvey: export the Spellbook precedent library as DOCX files and bulk-upload them to Harvey Vault or push them into the connected DMS that Harvey reads from; Harvey will index them and make them available to the assistant and agents without additional tagging steps.
- Warning: Harvey Vault supports bulk upload of large document collections (1.3M+ files processed daily across the platform) and DMS sync from iManage, NetDocuments, SharePoint, and Google Drive; Spellbook's precedent library is a manually curated list managed by an admin and does not have automated DMS sync.
- Warning: Harvey Vault provides semantic search across the entire uploaded corpus for arbitrary queries; Spellbook does not expose a standalone document search — precedents are surfaced only at drafting time, so the searchable knowledge-base use case does not transfer directly.
- Warning: Harvey Vault's retention and access policies are admin-controlled with role-based workspace separation; Spellbook's precedent library access is governed at the plan/team level without the same granularity of per-collection RBAC.
Both Harvey and Spellbook are SOC 2 Type II certified and contractually guarantee that customer data is never used to train AI models — so teams migrating between them can maintain their data-protection commitments without a compliance gap. When switching from Harvey to Spellbook: obtain Spellbook's Trust Center documentation and BAA (if HIPAA-relevant), verify that your jurisdiction's data-residency requirements are satisfied (Spellbook runs on AWS ca-central-1; Harvey offers US, EU/Switzerland, and Australia regional options), and update any vendor risk assessments or DPA addenda to reference Spellbook. Going from Spellbook to Harvey: request Harvey's SOC 2 report, ISO 27001/27701/42001 certificates, and DPA, then confirm the appropriate regional deployment matches your obligations; also validate SSO configuration (Harvey uses SAML; Spellbook uses Microsoft SSO with MFA). In both cases, export or archive any audit logs from the departing vendor before account closure since logs are not transferable.
- Warning: Harvey offers regional data isolation in the US, EU/Switzerland, and Australia; Spellbook's backend is AWS ca-central-1 (Canada) only, which may not satisfy EU or Australian data-residency requirements without additional DPA arrangements.
- Warning: Harvey holds ISO 42001 (AI management system) certification in addition to SOC 2 and ISO 27001; Spellbook's compliance documentation covers EU AI Act compliance but does not list ISO 42001, which may matter for enterprise procurement checklists.
- Warning: Spellbook has HIPAA BAA availability and PIPEDA coverage relevant to Canadian entities; Harvey's documented compliance framework is primarily US/EU-focused, so Canadian healthcare or government clients should verify PIPEDA coverage with Harvey's sales team.