Migrate from Leadrat CRM for Real Estate to HighLevel

Leadrat leads map directly to HighLevel contacts. All lead properties (name, email, phone, source, status) migrate as contact custom fields where no native equivalent exists. Leads with a status of 'Converted' in Leadrat receive a 'Customer' tag in HighLevel. During import, duplicate detection flags records with identical email addresses for review.

Leadrat contacts migrate as HighLevel contacts with a 1:1 field mapping. The primary company association becomes the Company link in HighLevel. Contacts without a primary company are imported with the company field blank and resolved post-migration. We also map the contact's address, phone, and custom fields to the matching HighLevel contact schema.

Leadrat companies map to HighLevel companies. Company name, website, industry, phone, address fields map directly. Multi-branch companies (parent/child) in Leadrat map using HighLevel's Parent Company field where available, otherwise maintained as separate companies. If a parent/child relationship cannot be represented, we tag the related contacts with a 'Branch' tag for later grouping.

Leadrat deals map to HighLevel opportunities. Deal name becomes the Opportunity name. Deal amount, expected close date, stage, and owner all map to their HighLevel equivalents. The deal's pipeline assignment in Leadrat becomes the HighLevel pipeline name. For deals with multiple stage histories, we preserve the latest stage and close date, ensuring the current pipeline snapshot reflects the most recent status.

Leadrat's pipeline configuration (multiple pipelines with unique stage sets) maps to a single HighLevel pipeline with stage names drawn from the most-primary Leadrat pipeline. Secondary pipelines in Leadrat are surfaced as a 'Original Pipeline' custom field on opportunities for reference.

Leadrat follow-up reminders with a due date map to HighLevel tasks with the same due date and assignee. Task title, description, priority, and completion status all transfer. Open tasks are imported as pending; completed tasks import with their completed timestamp preserved.

Leadrat property records require a new Custom Object in HighLevel named 'Property'. Fields like location, property type, price, square footage, bedrooms, and bathrooms map to custom fields in HighLevel's Custom Object schema. Property-to-contact associations use HighLevel's custom-object relationship feature. We also create a lookup field on the Property object that points back to the primary contact, enabling bidirectional queries across listings and leads.

Leadrat's native portal attribution fields (which portal the lead originated from) have no HighLevel equivalent. We create a 'Portal Source' custom field on the contact record and populate it from Leadrat's source property value, preserving the lead origin attribution for reporting.

Leadrat users are matched to HighLevel users by email address. Active Leadrat users must have a HighLevel user account created before migration; unassigned owners are flagged and mapped to a fallback user or team admin during the migration run. We provide a pre-migration user alignment report that lists each Leadrat owner and the corresponding HighLevel user account status, so you can resolve gaps before data moves.

Leadrat document attachments on leads, contacts, or deals are downloaded and re-uploaded to HighLevel's file storage. For large volumes, attachments are preserved as a URL reference in a custom 'Original Attachment URL' field so the file location is traceable post-migration.