Migrate your Checkbox data
No-code intake and workflow automation platform for in-house legal teams, handling everything from initial requests through approval routing and obligations tracking.
In its favor
Why people choose Checkbox
The signal that keeps Checkbox on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Legal teams choose Checkbox because it removes the need to write code when building intake forms and approval workflows, allowing legal operations staff to automate without developer involvement.
Organizations with large in-house legal departments (65+ and 85+ member teams at enterprise companies) select Checkbox to centralize and standardize how the business submits legal requests.
Checkbox integrates directly with tools legal teams already use, including Salesforce, Slack, Ironclad, and email, reducing friction between the intake layer and downstream systems.
Teams value the SOC 2 and ISO 27001 certifications when evaluating Checkbox for sensitive legal data, as in-house counsel handles confidential contracts and obligations.
The platform offers dedicated AI capabilities for legal workflows, including AI chatbots and document automation, attracting teams looking to augment manual processes with generative features.
Advanced customization for complex, multi-branch workflows requires deeper technical understanding, leading some teams to outgrow the no-code builder and seek more flexible alternatives.
As legal teams scale workflows across jurisdictions or business units, the platform's simplicity can become a constraint when trying to express nuanced conditional logic.
Some users report that while the platform is intuitive for basic automations, more tailored use cases require additional support or developer involvement.
Pricing is opaque and requires direct sales engagement for enterprise tiers, which creates friction for teams evaluating migration or trying to budget accurately.
Reasons to switch
Why people leave Checkbox
The recurring reasons buyers give for replacing Checkbox. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Checkbox fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Checkbox pricing overview
Checkbox uses an annual subscription model based on the number of admin users and email volume tiers. The Basic plan starts at $450 per year for one admin, scaling to $3,450 per year for the Team tier with 15 admins and 100,000 monthly emails. Enterprise pricing requires direct engagement with the sales team.
Basic
Tier 1 of 4
$450 per year
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Checkbox's schedule — see our quote-based pricing →
What gets migrated
Checkbox object support
Object-by-object support for Checkbox migrations. Per-pair details surface during scoping.
Intake Requests
Fully supportedIntake requests are the primary record type. Standard fields include requester details, submission date, priority, and status. We export all standard fields and map them directly to the destination schema.
Workflows
Not in this platformWorkflows define the automation logic and step sequences. These are stored as proprietary JSON structures with trigger-action conditions. We do not migrate workflow definitions as they cannot be reliably reconstructed outside Checkbox. We document the workflow structure so it can be rebuilt on the target platform.
Workflow Steps
Mapping requiredSteps are the individual nodes within a workflow. We export step names, sequence order, assigned owners, and conditional branching logic. Step-level trigger conditions require manual reconstruction at the destination.
Users and Teams
Fully supportedUser profiles and team structures are standard records with names, emails, roles, and team assignments. We map these 1:1 to the destination system. User IDs cannot be preserved across platforms.
Integration Connections
Mapping requiredCheckbox integrates with Slack, Salesforce, Ironclad, and email. We export the integration names and configuration types. API credentials and OAuth tokens cannot be migrated and must be re-established on the destination platform.
Attachments
Fully supportedFile attachments associated with intake requests are exported with their parent record reference. We preserve file names, upload timestamps, and download URLs where accessible.
Custom Fields
Mapping requiredCustom fields added to intake forms are exported as key-value pairs. Field type metadata (text, date, dropdown, etc.) is preserved in the export. Destination systems may require custom field recreation.
Audit Logs
Fully supportedAudit logs capture status changes, user actions, and timestamped events on each intake request. We export these as supplementary records tied to their parent request for compliance continuity.
AI Workflow Features
Mapping requiredCheckbox exposes AI-powered document generation and chatbot features on certain plans. AI workflow references are exported as metadata. The AI logic itself cannot be transferred.
| Object | Support | Notes |
|---|---|---|
| Intake Requests | Fully supported | Intake requests are the primary record type. Standard fields include requester details, submission date, priority, and status. We export all standard fields and map them directly to the destination schema. |
| Workflows | Not in this platform | Workflows define the automation logic and step sequences. These are stored as proprietary JSON structures with trigger-action conditions. We do not migrate workflow definitions as they cannot be reliably reconstructed outside Checkbox. We document the workflow structure so it can be rebuilt on the target platform. |
| Workflow Steps | Mapping required | Steps are the individual nodes within a workflow. We export step names, sequence order, assigned owners, and conditional branching logic. Step-level trigger conditions require manual reconstruction at the destination. |
| Users and Teams | Fully supported | User profiles and team structures are standard records with names, emails, roles, and team assignments. We map these 1:1 to the destination system. User IDs cannot be preserved across platforms. |
| Integration Connections | Mapping required | Checkbox integrates with Slack, Salesforce, Ironclad, and email. We export the integration names and configuration types. API credentials and OAuth tokens cannot be migrated and must be re-established on the destination platform. |
| Attachments | Fully supported | File attachments associated with intake requests are exported with their parent record reference. We preserve file names, upload timestamps, and download URLs where accessible. |
| Custom Fields | Mapping required | Custom fields added to intake forms are exported as key-value pairs. Field type metadata (text, date, dropdown, etc.) is preserved in the export. Destination systems may require custom field recreation. |
| Audit Logs | Fully supported | Audit logs capture status changes, user actions, and timestamped events on each intake request. We export these as supplementary records tied to their parent request for compliance continuity. |
| AI Workflow Features | Mapping required | Checkbox exposes AI-powered document generation and chatbot features on certain plans. AI workflow references are exported as metadata. The AI logic itself cannot be transferred. |
Gotchas
What to watch for in Checkbox migrations
Issues we've hit on past Checkbox migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Workflow JSON is not portable across platforms
API capabilities are not publicly documented
Integration tokens and OAuth connections cannot be migrated
| Severity | Issue |
|---|---|
| High | Workflow JSON is not portable across platforms |
| Medium | API capabilities are not publicly documented |
| Medium | Integration tokens and OAuth connections cannot be migrated |
Leaving Checkbox?
Where Checkbox customers move next
12 destinations Checkbox can migrate to.
How a Checkbox migration works
Four steps, Checkbox-specific
Connect
OAuth 2.0 and JWT (REST/JSON API) into Checkbox. Scopes limited to read-only on the data we move.
Map
We translate Checkbox-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Checkbox quirks before production.
Migrate
Full migration with Checkbox rate-limit handling. Rollback available throughout.
FAQ
Checkbox migration FAQ
Answers to the questions buyers ask most during Checkbox migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Checkbox migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Checkbox.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Checkbox setup and destination — written quote back within a business day.