CRM migration
Field-level mapping, validation, and rollback between Creatio and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Creatio
Source
Nutshell
Destination
Compatibility
8 of 10
objects map 1:1 between Creatio and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Moving from Creatio to Nutshell is a platform-size migration: Creatio targets mid-market and enterprise teams with a composable low-code platform and integrated Sales, Marketing, and Service modules, while Nutshell targets small to mid-market teams that need straightforward CRM functionality without the overhead of BPM tooling and schema design. The core structural difference is that Creatio uses a schema-centric entity model with configurable pipelines and external file storage, while Nutshell uses a simpler People, Companies, Leads, and Deals model with a native Activity timeline. We resolve this by extracting Creatio's entity schemas from the package archive, mapping Account and Contact records to Nutshell's Company and Person objects, and preserving historical timestamps across the Activity timeline. Calculated fields and multicurrency fields require explicit type-aware handling because Nutshell has no native equivalent for either. Workflows, BPM automations, and Creatio's process-centric tools do not migrate; we deliver a written inventory of these for the customer's admin to evaluate against Nutshell's automation capabilities.
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 Creatio 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.
Creatio
Account
Nutshell
Company
1:1Creatio Account records map to Nutshell Company records. The Account Name becomes the Company name, and address fields map to the standard Nutshell address block. Industry, phone, website, and custom fields transfer as custom Company fields in Nutshell. We use the Company name as the dedupe key during import. Accounts with no name are flagged for manual review before writeback.
Creatio
Contact
Nutshell
Person
1:1Creatio Contact records map to Nutshell Person records. The Contact Name splits into first_name and last_name; email, phone, and mobile map directly. Lifecycle stage and owner assignment transfer as custom Person fields. We resolve the parent Account to a Nutshell Company via the lookup relationship before inserting each Person, so the Person-Company link is satisfied at writeback rather than patched afterward.
Creatio
Lead
Nutshell
Lead
1:1Creatio Lead records map to Nutshell Lead records. Lead status and source fields migrate as custom fields on Nutshell's Lead object. If the customer's Nutshell plan includes the Leads feature, we map Leads directly. If the customer has disabled Leads in favor of adding Contacts directly, we migrate Leads as Persons with a custom field lead_source__c to preserve the source attribution.
Creatio
Opportunity
Nutshell
Deal
1:1Creatio Opportunity records map to Nutshell Deal records. The opportunity name, amount, stage, probability, close date, and owner migrate directly. Creatio's configurable pipeline stages map to Nutshell's Deal stage values, and we capture the active pipeline schema during discovery to ensure stage names match the destination. If the customer uses multiple pipelines in Creatio, we create Nutshell custom fields for pipeline attribution rather than using separate Deal record types.
Creatio
Case
Nutshell
Lead or Person custom field
lossyCreatio Case records have no direct Nutshell equivalent because Nutshell is a sales CRM without native service case management. We discuss the customer's priority during scoping: Cases can migrate as Nutshell Leads (if the customer uses Leads for post-sale service tracking), or as custom fields on the related Person record with case status and priority preserved. The preferred approach depends on whether the customer plans to use a separate helpdesk platform post-migration.
Creatio
Activity (Call, Email, Task)
Nutshell
Activity
1:1Creatio Activity records of type Call, Email, and Task map to Nutshell Activity records with type differentiation. We separate by Creatio ActivityType at writeback. Activity timestamps (CreatedOn and ModifiedOn) preserve as the Nutshell Activity date. The related Contact or Account resolves to the corresponding Nutshell Person or Company at migration time via the lookup map built during discovery.
Creatio
Product
Nutshell
Product
1:1Creatio Products map to Nutshell Product records with SKU, name, price, and unit of measure. Multi-currency pricing in Creatio requires currency conversion or a base-currency writeback decision during scoping. Nutshell Products do not support multi-currency pricing natively, so the customer chooses whether to write back the base currency value or the converted value.
Creatio
Custom Object
Nutshell
Custom Fields on standard objects
lossyCreatio custom objects do not have a direct Nutshell equivalent because Nutshell does not support custom object creation. During scoping we audit each custom object's column count, relationship type (lookup to base entity or standalone), and usage frequency. Standalone custom objects with few fields map to custom fields on the nearest standard object. Custom objects with complex lookup chains or high field counts are flagged as requiring a different destination platform or a post-migration data dictionary for manual reference.
Creatio
File and Attachment
Nutshell
Attachment on Person, Company, or Deal
1:1Creatio file attachments migrate to Nutshell as native attachments on the related record (Person, Company, or Deal). The key complexity is storage mode detection: Creatio v8.3.2+ supports dual storage (in-database or external S3/Azure Blob). We detect the UseEntityFileApi flag during discovery and route file extraction accordingly. Files stored externally require download from the configured S3 or Azure Blob bucket before writing to Nutshell. Attachments exceeding Nutshell's size limit are flagged for compression or host-link substitution.
Creatio
User and Owner
Nutshell
User
1:1Creatio Users map to Nutshell Users by email match. We extract every distinct owner referenced on Account, Contact, Opportunity, and Activity records during the owner audit phase. Owners without a matching Nutshell User go to a reconciliation queue, and the customer's admin provisions missing Users before record import resumes. Inactive Creatio users map to inactive Nutshell users if historical attribution must be preserved.
| Creatio | Nutshell | Compatibility | |
|---|---|---|---|
| Account | Company1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| Case | Lead or Person custom fieldlossy | Fully supported | |
| Activity (Call, Email, Task) | Activity1:1 | Fully supported | |
| Product | Product1:1 | Fully supported | |
| Custom Object | Custom Fields on standard objectslossy | Fully supported | |
| File and Attachment | Attachment on Person, Company, or Deal1:1 | Fully supported | |
| User and 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.
Creatio gotchas
Creatio schema packages require explicit export before migration
File storage mode affects attachment extraction
Calculated fields and multicurrency fields need type-aware writeback
Per-plan licensing gates certain features relevant to migration
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 schema audit
We audit the source Creatio environment across plan tier (Business, Scale, or Standard), package exports (standard and custom), entity schemas, pipeline definitions, file storage mode (in-database or S3/Azure Blob), and record volumes by object. We pair this with a Nutshell plan review and audit of existing Nutshell custom fields. The discovery output is a written migration scope with object-level mapping, a calculated-field and multicurrency-field flag list, a file storage routing decision, and a pipeline-to-Deal-stage mapping table.
Package schema extraction and column mapping
We extract Creatio package archives from the Configuration section and parse each entity schema to build the complete column map. We identify custom object definitions, custom fields on base entities, lookup relationships, and any schema dependencies between packages. The column map is validated against the Nutshell custom field audit to flag fields that cannot migrate as-is and require a type conversion or custom field workaround.
Owner reconciliation and user provisioning
We extract every distinct Creatio User referenced as an owner on Account, Contact, Opportunity, and Activity records. We match each by email against the Nutshell destination's User table. Owners without a matching Nutshell User go to a reconciliation queue, and the customer's admin provisions any missing users before record import resumes. Inactive Creatio users are mapped to inactive Nutshell users if historical attribution must be preserved on completed Activities.
File storage extraction
We detect the file storage mode during discovery. For in-database storage, we extract files via Creatio's standard export. For external S3 or Azure Blob storage, we use the bucket credentials to download files to a staging environment before writing to Nutshell. Attachments are matched to their parent record via the Creatio file lookup before writeback. Files exceeding Nutshell's size limit are flagged for host-link substitution or compression.
Production migration in dependency order
We run production migration in record-dependency order: Companies (from Creatio Accounts), Persons (from Creatio Contacts with CompanyId resolved), Leads, Deals (from Creatio Opportunities with OwnerId resolved and stage mapped), Products, Activities (Tasks, Calls, Emails via Nutshell API with ActivityDate preserved from Creatio CreatedOn), and custom fields last. Each phase emits a row-count reconciliation report before the next phase begins. Calculated fields are skipped; multicurrency fields are written as the base currency value or converted value per the scoping decision.
Cutover, validation, and workflow handoff
We freeze Creatio writes during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We validate record counts, spot-check 20-30 records per object against the Creatio source, and deliver the workflow inventory document to the customer's admin team. We support a one-week hypercare window where we resolve reconciliation issues. We do not rebuild Creatio BPM workflows as Nutshell automation rules inside the migration scope; that work is a separate assessment or an internal admin task.
Platform deep dives
Creatio
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 Creatio 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
Creatio: Not publicly documented as a request-per-second cap. Per-response limits exist: OData responses are capped at 20,000 lines and OData batch requests may include up to 100 sub-requests..
Data volume sensitivity
Creatio 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 Creatio to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Creatio 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 Creatio
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.