Migrate from Inmovilla to Pipedrive

Inmovilla contacts map directly to Pipedrive Persons. Name, email, phone, address, and owner assignments transfer as-is. Multiple contacts per property in Inmovilla create multiple Person records in Pipedrive. Custom field values attached to contacts also migrate to corresponding Pipedrive Person custom fields using field-type mapping for text, numeric, date, and enum field types.

Inmovilla agency and company records map to Pipedrive Organizations. Agency name, address, website, and industry fields transfer. Inmovilla parent-child agency hierarchies map to Pipedrive Organization hierarchy via parent_id. Additional company metadata such as tax identification numbers stored in custom fields migrates to Pipedrive Organization custom fields with appropriate type mapping.

Inmovilla property records have no direct Pipedrive equivalent. We map property data to Pipedrive Deals with custom fields: property_type, listing_status, price, surface_area, bedrooms, bathrooms, portal_sync_status, virtual_tour_url. Each property becomes one Deal. Property-contact associations become Activity links between the Deal and associated Person records, preserving the relationship context without duplicating data.

Inmovilla leads without a converted property map to Pipedrive Leads. Lead source, status, and assigned owner transfer. Leads with an associated property become Deals with the lead status preserved in a custom field. The original lead creation date migrates to the Deal add_time field, maintaining historical accuracy for pipeline velocity calculations.

Inmovilla deal stages such as Reservado, Vendido, and Disponible map value-by-value to Pipedrive deal stages. We create a Pipedrive pipeline matching Inmovilla's stage sequence and apply stage-probability mapping per your specified values. Custom stage colors and names from Inmovilla transfer to maintain visual consistency in your Pipedrive pipeline view.

Inmovilla calls, emails, and meetings map to Pipedrive Activities with original timestamps, owner assignments, and linked Person or Deal references preserved. Activity type such as call, email, meeting, or task maps directly. The original activity subject and notes content transfer intact, maintaining complete interaction history for each contact and property deal.

Inmovilla notes attach to contacts, properties, or deals. We map notes to Pipedrive Activities with type=note, preserving the original content, creation date, and linked record association. Note formatting such as bold or italic text may simplify during transfer depending on Pipedrive's note field support for rich text.

Inmovilla property documents such as contracts, floor plans, and contact attachments download and re-upload to Pipedrive as Activity attachments on the linked Person or Deal. File size limits per Pipedrive plan apply. We validate total attachment volume against your plan storage quota before initiating the document transfer phase.

Every Inmovilla custom property field requires a corresponding Pipedrive custom field. Field type mapping follows these rules: text to string, number to numeric, date to date, and picklist to enum. Pipedrive API assigns hash keys to custom fields rather than using display names. We map values before bulk load to ensure each Inmovilla attribute populates the correct Pipedrive field.

Inmovilla users resolve to Pipedrive users by email match. Unmatched users are flagged before migration. Records for unmatched owners assign to a fallback Pipedrive user specified in the migration plan. Pre-flight validation ensures every Inmovilla owner has a corresponding Pipedrive user ID before records load.

Inmovilla portal sync configurations such as idealista, fotocasa, and habitaclia are Inmovilla-specific integrations with no Pipedrive equivalent. The sync settings must be rebuilt using Zapier, Make, or Pipedrive's workflow automations after migration. We export your portal sync configuration as a reference document for your Pipedrive admin to use during reconstruction.

Inmovilla workflows including listing triggers, email automations, and portal update rules do not migrate. We export workflow definitions as a structured reference document listing each automation's trigger conditions and actions. Your Pipedrive admin uses this document to rebuild equivalent automations using Pipedrive's Automation builder or Sequences post-migration.