Migrate from AscendixRE to HighLevel

Direct 1:1 mapping. HighLevel's Company object holds business name, domain, address, phone, and custom fields. Primary address and shipping address fields map field-by-field. HighLevel Company does not have a native OwnerId field — owner assignment is handled separately via Contact ownership.

Direct 1:1 mapping for name, email, phone, job title, and address fields. HighLevel Contact has no native industry or department fields — those migrate as Short Text custom fields. Duplicate contacts are flagged before ingestion using email as the unique key.

HighLevel has no Lead object separate from Contact — all lead records land in the Contact object. FlitStack appends a custom field Lead_Status__c to preserve the original Salesforce Lead status (New, Working, Nurturing, etc.) so teams can filter converted vs. unconverted records in HighLevel.

Direct 1:1 mapping for deal name, amount, close date, and custom fields. HighLevel Opportunity has a Status pick-list that maps to Salesforce Opportunity Stage values. The HighLevel pipeline kanban board represents the deal stage visually. Opportunity-to-Contact associations use HighLevel's built-in Opportunity Contact Roles.

AscendixRE Property records — including address, property type, square footage, unit count, year built, and status — map to a HighLevel Custom Object named 'Property'. Each property field is recreated as a matching HighLevel field type (text, number, pick-list, or date). This counts toward the 10-custom-object limit in HighLevel.

Listing records carry listing type (For Sale / For Lease), listing price, MLS number, and availability status. These fields are recreated as HighLevel custom fields on a 'Listing' Custom Object. Each listing is associated to its Property record via HighLevel's custom object association feature.

Lease records include lease type (Office, Retail, Industrial), lease start/end dates, rent amount, and tenant name. All migrate to a 'Lease' Custom Object in HighLevel. Tenant association uses a Contact lookup field on the Lease object. Occupied counts and lease status pick-list values are mapped value-by-value.

Sale records contain sale price, sale date, buyer information, and commission details. These migrate to a 'Sale' Custom Object in HighLevel. Buyer is stored as a Contact lookup. Commission calculations (which AscendixRE handles natively) are recreated as custom number fields and formulas in HighLevel.

Availability records track available square footage, asking rent, and availability date per property. All fields migrate to a 'Availability' Custom Object in HighLevel and are associated to the parent Property. Teams with many availabilities per property should confirm they will stay under HighLevel's 10-custom-object limit after all CRE objects are created.

Direct 1:1 mapping. Salesforce Task fields (subject, status, priority, due date, description, whoId, whatId) map to HighLevel Task fields. HighLevel Task has a Type pick-list (Call, Email, SMS, Other) used to classify activity records. Original timestamps and assigned user are preserved.

HighLevel has no native Event object. Calendar events from Salesforce are ingested as HighLevel Tasks with Type='Meeting'. Start time, end time, and location are stored in custom datetime and text fields on the migrated task record. Recurring events are expanded into individual task instances.

Direct 1:1 mapping for title and body content. HighLevel Note stores the content as a Long Text field. The parent record (Contact, Opportunity, or Custom Object) is linked via the built-in relationship. Salesforce Notes with rich-text formatting are imported as plain text with formatting stripped.

HighLevel stores files as attachments on records with a 25 MB per-file limit. Files larger than 25 MB are split or linked via a URL custom field pointing to a cloud storage location. File names, MIME types, and creation dates are preserved as metadata fields. Inline images in Notes are downloaded and re-uploaded individually.

HighLevel users are matched to Salesforce users by email address. Unmatched owners are flagged before migration — the team either creates HighLevel user accounts for them or assigns their records to a fallback user. Owner name is preserved on each record as a custom text field for audit purposes.

If the source uses more than 10 custom objects (e.g., Capital Source, Commission Tracker, Stacking Plan, Tenant Rep Preference), the excess objects cannot all become HighLevel Custom Objects. FlitStack flags each overflow object and works with the team to either merge it into an existing custom object, store it as structured custom fields on Contact or Opportunity, or archive it as a CSV reference file.