CRM migration

Migrate from Inmovilla to Nutshell

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

Inmovilla logo

Inmovilla

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Inmovilla and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Inmovilla logo

Inmovilla

What's pushing teams away

  • Billing disputes and account blocking — customers report being charged for inactive periods and having accounts suspended over disputed invoices, with support described as unhelpful in resolving billing conflicts.
  • Visual design feels dated — a G2 reviewer noted that the UI has not kept pace with modern standards, and while a global redesign is reportedly in progress, the current interface feels behind the times.
  • Limited flexibility for non-standard workflows — agencies with unusual commission structures or multi-office setups report friction when trying to configure the system outside its default assumptions.
  • Lack of transparent public pricing — no publicly documented pricing tiers makes it difficult to compare cost against alternatives before committing to a sales conversation.

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 Inmovilla objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

Inmovilla 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

maps to

Nutshell

Company

1:1
Fully supported

Inmovilla 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

maps to

Nutshell

Company (as custom-field carrier)

1:1
Fully supported

Inmovilla'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

maps to

Nutshell

Lead

1:1
Fully supported

Inmovilla 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

maps to

Nutshell

Deal

1:1
Fully supported

Inmovilla 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.)

maps to

Nutshell

Pipeline Stage

1:1
Fully supported

Inmovilla'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)

maps to

Nutshell

Task

1:1
Fully supported

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

maps to

Nutshell

Task

1:1
Fully supported

Inmovilla 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

maps to

Nutshell

Note

1:1
Fully supported

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

maps to

Nutshell

Custom Fields on Company

1:1
Fully supported

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

maps to

Nutshell

File attachment on Company / Person / Deal

1:1
Fully supported

Inmovilla 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

maps to

Nutshell

User

1:1
Fully supported

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

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.

Inmovilla logo

Inmovilla gotchas

High

Auto-renewing subscription causes unexpected charges

Medium

Pipeline stage names are agency-configured

High

No publicly documented API

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

  • Property data has no native Nutshell home — every real estate field needs a custom field

    Inmovilla stores property_type, num_bedrooms, surface_area, energy_rating, floor_number, garage_space, and portal_source as structured fields on a Property object. Nutshell has no Property or Listing object — these fields must be pre-created as custom fields on the Nutshell Company record that represents each property listing. If your Inmovilla setup uses more than 10 custom property fields, the custom-field creation and mapping work in Nutshell becomes the longest pre-migration step. FlitStack AI delivers a custom-field creation guide that specifies the field name, type, and pick-list values for every Inmovilla custom property field so your Nutshell admin can pre-create the schema before data lands. Fields not pre-created will be skipped during migration and flagged for post-migration manual entry.

  • Spanish deal stages require manual Nutshell pipeline creation before value-mapping can run

    Inmovilla deal stages follow the Spanish real estate transaction lifecycle: Reserva (reservation deposit), Contrato Reservado (reservation contract signed), En Negociación (negotiation), Pendiente de Escritura (pending deed), and Cerrada (closed). Nutshell pipeline stages are fully customizable but must be created manually in the Nutshell UI before migration begins. The value-mapping between Inmovilla stages and Nutshell stage IDs cannot be configured until the Nutshell pipeline exists. If your Inmovilla account has multiple pipelines (e.g., separate pipelines for Sales, Rentals, and Commercial), each requires its own Nutshell pipeline with corresponding stages. FlitStack AI generates a pipeline-and-stage mapping plan as part of the migration package, but Nutshell-side pipeline creation is a prerequisite step that your team or our team performs in the Nutshell UI.

  • Inmovilla portal syndication and property listing automations do not migrate

    Inmovilla's core differentiator for Spanish real estate agencies is automated publishing to property portals (Idealista, Fotocasa, Habitaclia, Milanuncios, and others). These portal syndication rules — which listings publish to which portals, on what schedule, with which photos and descriptions — are automation logic, not data. Nutshell has no native portal syndication feature and no equivalent API endpoint for publishing listings to third-party property portals. All portal integration workflows must be discontinued or replaced with a third-party syndication tool (such as Syska, Enfoca, or a custom integration). We can export Inmovilla workflow definitions as a reference document for your team to use when rebuilding portal syndication logic in a dedicated tool.

  • N:N contact-to-property relationships collapse to a primary property link

    Inmovilla allows a contact (buyer or tenant) to be associated with multiple Property records simultaneously — a buyer may be evaluating three properties at once. Nutshell's Person record has a single primary Company link and a single primary Deal link. When an Inmovilla contact has N active property associations, we migrate the most recently modified association as the primary link in Nutshell and flag the others for manual review. If retaining the full association history is critical, the secondary associations can be captured as notes on the Person record or as custom fields — but Nutshell does not have a native multi-property contact model.

  • Inmovilla billing disputes and renewal model generate account access risk during migration

    Trustpilot and Capterra reviews document that Inmovilla's automatic-renewal subscription model has caused billing disputes — customers reporting being charged for periods of inactivity and encountering difficulties canceling. This creates a specific migration risk: if Inmovilla suspends account access due to a billing dispute during the migration window, the API export may be interrupted. FlitStack AI recommends resolving any outstanding Inmovilla billing issues before scheduling the migration cutover. We use read-only API access to extract data, but Inmovilla may restrict API access on suspended accounts. We can also perform a manual export via CSV if the API is unavailable, though this requires your team to download the export file from Inmovilla directly.

Migration approach

Six steps for a successful Inmovilla to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

Inmovilla logo

Inmovilla

Source

Strengths

  • Integrated multi-portal syndication to Spanish real estate websites without manual re-entry
  • Comprehensive property management covering the full listing lifecycle from inquiry to close
  • Dedicated mobile app enabling agents to work from any location on any device
  • Commission tracking tied directly to transactions and agent assignments
  • Established user base of over 4,500 Spanish real estate agencies

Weaknesses

  • Billing model uses auto-renewing monthly licenses with disputed enforcement practices
  • UI and visual design reported as outdated with a redesign still in progress
  • No publicly documented pricing or tier structure for pre-purchase evaluation
  • Limited flexibility for non-standard Spanish real estate workflows
  • Support responsiveness criticized in billing dispute scenarios
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. 2 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 Inmovilla and Nutshell.

  • Object compatibility

    B

    2 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

    Inmovilla: Not publicly documented..

  • Data volume sensitivity

    B

    Inmovilla doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Inmovilla 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 Inmovilla to Nutshell data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Inmovilla-to-Nutshell migrations complete in 48–72 hours of clock time for setups under 25,000 records. The pre-migration phase — exporting Inmovilla data, auditing custom property fields, designing Nutshell custom fields, and configuring pipelines — typically adds 3–5 business days and can run in parallel with your team's Nutshell setup work. Complex setups with more than 200,000 records or extensive custom property fields extend to 5–7 days. Nutshell pipeline creation in the UI is a manual prerequisite step that your team controls and can complete before the migration window.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Inmovilla.
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