CRM migration
Field-level mapping, validation, and rollback between Altcraft and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Altcraft
Source
Nutshell
Destination
Compatibility
7 of 10
objects map 1:1 between Altcraft and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Moving from Altcraft to Nutshell is a structural data model shift, not a direct record copy. Altcraft's CDP uses customer Profiles that merge behavioral data, channel subscriptions, and device context into a unified 360-degree view; Nutshell uses standard CRM objects (People, Companies, Deals, Activities) with no native marketing automation layer. We extract Altcraft Profiles via CSV export using Albato connectors or direct database access where the customer provides credentials, restructure the data into Nutshell's People and Companies schema, preserve deal history in Nutshell Deals, and attach campaign performance data as Notes on the relevant Contact record. Automation Scenarios, omnichannel messaging templates, and Control Group assignments do not migrate as portable logic; we deliver a written inventory of these for the customer's admin to rebuild in Nutshell's workflow builder or a separate marketing automation tool. Altcraft's per-profile billing model means teams can reduce costs immediately upon migration if Nutshell's per-user model fits the team size better.
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 Altcraft 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.
Altcraft
Customer Profile
Nutshell
Person (Contact)
1:1Altcraft Profiles are the central record containing behavioral data, channel subscriptions, device metadata, and all custom fields. We export via CSV through Albato or UI-based export, then map each Profile to a Nutshell Person. The HubSpot-style Profile ID is preserved in a custom field for audit. Channel subscription preferences (email, SMS, push) map to the Nutshell Person's email and phone fields with subscription status tracked in a custom field.
Altcraft
Company (within Profile)
Nutshell
Company
1:1Altcraft embeds company data within the Profile record. We extract the company name, domain, industry, address, and employee count into a separate Company record in Nutshell before importing the Person, so that the Person.Company lookup resolves at import time. The company domain becomes the Company website field.
Altcraft
Deal (Opportunity)
Nutshell
Deal
1:1Altcraft Deals linked to Profiles migrate to Nutshell Deals with the Person and Company lookups resolved. Deal stage names from Altcraft's pipeline map to Nutshell's stage values. If Altcraft has multiple deal pipelines, we use Nutshell's Loss Reasons and Tags to preserve pipeline context because Nutshell does not have native multi-pipeline support.
Altcraft
Campaign
Nutshell
Note (on Person/Company)
1:manyAltcraft Campaigns with send history, open and click analytics, and channel assignment do not have a native Nutshell equivalent. We attach campaign metadata as a Note on the relevant Person record, tagging the Note with the campaign name and date so that sales reps can see outreach history without opening a separate marketing tool.
Altcraft
Segment (Static)
Nutshell
Tag + List
1:1Static segments are straightforward list transfers. We assign all Profiles in a static segment a corresponding Tag in Nutshell, and optionally create a Nutshell List with the segment name for list-based campaign targeting. Dynamic segments are documented with their criteria logic for manual rebuild in Nutshell.
Altcraft
Product
Nutshell
Product
1:1Altcraft Products migrate to Nutshell Products with SKU, name, description, and pricing. Nutshell Products are used in Deal line items, so we create the Product records before Deal import so that the lookup is satisfied.
Altcraft
Order (linked to Profile)
Nutshell
Custom Fields on Person
lossyAltcraft Order history is linked to the Profile at migration time. If the order volume is small (under 1,000 records), we embed order summaries as custom fields on the Nutshell Person record (last order date, total orders, total revenue). For high-volume order history, we document the order table schema for export to a separate data warehouse or BI tool.
Altcraft
Custom Profile Fields
Nutshell
Custom Fields
lossyAltcraft user-defined custom fields on the Profile object export as structured columns in the profile CSV. We map each field to a Nutshell custom field of equivalent type (text, number, date, dropdown). Boolean and multi-select fields from Altcraft map to Nutshell checkboxes and multi-select picklists respectively. The API name in Altcraft is preserved in the Nutshell custom field description for audit.
Altcraft
Engagement: Email
Nutshell
Activity (Note)
1:1Altcraft email engagement records (send, open, click, reply) attach to the Profile as behavioral history. We migrate the most recent 90 days of email engagement as Activities in Nutshell linked to the Person record, with the engagement type and timestamp preserved. Older engagement history is documented in a CSV export for reference.
Altcraft
Control Group
Nutshell
Tag on Person
1:1Altcraft Control Group assignments are tied to Profile IDs. We export the Control Group membership as an explicit attribute and reapply it as a Tag on the Nutshell Person record (e.g., 'Control Group A') after the Person ID is established. The customer should configure comparative campaign reporting in their marketing analytics tool post-migration.
| Altcraft | Nutshell | Compatibility | |
|---|---|---|---|
| Customer Profile | Person (Contact)1:1 | Fully supported | |
| Company (within Profile) | Company1:1 | Fully supported | |
| Deal (Opportunity) | Deal1:1 | Fully supported | |
| Campaign | Note (on Person/Company)1:many | Fully supported | |
| Segment (Static) | Tag + List1:1 | Fully supported | |
| Product | Product1:1 | Fully supported | |
| Order (linked to Profile) | Custom Fields on Personlossy | Fully supported | |
| Custom Profile Fields | Custom Fieldslossy | Fully supported | |
| Engagement: Email | Activity (Note)1:1 | Fully supported | |
| Control Group | Tag on Person1: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.
Altcraft gotchas
Profile-count pricing means database size drives the bill
Automation Scenarios do not export as portable logic
API developer guide returns HTTP 301, blocking programmatic discovery
Private Cloud and on-premise use separate support contracts
Control Group assignment is Profile-ID dependent
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 Altcraft export package review
We audit the source Altcraft account across tier (Cloud, Cloud Pro, Private Cloud, On-premises), Profile volume, custom field definitions, active Segments, existing Deals, and Products. We request the UI-based CSV export package from Altcraft and review it for field coverage and completeness. For Private Cloud and On-premises deployments, we coordinate with the customer's technical team to obtain database credentials or API access tokens. We pair this with a Nutshell account audit to confirm the existing data model, user count, and any active integrations that might affect import sequencing.
Schema design and field mapping specification
We design the destination schema in Nutshell. This includes creating all required custom fields on Person, Company, and Deal objects to receive Altcraft data that does not map to standard Nutshell fields (behavioral attributes, channel subscription status, original Profile ID). We map Altcraft's multi-segment structure to Nutshell Tags and optionally Lists. If Altcraft has multiple deal pipelines, we define the Tag strategy and Loss Reason structure in Nutshell before migration. The mapping specification is reviewed and approved by the customer's admin before any data moves.
Company and Product import
We import Nutshell Companies first because Person records reference Company lookups. Altcraft company data embedded within Profiles is extracted into a denormalized Company import file. Products from Altcraft are imported next so that Deals referencing products have a valid Product lookup. Each phase emits a row-count reconciliation report before the next phase begins.
Person (Profile) import with Company resolution
We import Nutshell People using the Altcraft Profile CSV. The Company lookup resolves by matching the Altcraft company name and domain against the Company records imported in the previous step. Unmatched companies are created as a catch-all Company record or held in a reconciliation queue for the admin to resolve. Tags from Altcraft are applied during import using Nutshell's bulk tag assignment. We flag any Profiles that lack an email address (required in Nutshell) and hold them for manual resolution.
Deal import with stage and loss-reason mapping
Altcraft Deals are imported as Nutshell Deals with Person and Company lookups resolved. Stage values map per the approved stage matrix. Loss reasons from Altcraft become Nutshell Loss Reasons. If Altcraft had multiple deal pipelines, the pipeline name is applied as a Tag on each Deal. Activity history for Deals (if any exists in Altcraft) is attached as Notes on the Deal record.
Cutover, validation, and workflow handoff
We freeze writes to Altcraft during cutover, run a final delta migration of any Profiles or Deals modified during the migration window, then mark Nutshell as the system of record. We deliver the Scenario inventory and channel configuration document to the customer's admin team for rebuild in Nutshell workflows or a separate marketing automation platform. We support a 72-hour hypercare window to resolve any record mismatches or import errors raised during initial Nutshell usage. We do not rebuild Altcraft Scenarios as Nutshell workflows inside the migration scope; that work is handled by the customer's admin or a separate implementation engagement.
Platform deep dives
Altcraft
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 Altcraft 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
Altcraft: Configurable via API_MAX_REQUESTS_COUNT — exceeding returns HTTP 429. Specific numeric limits are not published in the developer guide and must be confirmed per deployment..
Data volume sensitivity
Altcraft exposes a bulk API — large-volume migrations stream efficiently.
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 Altcraft to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Altcraft 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 Altcraft
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.