CRM migration
Field-level mapping, validation, and rollback between Inmovilla and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Inmovilla
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Inmovilla and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Inmovilla is a Spanish real-estate CRM focused on property management, portal syndication, and real estate transaction workflows across more than 4,500 agencies in Spain. Its data model centers on Properties (listings), Contacts (clients), Companies (agencies and landlords), Deals (transactions), and activity history tied to property viewings and offers. Nutshell is an SMB sales CRM built for small-to-mid-market teams that need straightforward pipeline management, contact organization, and sales automation with integrated engagement tools — it has no native real-estate object model. FlitStack AI migrates all standard Inmovilla objects (people, companies, deals, tasks, notes) into Nutshell's Person, Company, and Deal structures. Property-specific fields — property type, number of bedrooms, listing status, price per meter — have no direct Nutshell equivalent and migrate as custom fields on Nutshell Company or Person records. Inmovilla's deal stages (Reserva, En Negociación, Cerrada) map to Nutshell pipeline stages via value-by-value mapping. Engagement history (property viewings, calls, email threads) migrates as Nutshell Tasks. The migration uses Inmovilla's API export and bulk-import into Nutshell via the Nutshell JSON-RPC API, with a 24–48 hour delta-pickup window at cutover. Workflows, automations, portal integrations, and email templates do not migrate — they must be rebuilt in Nutshell or discontinued.
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 Inmovilla 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.
Inmovilla
Person / Contact
Nutshell
Person
1:1Inmovilla contacts (buyer and seller clients) map directly to Nutshell Persons. Name, email, phone, address, and job title transfer directly. Owners are resolved by email match against Nutshell users. Contacts without an email receive a generated placeholder address to preserve the record.
Inmovilla
Company / Agency
Nutshell
Company
1:1Inmovilla company records (agencies, landlords, developers) map to Nutshell Companies. Company name, website, address, and industry classification transfer directly. Parent-child company hierarchies in Inmovilla map to Nutshell's parent_company association, preserving organizational structure across both platforms. Each company record maintains its complete relationship tree in the target system.
Inmovilla
Property / Listing
Nutshell
Company (as custom-field carrier)
1:1Inmovilla's Property object has no Nutshell equivalent. We map each Property to a Nutshell Company record, storing property_type, num_bedrooms, surface_area, listing_status, and price as Nutshell custom fields on the Company. The Property's address becomes the Company's address. This approach preserves all property-specific data while making it searchable within Nutshell's standard Company framework.
Inmovilla
Lead
Nutshell
Lead
1:1Inmovilla Leads (prospective buyers not yet attached to a property) map to Nutshell Leads. Lead name, email, phone, source, and status transfer directly. Inmovilla lead status values map to Nutshell lead status via value mapping. This ensures continuity of the lead pipeline and preserves historical lead scoring data from the source system.
Inmovilla
Deal / Transaction
Nutshell
Deal
1:1Inmovilla deals (property transactions) map to Nutshell Deals linked to the Person (buyer/seller) and the Property-Company record. Deal name, amount, close date, and owner transfer directly. The Inmovilla deal is linked to both the Person and the Property-Company in Nutshell.
Inmovilla
Deal Stage (Reserva, Contrato Reservado, etc.)
Nutshell
Pipeline Stage
1:1Inmovilla's Spanish real estate deal stages map to Nutshell pipeline stage values via value-by-value mapping. Reserva maps to an early pipeline stage (e.g., Appointment Scheduled). Contrato Reservado maps to Under Contract. En Negociación maps to Proposal. Cerrada maps to Closed Won. Closed Lost maps from Inmovilla records marked as withdrawn.
Inmovilla
Task / Activity (Property Viewing)
Nutshell
Task
1:1Inmovilla property viewing logs migrate as Nutshell Tasks with Type='Meeting' and the property address in the task description. Original timestamps, owner assignments, and linked Person and Property records are preserved. A Nutshell Deal is linked if the viewing is tied to an active transaction.
Inmovilla
Task / Activity (Call, Email)
Nutshell
Task
1:1Inmovilla call and email engagement records migrate as Nutshell Tasks with Type='Call' or Type='Email' respectively. Subject line, description, timestamp, and owner transfer directly. Activities without a subject receive a generated one based on activity type and date. All engagement history is preserved and linked to the corresponding Person record for complete activity tracking.
Inmovilla
Note
Nutshell
Note
1:1Inmovilla notes migrate to Nutshell Notes attached to the relevant Person, Company, or Deal record. Rich-text formatting is preserved where Nutshell's note format supports it. Notes without a parent record attach to the most recently related Person record. This ensures all historical context transfers even when note associations are ambiguous.
Inmovilla
Custom Property Fields (real estate specific)
Nutshell
Custom Fields on Company
1:1Inmovilla custom fields on Properties (energy_rating, orientation, floor_number, garage_space, community_fees, listing_portal_source) have no Nutshell equivalent. Each custom field requires a corresponding Nutshell custom field to be created on the Company object before migration. We deliver a custom-field creation guide as part of the migration plan.
Inmovilla
Attachment / File (property photos, contracts)
Nutshell
File attachment on Company / Person / Deal
1:1Inmovilla file attachments (property photos, scanned contracts, PDF reports) are re-uploaded to Nutshell as file attachments on the mapped Company or Deal record. Nutshell's 25MB per-file limit applies; larger files are flagged for manual handling. All file metadata including original upload dates and descriptions transfer with each attachment.
Inmovilla
User / Owner
Nutshell
User
1:1Inmovilla owner IDs are resolved against Nutshell users by email address match. Unmatched owners are flagged before migration — the team either creates Nutshell user accounts for them or assigns their records to a fallback owner. No record lands in Nutshell without an owner.
| Inmovilla | Nutshell | Compatibility | |
|---|---|---|---|
| Person / Contact | Person1:1 | Fully supported | |
| Company / Agency | Company1:1 | Fully supported | |
| Property / Listing | Company (as custom-field carrier)1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Deal / Transaction | Deal1:1 | Fully supported | |
| Deal Stage (Reserva, Contrato Reservado, etc.) | Pipeline Stage1:1 | Fully supported | |
| Task / Activity (Property Viewing) | Task1:1 | Fully supported | |
| Task / Activity (Call, Email) | Task1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Custom Property Fields (real estate specific) | Custom Fields on Company1:1 | Fully supported | |
| Attachment / File (property photos, contracts) | File attachment on Company / Person / Deal1:1 | Fully supported | |
| User / 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.
Inmovilla gotchas
Auto-renewing subscription causes unexpected charges
Pipeline stage names are agency-configured
No publicly documented API
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
Export and audit Inmovilla data
FlitStack AI connects to Inmovilla via API using your X-Token credentials and exports all people, companies, properties, deals, leads, tasks, notes, and file attachments. We run a data audit that identifies duplicate records, missing required fields (especially contacts without email addresses), and the full inventory of custom property fields. The audit produces a data quality report that flags records requiring pre-migration cleanup — particularly duplicate contacts and properties with conflicting stage values — so your team can decide how to handle them before the migration plan is finalized.
Design Nutshell custom fields and pipelines
Based on the Inmovilla data audit, FlitStack AI generates a Nutshell setup guide that specifies every custom field to create (name, type, pick-list values) and every pipeline stage to configure in Nutshell. This includes mapping Inmovilla's Spanish deal stages to Nutshell stage names, defining the property-related custom fields on the Company object, and setting up the Nutshell lead status pick-list. Your Nutshell admin creates the fields and pipelines in the Nutshell UI. We verify the setup before proceeding — if a required custom field is missing, migration will skip those records and flag them for manual handling.
Resolve owners and create user mapping
Inmovilla owner IDs are matched against Nutshell users by email address. We generate a pre-migration owner report that shows every Inmovilla owner, their email, and whether a corresponding Nutshell user account exists. Owners without a Nutshell account are flagged — your team creates the Nutshell user before migration or designates a fallback owner for their records. No Person, Company, Deal, or Lead record is written to Nutshell without a valid owner ID. This step also identifies any contacts in Inmovilla that lack an email address, which receive a generated placeholder address to preserve the record.
Run sample migration with field-level diff
A representative slice migrates first — typically 100–500 records spanning contacts, companies, properties (as Companies with custom fields), deals, and a sample of tasks. We generate a field-level diff between the Inmovilla source values and the Nutshell destination values so you can verify that property_type mapped to Property_Type__c, deal stages mapped via value mapping, owner resolution worked correctly, and file attachments uploaded to the right records. You review the sample in Nutshell and approve before the full migration commits. Any mapping adjustments are made before the full run.
Execute full migration with delta-pickup cutover
The full migration runs against Nutshell via the JSON-RPC API. A delta-pickup window (typically 24–48 hours) captures any records created or modified in Inmovilla during the cutover window — important for agencies where deals advance or new leads enter during the migration window. Audit logs capture every operation including skipped records, owner resolution failures, and missing custom field values. One-click rollback is available if reconciliation fails. After rollback verification, the Inmovilla account can be suspended or downgraded. FlitStack AI delivers a post-migration reconciliation report comparing record counts per object between Inmovilla and Nutshell.
Platform deep dives
Inmovilla
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 Inmovilla and Nutshell.
Object compatibility
2 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
Inmovilla: Not publicly documented..
Data volume sensitivity
Inmovilla 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 Inmovilla to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Inmovilla 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 Inmovilla
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.