CRM migration
Field-level mapping, validation, and rollback between Aritic Sales CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Aritic Sales CRM
Source
Nutshell
Destination
Compatibility
9 of 10
objects map 1:1 between Aritic Sales CRM and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Aritic Sales CRM to Nutshell is a structural migration that requires resolving several data-model differences. Aritic allows linking a Contact to any unrelated Company for deal-influencer tracking, while Nutshell uses a standard Company-People hierarchy where each Person is tied to a primary Account. We translate Aritic's flexible relationship model by assigning a primary Company to each Contact, preserving secondary associations in a custom field note, and flagging any Contact with more than one associated Company for verification. Lead scores export as numeric values stored on the Person record, since Nutshell does not include native lead scoring. Workflow automation rules, segmentation rules, and sequence logic do not transfer in any format; we document the full active workflow inventory so your team can rebuild in Nutshell or configure Nutshell Automations manually. Activity history (calls, emails, meetings) migrates into Nutshell's activity feed against the resolved Person and Company records.
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 Aritic Sales CRM 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.
Aritic Sales CRM
Contact
Nutshell
Person
1:1Aritic Contact maps to Nutshell Person. The key migration challenge is resolving Aritic's flexible relationship model (any Contact linked to any unrelated Company) into Nutshell's Company-People hierarchy. We assign a primary Company to each Contact during import, record additional Company associations in a custom text field aritic_secondary_companies__c, and flag any Contact linked to three or more Companies for manual verification post-import. Email, phone, address, lifecycle stage, and custom properties map to Nutshell's standard Person fields or custom fields pre-created during scoping.
Aritic Sales CRM
Company
Nutshell
Account
1:1Aritic Company maps directly to Nutshell Account. Company name becomes Account name, domain becomes Website, address maps to the Account address fields, and industry maps to a custom or standard industry picklist. Account is imported first to establish the foreign-key reference for downstream Person imports. Multiple Contacts pointing to the same Aritic Company consolidate into a single Account with multiple Person records linked.
Aritic Sales CRM
Deal
Nutshell
Opportunity
1:1Aritic Deal maps to Nutshell Opportunity. The Aritic pipeline and stage assignment maps to Nutshell's pipeline and stage using a pre-configured stage name mapping created during scoping. Deal fields (name, value, close date, probability, created date, owner) map to Nutshell Opportunity fields. Aritic's 360-degree deal view data and milestone notes migrate as Opportunity notes or custom fields. Closed-won and closed-lost reasons map to custom fields in Nutshell.
Aritic Sales CRM
Pipeline + Pipeline Stage
Nutshell
Pipeline + Stage
lossyAritic pipelines map to Nutshell pipelines with stage names preserved. Nutshell Starter and Professional plans are limited to one pipeline; if Aritic has multiple active pipelines, we recommend upgrading to Nutshell Advanced ($42/user) or consolidating pipelines during migration. Stage order, names, and win/loss criteria are mapped during configuration. Stage-level automation triggers in Aritic do not transfer and are documented in the workflow inventory for rebuild in Nutshell Automations.
Aritic Sales CRM
Task
Nutshell
Activity
1:1Aritic Tasks map to Nutshell Activity records linked to the resolved Person and Account. Due date, assignee, completion status, and description preserve. Open and closed tasks migrate with full status history. Completed task history is preserved; any activity log beyond the task record itself may not carry forward in full detail.
Aritic Sales CRM
Activities (calls, emails, meetings)
Nutshell
Activity
1:1Aritic call, email, and meeting engagements merge into Nutshell's unified Activity feed. Each engagement type retains its category marker (call, email, meeting) so the activity timeline remains readable. Activity timestamp, participant (Person), related Company, and owner preserve. Meeting location and attendee data migrate as Activity notes or custom fields if Nutshell's standard fields do not capture the detail.
Aritic Sales CRM
Lead Scoring
Nutshell
Custom numeric field
1:1Aritic lead score values export as static numbers and migrate to a pre-created custom numeric field (aritic_lead_score__c) on the Nutshell Person record. The active scoring rule model (rules, weights, triggers, conditions) is proprietary to Aritic and does not export. We deliver a scoring-rule inventory sheet so the customer can recreate their model in Nutshell using custom fields and Nutshell Automations, typically one to two hours per complex scoring rule.
Aritic Sales CRM
Tags and Segments
Nutshell
Labels
1:1Aritic tags applied to Contacts and Deals export as comma-separated lists and map to Nutshell Labels on the Person or Account record. Segmentation rules built in Aritic (behavioral segmentation, dynamic lists) do not export and require manual rebuild in Nutshell or a third-party segmentation tool. Tags used for deal categorization migrate as Opportunity Labels or a custom multi-select field depending on Nutshell's current field structure.
Aritic Sales CRM
Custom Fields
Nutshell
Custom Fields
1:1Aritic custom fields on Contacts, Companies, and Deals are enumerated during scoping. We map each to a pre-created Nutshell custom field of matching type (text, number, date, dropdown). Dropdown fields require a value mapping if Aritic uses picklist values not present in Nutshell. Any Aritic formula-type fields or calculated fields are flagged as read-only; the calculated value at migration time imports as a static number or text field, and the customer documents whether the formula needs rebuilding in Nutshell.
Aritic Sales CRM
Owner
Nutshell
User
1:1Aritic Owner records map to Nutshell User by email match. Active owners resolve directly; inactive owners are preserved as read-only User records to maintain historical assignment on Deals, Tasks, and Activities. Any Owner in Aritic without a matching email in Nutshell goes to a reconciliation queue for the customer's admin to provision the User before record import continues.
| Aritic Sales CRM | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Pipeline + Pipeline Stage | Pipeline + Stagelossy | Fully supported | |
| Task | Activity1:1 | Fully supported | |
| Activities (calls, emails, meetings) | Activity1:1 | Fully supported | |
| Lead Scoring | Custom numeric field1:1 | Mapping required | |
| Tags and Segments | Labels1:1 | Mapping required | |
| Custom Fields | Custom Fields1:1 | Mapping required | |
| Owner | User1: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.
Aritic Sales CRM gotchas
Contact cap is a hard migration boundary on Free and Professional
Workflow automations do not export and must be rebuilt manually
Relationship linking creates non-standard Company-Contact associations
Lead scores export as static values, not active models
Invoice and quote attachments may be URL-based rather than stored files
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
Discovery and source audit
We audit the Aritic Sales CRM account across plan tier (Free/Professional), custom fields on Contacts/Companies/Deals, active pipeline count, workflow automation rules, engagement history volume, and tag/segment usage. We also identify any URL-based file attachments and verify the Aritic plan tier because the 200-contact cap affects how many records can be imported and which features are available. The discovery output is a written migration scope with record counts, custom field inventory, pipeline mapping plan, and workflow inventory.
Nutshell plan and schema preparation
We confirm the target Nutshell plan based on pipeline count (Starter/Professional for single pipeline, Advanced for multiple pipelines), engagement suite needs (email marketing, SMS, web chat as add-ons), and user count. We create all required custom fields in Nutshell before migration using the field names and types from the discovery audit, including aritic_lead_score__c, aritic_secondary_companies__c, and any custom dropdown value mappings. We configure pipeline stages matching the Aritic stage names and order.
Relationship model resolution and staging
We resolve the Contact-to-Company relationship model before import. For each Aritic Contact, we identify the primary Company by treating the first-linked or highest-weighted Company association as primary. Additional Company associations serialize into aritic_secondary_companies__c as a semicolon-separated list. Contacts with three or more associated Companies are staged in a separate import batch flagged for manual verification. The relationship resolution logic is documented in the migration workbook so the customer can adjust the primary Company assignment post-import if needed.
Sandbox or test-account migration and reconciliation
We run a full migration into a Nutshell test account or Sandbox environment using production-like record volume. The customer's team lead reconciles record counts (People in, Accounts in, Opportunities in, Activities in), spot-checks 20-30 random records against the Aritic source, and reviews the secondary-company field output. Mapping corrections, custom field additions, and pipeline stage name adjustments happen here before production migration begins.
Production migration in dependency order
We run production migration in record-dependency order: Accounts (from Aritic Companies first), People (with primary AccountId resolved and secondary companies captured), Opportunities (with AccountId and OwnerId resolved), Activities (calls, emails, meetings via API with ActivityDate preserved for timeline ordering), Tags/Labels, and custom field data. Each phase emits a row-count reconciliation report. The Owner reconciliation step resolves Aritic Owner emails to Nutshell Users; any unresolved owners go to a queue for manual User provisioning before record import resumes.
Cutover, delta sync, and workflow handoff
We freeze writes to Aritic during cutover, run a final delta migration of any records modified during the migration window, then mark Nutshell as the system of record. We deliver the workflow inventory document to the customer's admin team along with the scoring-rule inventory. We support a three-day hypercare window where we resolve any reconciliation issues. Workflow automation rebuild in Nutshell Automations and Nutshell Automations configuration are outside standard migration scope; these are documented for the customer's admin or a Nutshell implementation partner.
Platform deep dives
Aritic Sales CRM
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 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 Aritic Sales CRM and Nutshell.
Object compatibility
3 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
Aritic Sales CRM: Not publicly documented in available sources.
Data volume sensitivity
Aritic Sales CRM 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 Aritic Sales CRM to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Aritic Sales CRM 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 Aritic Sales CRM
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.