CRM migration

Migrate from Altcraft to Nutshell

Field-level mapping, validation, and rollback between Altcraft and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Altcraft logo

Altcraft

Source

Nutshell

Destination

Nutshell logo

Compatibility

70%

7 of 10

objects map 1:1 between Altcraft and Nutshell.

Complexity

BStandard

Timeline

2-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Altcraft logo

Altcraft

What's pushing teams away

  • Profile-based pricing scales with database size, creating unpredictable monthly bills as the contact list grows and pushing teams toward flat-rate alternatives.
  • On-premise and private cloud installations require custom integration work per environment, making the total cost of ownership higher than the headline subscription price suggests.
  • Limited public review presence and sparse independent user community make peer validation and competitive comparison difficult before committing.
  • Documentation and developer guides return errors or redirect loops, raising concerns about the platform's long-term maintenance and support responsiveness for enterprise accounts.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Altcraft objects map to Nutshell

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

maps to

Nutshell

Person (Contact)

1:1
Fully supported

Altcraft 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)

maps to

Nutshell

Company

1:1
Fully supported

Altcraft 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)

maps to

Nutshell

Deal

1:1
Fully supported

Altcraft 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

maps to

Nutshell

Note (on Person/Company)

1:many
Fully supported

Altcraft 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)

maps to

Nutshell

Tag + List

1:1
Fully supported

Static 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

maps to

Nutshell

Product

1:1
Fully supported

Altcraft 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)

maps to

Nutshell

Custom Fields on Person

lossy
Fully supported

Altcraft 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

maps to

Nutshell

Custom Fields

lossy
Fully supported

Altcraft 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

maps to

Nutshell

Activity (Note)

1:1
Fully supported

Altcraft 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

maps to

Nutshell

Tag on Person

1:1
Fully supported

Altcraft 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.

Gotchas + challenges

What specifically takes care here

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 logo

Altcraft gotchas

High

Profile-count pricing means database size drives the bill

High

Automation Scenarios do not export as portable logic

Medium

API developer guide returns HTTP 301, blocking programmatic discovery

Medium

Private Cloud and on-premise use separate support contracts

Medium

Control Group assignment is Profile-ID dependent

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Altcraft API documentation returns errors, blocking programmatic discovery

    The official Altcraft developer guide at guides.altcraft.com/en/developer-guide/ returns a 301 redirect and cannot be accessed reliably. This prevents us from programmatically enumerating available endpoints, object schemas, and custom field types before migration. We work around this by exporting Profile data through Altcraft's UI-based CSV export (available in Cloud and Cloud Pro tiers), through Albato connectors where the customer has an active Albato account, or via direct database credentials if the customer provides on-premise or Private Cloud access. API-based migration is only possible when the customer supplies their own endpoint documentation or access tokens. Teams should request a full data export package from Altcraft during discovery to confirm field coverage before migration begins.

  • Automation Scenarios have no export format and do not migrate as logic

    Altcraft Scenarios are configured in a visual builder with conditional branching, loop constructs, API webhook calls, and ML-driven personalization triggers that have no standard export format. We cannot generate a portable automation package for Nutshell or any other destination platform. We export the scenario as a structured description, a list of all referenced Profile IDs, and trigger conditions for each scenario, then deliver a written playbook for the customer's admin to rebuild the logic manually in Nutshell's workflow rules or in a separate marketing automation tool. Teams with complex Scenarios (multi-branch logic, API webhook chains, ML-driven routing) should allocate two to four weeks for manual rebuild scope post-migration.

  • Profile-count billing continues accruing during the export window

    Altcraft bills on the number of customer Profiles stored across all tiers. During migration, both platforms accumulate costs simultaneously: Altcraft continues charging for every Profile in the database while Nutshell is being provisioned and the migration team is extracting data. We advise customers to throttle their export to minimize the double-billing window, and to coordinate with Altcraft's billing team to freeze new Profile creation during the final export pass. Profile records that are archived or suppressed in Altcraft but not deleted from the database still count toward billing; we flag these during scoping.

  • Nutshell lacks native omnichannel and CDP features that Altcraft provides

    Nutshell is a focused sales CRM with no built-in SMS, push notifications, behavioral tracking, or ML-driven personalization. Teams migrating from Altcraft expecting to replicate the full omnichannel stack will need to implement separate tools for email marketing, SMS, and push. We document the channel configuration that existed in Altcraft (sender IDs, approved addresses, API credentials) as a written handoff so that the customer can re-establish those integrations in their chosen marketing automation tool post-migration. Nutshell's basic workflow rules handle task assignment and stage automation but do not replace Altcraft's Scenario builder.

Migration approach

Six steps for a successful Altcraft to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Altcraft logo

Altcraft

Source

Strengths

  • Combines CDP, marketing automation, and omnichannel messaging in a single product rather than requiring three separate integrations.
  • Supports cloud, dedicated private cloud, and on-premise deployment to satisfy data-residency and sovereignty requirements.
  • Profile model unifies behavioral data with CRM and SQL data sources, enabling segment logic that references external relational data.
  • Includes Campaign Master, Control Groups, and ML algorithms in Cloud Pro tier—features typically charged as add-ons by competitors.
  • Built on a modern stack (Golang, ClickHouse, MongoDB) that supports real-time analytics and high-volume profile processing.

Weaknesses

  • API documentation is incomplete, returning errors or redirects, which creates friction for migration planning and third-party integration.
  • Pricing is profile-count based, making the total cost unpredictable and significantly higher than competitors for large contact databases.
  • Headquartered in Russia with a small team (21–45 employees), which may present compliance, support, and continuity risks for EU and US enterprises.
  • Limited public review presence and sparse community content make independent evaluation difficult compared to well-documented Western alternatives.
  • On-premise and private cloud require significant custom configuration, and some features (LDAP SSO, custom channels) are tier-gated, inflating implementation cost.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Altcraft and Nutshell.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    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

    A

    Altcraft exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Altcraft to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Altcraft to Nutshell data migrations

Answers to the questions buyers ask most during Altcraft to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Altcraft to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations land between two and three weeks for accounts under 10,000 Profiles with straightforward field mappings and no complex segment restructuring. Migrations exceeding 10,000 Profiles, requiring multi-segment-to-Tag conversion, deal history reconstruction with activity attachment, or coordination with a Private Cloud or On-premises Altcraft instance move to four to six weeks. The primary time variable is the speed of Altcraft's UI-based CSV export, which is throttled by Altcraft's export job performance rather than our migration tooling.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Altcraft.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day