Migrate from Property Minder to Zoho CRM

Property Minder real estate fields require custom field creation in Zoho CRM

Property Minder stores property_type, mls_number, listing_price, and listing_status as native fields on its property-listing object. Zoho CRM has no built-in real estate module — none of these fields exist by default. Custom fields must be created on the Account or Deal module before migration data is loaded. Pick-list fields like property_type and listing_status need their values defined in Zoho first; importing data into a pick-list field before the pick-list values exist causes import errors. We create a custom field setup plan during the schema phase that names each field, its data type, and which Zoho module it belongs to, so your Zoho admin can pre-create the fields before we load a single record.

Zoho Bulk Read API caps exports at 200,000 records per job

If Property Minder holds more than 200,000 total records across contacts, accounts, deals, and activities, Zoho's bulk read API — which FlitStack uses to extract destination-side validation data during the migration — will return a truncated result set and report a pagination token. The API response will include a more_records=true flag and a next_page_token that we use to queue a second export job. This is not a data loss condition but it adds a step to the extraction phase. For migrations approaching this threshold, we pre-scope the export in multiple jobs by object type so the migration plan accounts for the additional API round-trips and the timeline extends accordingly.

Attachment re-upload to Zoho Files enforces a 25MB per-file limit

Property Minder property listings often carry multiple high-resolution photos, MLS PDFs, and listing documents. Zoho CRM's Files module enforces a 25MB ceiling per individual file during re-upload. Files that exceed this limit fail silently in some import paths and throw a validation error in others. During the pre-migration audit, we identify all files exceeding 25MB and flag them for client decision: compress images to a standard resolution, split multi-page PDFs, or drop oversized files from the migration set. We do not skip these files without explicit instruction — they represent property listing context that matters for deal history.

IDX search automations and MLS follow-up sequences do not transfer to Zoho Blueprint

Property Minder's IDX search automations trigger client notifications when new MLS listings match saved criteria — a core workflow for buyer-agent teams. Zoho CRM has no native equivalent to MLS feed integration or IDX-triggered automations. More broadly, any Property Minder workflow rule, sequence, or follow-up trigger has no Blueprint-compatible export format. When we run the migration, these automations are documented in an export file that lists every active rule with its trigger conditions and actions, but the rules themselves must be rebuilt from scratch in Zoho Blueprint or reconstructed as Deluge scripts. We deliver the reference document during the approach phase so your Zoho admin can begin the rebuild before migration day.

Property Minder deal stages do not map 1:1 to Zoho CRM Deal Stages

Property Minder uses a simplified stage model: Active, Under Contract, Pending, and Closed. Zoho CRM Deal stages follow a configurable pipeline model — the default installation includes New Lead, Qualification, Needs Analysis, Proposal/Price Quote, Negotiation Review, Closed Won, and Closed Lost, and each stage has an associated probability and forecast category. When migrating deal data, we map each Property Minder stage to the most semantically close Zoho stage value and re-apply probability and forecast-category values during the import. Teams that have customized Property Minder stage names — or added custom stages — need a value-mapping table built during the schema phase so the mapping is explicit before any data loads.