CRM migration
Field-level mapping, validation, and rollback between Textline and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Textline
Source
Nutshell
Destination
Compatibility
6 of 9
objects map 1:1 between Textline and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Migrating from Textline to Nutshell means shifting from a messaging-first platform to a full CRM with a fundamentally different record architecture. Textline organizes around Conversations threaded to a Contact's phone number; Nutshell organizes around People, Companies, and Leads with Opportunities in a sales pipeline. We resolve that model gap by mapping Textline Contacts to Nutshell People, conversation history to Activity records on each Person's timeline, and Textline's Departments and Agent assignments to Nutshell's custom fields and User lookups. Textline's Automations, Routes, and Templates cannot migrate programmatically because they rely on Textline-specific routing logic and a template library with no standard CRM equivalent; we deliver a written inventory of these for the customer's admin to rebuild. API access must be confirmed on the Textline Standard or Pro tier before migration begins, as Essentials lacks the endpoints required for programmatic export.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Textline object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Textline
Contact
Nutshell
Person
1:1Textline Contacts in the Address Book map to Nutshell People. Core fields (name, phone, email, notes) migrate directly. Tags from Textline migrate as a flat tag list on the Nutshell Person record. Custom address book fields migrate to custom Person fields in Nutshell if the Textline account is on Standard or Pro; Essentials accounts have no custom fields to migrate.
Textline
Conversation
Nutshell
Activity (Task + Note)
1:manyTextline conversation threads map to Activity records on each Person's timeline in Nutshell. Each message becomes a Note attached to the Person, with direction (inbound/outbound), timestamp, and body preserved. Conversation-level metadata (department, routing tag) migrates as a custom field on the Activity. Because Textline lacks a bulk conversation export endpoint, we paginate and batch export per conversation, which extends the timeline for accounts with multi-year history.
Textline
Agent
Nutshell
User
1:1Textline Agents map to Nutshell Users by email address. Agent name and department assignment migrate as a custom Person field or a dedicated User custom field. Permissions and Custom Roles from Textline cannot migrate programmatically because Nutshell's role-based access model differs; we document the permission matrix for the customer's admin to configure in Nutshell Settings post-migration.
Textline
Department
Nutshell
Custom Field (Person) + Territory
lossyTextline Departments group phone numbers by location or function. The department-to-phone-number assignment migrates as a custom Person field in Nutshell. If the customer uses Nutshell Territory, we map Departments to Territory values as an alternative. The department-level routing logic tied to Textline Routes is documented separately and not migrated (Routes are not exposed via Textline's API).
Textline
Phone Number
Nutshell
Custom Field (Person)
1:1Textline phone numbers attached to Contacts map to the primary phone field on Nutshell Person. Additional phone numbers from multi-line Contacts migrate to a custom phone field in Nutshell. The association between phone number and department is preserved through the custom department field mapping.
Textline
Message Template
Nutshell
Email Template
1:1Textline Message Templates (canned replies) migrate to Nutshell Email Templates. Template body and shortcut codes transfer to Nutshell's template library. Customers should verify template behavior in Nutshell's editor because formatting and personalization token syntax differ between platforms.
Textline
Custom Address Book Field
Nutshell
Custom Field (Person)
lossyTextline custom address book fields (Standard and Pro tiers) migrate to Nutshell custom Person fields. We preserve field labels and value data; field types (text, dropdown, date) are recreated in Nutshell's field settings during the schema phase. If the destination Nutshell plan does not include unlimited custom fields (Enterprise), we flag any field count constraints before migration begins.
Textline
Announcement
Nutshell
Campaign (Activity Log)
1:1Textline Announcements (bulk outbound messages) cannot migrate as sending records in Nutshell because Nutshell's email marketing functionality is a separate Engagement Suite product. We export announcement history as an Activity log entry on the relevant Person records, documenting what was sent and when, so the customer has an audit trail even if the sending mechanism cannot be replicated.
Textline
Tag
Nutshell
Tag
1:1Tags applied to Textline Contacts migrate as Nutshell Tags on the Person record. Tag taxonomy and naming conventions are preserved as-is. Tags used for routing or segmentation in Textline are flagged as requiring manual reassignment review in Nutshell.
| Textline | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Conversation | Activity (Task + Note)1:many | Fully supported | |
| Agent | User1:1 | Fully supported | |
| Department | Custom Field (Person) + Territorylossy | Fully supported | |
| Phone Number | Custom Field (Person)1:1 | Fully supported | |
| Message Template | Email Template1:1 | Fully supported | |
| Custom Address Book Field | Custom Field (Person)lossy | Fully supported | |
| Announcement | Campaign (Activity Log)1:1 | Fully supported | |
| Tag | Tag1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Textline gotchas
API access requires Standard or Pro plan
HIPAA compliance is a paid add-on with separate configuration
Conversation export requires per-conversation manual action
Routes are not exposed via the public API
Custom address book fields are tier-gated
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Plan tier and API access confirmation
We confirm the Textline plan tier (Essentials, Standard, or Pro) during scoping to determine API availability. For Essentials accounts, we establish a CSV-first export strategy for Contacts and agree on a manual conversation export process. For Standard and Pro accounts, we test the Textline API endpoints for Contact, Conversation, Agent, and Department exports and document rate limits before building the export pipeline. If the account includes a HIPAA plan, we initiate the PHI handling checklist and BAA confirmation at this stage.
Schema design and custom field mapping
We design the Nutshell schema based on the migrated object inventory. This includes creating custom Person fields for department assignments, phone line labels, and any Textline custom address book fields. We map Tags to Nutshell Tags and define whether Announcement history will log as Activity records. Nutshell's custom field types (text, long text, currency, date) are matched to the source field data types during this phase. The schema is validated in Nutshell's sandbox or trial environment before production migration begins.
Contact and Agent export with owner resolution
We export Textline Contacts (with custom fields on Standard and Pro), Tags, Agents, and Department assignments. Agents are matched by email to Nutshell Users. Any Agent without a matching Nutshell User is held in a reconciliation queue for the customer's admin to provision. Contact export uses the Textline Address Book API endpoint; Agent export uses the Teams endpoint. The export outputs a row-count reconciliation report before the next phase begins.
Conversation history export and Activity mapping
We paginate through Textline conversation exports, batching by contact ID and applying rate-limit handling. Each message is mapped to a Nutshell Activity record on the corresponding Person timeline. Direction (inbound/outbound), timestamp, body, and MMS attachment references (where URLs are accessible) transfer to Nutshell. The customer is informed during scoping that this phase is the longest in the migration for accounts with extensive conversation history, and the timeline estimate is updated accordingly.
Production migration and reconciliation
We run the production migration into the live Nutshell environment in dependency order: custom Person fields first (so the schema is ready), then People records with Tags, then Activity history. After each phase, we emit a row-count reconciliation report and spot-check 20-30 records against the Textline source. Agents without a matching Nutshell User are resolved before People import to satisfy any ownership dependencies.
Cutover, handoff documentation, and post-migration review
We freeze Textline writes during cutover, run a final delta migration of any records modified during the migration window, and enable Nutshell as the system of record. We deliver the migration report, including a list of Textline Routes and Automations documented for manual rebuild in Nutshell's workflow tools, the Tags taxonomy mapping, and any HIPAA data handling sign-off. We support a five-business-day post-migration window for reconciliation issues. Workflow rebuild in Nutshell Pro or Business automation features is outside standard scope and is handled as a separate engagement.
Platform deep dives
Textline
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Textline and Nutshell.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Textline: Not publicly documented.
Data volume sensitivity
Textline doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Textline to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Textline to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Textline
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.
