CRM migration
Field-level mapping, validation, and rollback between Sales Creatio and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Sales Creatio
Source
Nutshell
Destination
Compatibility
9 of 11
objects map 1:1 between Sales Creatio and Nutshell.
Complexity
CModerate
Timeline
1-3 weeks
Overview
Moving from Sales Creatio to Nutshell is a size and complexity reduction, not a feature-for-feature swap. Creatio's deep process-automation layer, industry-specific editions, and BPM workflow engine have no direct equivalents in Nutshell's lean, web-first sales CRM. We handle the object-level migration of Contacts, Accounts, Opportunities, Cases, Activities, Orders, and Products with their lookup chains intact. Custom objects and custom fields receive explicit type-level mapping during the discovery pass. Creatio BPM workflows are not portable; we deliver a written inventory documenting every active workflow's trigger, steps, conditions, and actions so your admin can rebuild them in Nutshell's automation tools. We do not migrate Files and Attachments as standard scope; these require a separate extraction and re-link step. Nutshell's transparent per-user pricing starts at $16 per month versus Creatio's $25 per user per month minimum, making the switch attractive for teams that no longer need enterprise workflow depth.
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 Sales 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.
Sales Creatio
Accounts
Nutshell
Company
1:1Creatio Accounts map directly to Nutshell Companies. Address fields, industry classification, type, and ownership transfer as-is. The Company record must exist before any Contact import so that the person-to-company link is satisfied at insert time. We use company name as the dedupe key during import.
Sales Creatio
Contacts
Nutshell
Person
1:1Creatio Contacts map to Nutshell People. Name, email, phone, communication preferences, and owner assignment transfer directly. The link to parent Account maps to the Nutshell person-to-company relationship. Lifecycle stage from Creatio transfers as a custom text field on the Nutshell Person record.
Sales Creatio
Leads
Nutshell
Lead
1:1Creatio Leads map to Nutshell Leads. Lead source, status, rating, and conversion date fields transfer as custom fields on the Nutshell Lead. Unconverted Creatio Leads remain Leads in Nutshell; leads that were partially converted before migration are flagged for manual review.
Sales Creatio
Opportunities
Nutshell
Deal
1:1Creatio Opportunities map to Nutshell Deals. Pipeline stage, amount, probability, and close date transfer. Stage names from Creatio are preserved as-is in Nutshell's Deal stage field; if the stage names differ significantly from Nutshell defaults, we configure custom stage names during the pre-migration setup phase.
Sales Creatio
Activities
Nutshell
Activity
1:1Creatio Activities (tasks, calls, emails, meetings) map to Nutshell Activity records. The activity type enumeration normalizes to Nutshell's activity types (Task, Call, Email, Meeting). Regarding lookups link to the migrated Person, Company, or Deal. Activity timestamps and owner assignments preserve throughout.
Sales Creatio
Cases
Nutshell
Case (via Activities or Custom Field tracking)
lossyCreatio Cases map to Nutshell Cases if the Nutshell plan includes Case management. If Cases are not available on the target plan, we map case records to a combination of Activity notes and a custom Deal field tracking open issues. Priority, status, and resolution notes migrate as custom fields. SLA timers do not transfer as Nutshell lacks a native SLA engine.
Sales Creatio
Orders
Nutshell
Deal with line item notes
lossyCreatio Orders map to Nutshell Deals with line item detail preserved in the Deal description or a linked custom field. The order-to-product lookup resolves by matching Products to Nutshell Products during import. If the customer uses Nutshell Quotes, the order header migrates as a draft Quote rather than a closed Deal.
Sales Creatio
Products
Nutshell
Product
1:1Creatio Products carry pricing, unit type, and tax categories that map to Nutshell Products. Product pricing migrates as Standard Price Book entries. Bundle and pricing rule support depends on Nutshell's quoting capabilities on the target plan.
Sales Creatio
Custom Objects
Nutshell
Not supported in Nutshell
1:1Creatio custom objects have no direct Nutshell equivalent because Nutshell does not support standalone custom object types. We document every custom object schema (field list, types, relationships) and propose a mapping strategy: child records of custom objects may attach to a parent standard record as custom fields, or the customer accepts that the custom object data migrates as a CSV reference table outside Nutshell. This must be resolved during scoping.
Sales Creatio
Custom Fields
Nutshell
Custom Fields (People, Company, Lead)
1:1Creatio custom fields on standard objects map to Nutshell custom fields on the equivalent People, Company, or Lead object. Nutshell supports Text (225 chars), Long Text, Currency, and Date field types. Complex Creatio field types (lookups, multi-select picklists) require transformation to a Nutshell-supported equivalent or a manual post-migration cleanup step.
Sales Creatio
Users and Owners
Nutshell
User
1:1Creatio user records map to Nutshell User accounts by email match. Owner assignments on Contacts, Accounts, Opportunities, and Activities resolve by matching Creatio owner email to Nutshell User email. Orphaned owners (Creatio users with no Nutshell match) are flagged in the reconciliation report for the customer's admin to provision before record import continues.
| Sales Creatio | Nutshell | Compatibility | |
|---|---|---|---|
| Accounts | Company1:1 | Fully supported | |
| Contacts | Person1:1 | Fully supported | |
| Leads | Lead1:1 | Fully supported | |
| Opportunities | Deal1:1 | Mapping required | |
| Activities | Activity1:1 | Mapping required | |
| Cases | Case (via Activities or Custom Field tracking)lossy | Fully supported | |
| Orders | Deal with line item noteslossy | Fully supported | |
| Products | Product1:1 | Fully supported | |
| Custom Objects | Not supported in Nutshell1:1 | Mapping required | |
| Custom Fields | Custom Fields (People, Company, Lead)1:1 | Mapping required | |
| Users and Owners | User1:1 | Mapping required |
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.
Sales Creatio gotchas
Live update socket storm during bulk data import
BPM workflows are not exportable or portable
Cloud vs on-site file storage affects migration path
Classic UI dashboards require separate migrator tool
Soft caps on server resources can trigger post-migration upsell
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 data audit
We audit the source Creatio instance across edition (Growth, Enterprise, Unlimited), custom objects, custom fields, active BPM workflows, activity volume by type, file storage location (database vs S3/Azure Blob), and user count. We pair this with a Nutshell edition recommendation based on the customer's team size and required features. The discovery output is a written migration scope, object inventory, and a list of items requiring admin decision (custom object handling, workflow rebuild priority, file extraction approach).
Schema design and pre-migration Nutshell setup
We configure Nutshell before any data moves. This includes creating custom fields on People, Companies, and Leads to match Creatio custom fields, configuring Deal stages to match the Creatio pipeline stage names, setting up any required nuttShell automation rules, and provisioning User accounts for every Creatio owner referenced on migrating records. Nutshell setup happens in a trial or development environment first for validation.
Owner reconciliation and User provisioning
We extract every distinct Creatio user referenced as an owner on Contacts, Accounts, Opportunities, and Activities and match by email against the Nutshell User table. Any Creatio owner without a matching Nutshell User enters a reconciliation queue for the customer to provision before record migration resumes. OwnerId references are required on most standard object imports, so this step gates the rest of the migration.
Production migration in dependency order
We run production migration in record-dependency order: Companies (from Creatio Accounts), People (from Creatio Contacts with CompanyId resolved), Leads (from Creatio Leads), Deals (from Creatio Opportunities with CompanyId and OwnerId resolved), Activities by type (tasks, calls, emails, meetings in separate batches), Cases, Orders, Products. Custom objects migrate last and use a documented fallback strategy if Nutshell's schema cannot represent the relationship directly. Each phase emits a row-count reconciliation report before the next phase begins.
BPM workflow inventory delivery and automation handoff
We export every active Creatio BPM workflow as a written reference document. The document captures the workflow name, trigger type, step sequence, decision conditions, action types, and any lookup or field references. This is not a migration of workflow logic; it is a specification document for your admin to use when rebuilding equivalent automation in Nutshell's rules-based automation layer. We deliver the document at the same time as the migration sign-off.
Cutover, validation, and post-migration support
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 against the Creatio source, and deliver the migration reconciliation report. We offer a three-day hypercare window for reconciliation issues. We do not rebuild BPM workflows or configure Nutshell automation rules as standard scope; these are separate engagements or internal admin tasks.
Platform deep dives
Sales Creatio
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 4 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Sales Creatio and Nutshell.
Object compatibility
4 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
Sales Creatio: Not publicly documented; service-level limits apply per DataService session.
Data volume sensitivity
Sales Creatio 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 Sales Creatio to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Sales 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 Sales 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.