Migrate from AscendixRE to Salesforce Sales Cloud

Direct field-to-field map. AscendixRE contacts are standard Salesforce Contact records, so the object structure is identical in both systems. Email, phone, name, title, and mailing address fields map directly without any transformation logic. Owner resolution uses email matching against destination Salesforce users to preserve the original record ownership assignments during migration. Any contacts without matching email addresses are flagged for manual owner assignment review after migration completes.

Direct field-to-field map. AscendixRE accounts are standard Salesforce Account records, maintaining the same field structure in both source and destination systems. Company name, website, industry, employee count, and annual revenue fields map directly to their Salesforce Account equivalents. Since Account is a standard Salesforce object, no custom field creation is required in the destination org, and all standard Account features like related lists and page layouts apply immediately after migration.

Direct field-to-field map. Lead object structure is consistent between AscendixRE and Salesforce, with both platforms using the standard Salesforce Lead object. Status, source, and rating fields map directly. Any custom lead scoring fields that exist in AscendixRE migrate as custom Number fields on the Salesforce Lead object. Lead conversion settings and assignment rules in the destination org will apply to migrated leads based on the standard Salesforce lead management configuration.

Direct field-to-field map. AscendixRE opportunities are Salesforce Opportunity records, so the core object structure transfers directly. Deal name, amount, stage, close date, and owner map directly to their Salesforce counterparts. Stage probability values and forecast category settings are re-applied from the Salesforce destination org side to ensure your sales forecasting pipeline reflects your current Salesforce configuration rather than carrying forward potentially outdated stage probability assumptions from AscendixRE.

Direct field-to-field map. Activity logs from AscendixRE including call logs, emails, and follow-up tasks migrate as Salesforce Tasks. Original timestamps are preserved to maintain the complete activity history timeline. Subject lines and owner assignments transfer directly, ensuring that the full record of client interactions, follow-up activities, and task assignments is intact in Salesforce for ongoing relationship management and compliance tracking purposes.

Direct field-to-field map. Scheduled meetings, property tours, and other calendar events logged in AscendixRE migrate as Salesforce Events. Start and end times transfer with original values preserved, maintaining accurate scheduling records. Attendee information including invitee names and email addresses migrates to Salesforce EventWhoIds and EventRelation records, ensuring that all scheduled property viewings and client meetings retain their participant information in the destination system.

AscendixRE Property records require a custom Property__c object in the destination Salesforce org. Property address, type (office, retail, industrial, land, multi-family), square footage, year built, and zoning information migrate as custom fields on the new Property__c object. FlitStack creates the complete custom object schema including all field definitions, data types, and pick-list values before loading any data into the destination org. This ensures referential integrity is maintained when related objects like Listing__c and Lease__c are loaded subsequently.

AscendixRE Listing records require a custom Listing__c object in the destination org. Listing status (active, under contract, pending, sold, off-market), asking price/rent, listing date, and property lookup link migrate as custom fields. Listings maintain their relationship to Property__c via a lookup field that references the parent property record. The destination Listing__c object must be created and the lookup field configured before Listing records are loaded to preserve the property-to-listing relationship.

AscendixRE Lease records require a custom Lease__c object. Lease start and end dates, tenant name, square footage, base rent, and CAM (Common Area Maintenance) charges migrate as custom fields. Lease__c maintains relationships to Property__c for the leased asset and to Contact/Account for tenant information. Tenant name maps to a Contact lookup where possible, with unmatched tenants stored as text for manual resolution post-migration to preserve the tenant relationship linkage in Salesforce.

AscendixRE Sale records require a custom Sale__c object in the destination Salesforce org. Sale price, sale date, buyer and seller information, and property lookup link migrate as custom fields on the new Sale__c object. Sale records maintain relationships to Property__c for the sold asset and to Contact/Account records for buyer and seller party information. Buyer and seller names are mapped to Contact lookups where matching contacts exist, with unmatched parties flagged for manual resolution to ensure proper party relationship tracking.

AscendixRE Availability records require a custom Availability__c object. Available square footage, asking rent, lease type (gross, net, triple net), and availability date migrate as custom fields on the new Availability__c object. Availability records link to Property__c via a lookup relationship that identifies which property has the available space. This relationship must be established in the destination org schema before Availability records are loaded, ensuring that all available space listings correctly reference their associated property records in Salesforce.

AscendixRE Capital Source records require a custom Capital_Source__c object in Enterprise-tier plans. Capital type (debt, equity, preferred), amount, investor contact lookup, and related deal information migrate as custom fields. Capital_Source__c objects may link to Opportunity or custom Deal__c records to track funding associated with specific transactions. This object is only created in the destination org if your AscendixRE plan includes Capital_Source__c functionality, and the related deal linkage must be configured before capital source records are loaded.

AscendixRE inquiry records capture prospective tenant, buyer, and landlord inquiries that need routing logic during migration. New prospect inquiries with no matching Contact record in Salesforce route to the Lead object for standard lead management. Follow-up inquiries from existing contacts route to the Contact record with an associated Opportunity created for ongoing deal tracking. Landlord listing inquiries may route to a custom Inquiry__c object if your Salesforce setup includes structured inquiry intake processes. The routing logic must be defined per inquiry type before migration begins so that all records land in the correct destination object with appropriate field population.

File attachments on AscendixRE records including property photos, lease documents, deal PDFs, and listing brochures migrate to Salesforce Files using ContentDocument and ContentVersion objects. Files are linked to their parent record (Property__c, Lease__c, Listing__c, Sale__c) via ContentDocumentLink junction records, maintaining the association between documents and their related business records. Salesforce's 25MB per-file size limit applies to all migrated files. Any AscendixRE files exceeding this limit are flagged during migration for manual upload to Salesforce after the automated migration completes.