Migrate from Propertybase to Microsoft Dynamics 365 Sales

Propertybase Company maps directly to D365 Account. Company name, address, phone, website, industry, and employee count transfer as Account field values. Parent-child company hierarchies in Propertybase map to the Account.ParentId lookup in D365; parent records must migrate before child records for referential integrity.

Propertybase Contact maps 1:1 to D365 Contact. Name, email, phone, job title, and address fields transfer directly. All D365 Contacts require an AccountId (primary company lookup) — contacts without a primary company in Propertybase receive a placeholder 'Unassigned' Account record to satisfy the Dataverse required-field constraint.

Propertybase Individual Contact records (where SystemIsIndividual = TRUE) map directly to D365 Contact. The individual-flag distinction is preserved as a custom 'Is_Individual_Contact__c' field on the Contact record since D365 does not have a native individual-vs-company contact distinction at the object level.

Propertybase Enquiry records route to D365 Lead if the enquiry has not been qualified into a deal. Enquiry status, source, and interest-level fields map to Lead custom fields. Qualified enquiries that have converted to offers in Propertybase map to Opportunity records instead.

Propertybase Listing records require a custom 'Property__c' table in D365 Dataverse. This table must be pre-created before migration with fields matching Propertybase Listing schema: address components, list price, property type, status (Active, Pending, Sold), bedrooms, bathrooms, square footage, and media URLs. We deliver a Dataverse table creation specification as part of the migration plan.

Listing-level fields (ListingName, Address, ListPrice, PropertyType, Status, Beds, Baths, SqFt) map field-by-field to the custom Property__c Dataverse table columns. Media URLs (property images) store as text fields pointing to re-uploaded file locations in D365 SharePoint or Dataverse file storage. Property media files are downloaded from Propertybase prior to migration and re-uploaded to maintain the original file references, ensuring that all property images remain accessible in the destination system.

Propertybase Offer/Contract records map to D365 Opportunity entities. The offer amount maps to Opportunity.Amount, offer status (Pending, Accepted, Declined) maps to Opportunity.StageName using a value-mapping table. The linked Listing lookup requires resolution to the Property__c table custom ID after Listings are migrated.

Accepted Propertybase Offers that represent binding contracts can optionally map to D365 Quote or Order entities if the destination uses Dynamics 365's quote-to-cash workflow. This requires a separate mapping decision based on your D365 configuration — we surface the choice in the pre-migration planning call.

Propertybase Favourite records (linking Contact to Listing for buyer interest tracking) map to a custom Dataverse junction table between Contact and Property__c. This relationship does not have a native D365 equivalent and requires a custom 'Property_Interest__c' junction entity with ContactId and PropertyId lookup fields.

Propertybase activity records (calls logged, emails tracked, meetings scheduled, notes attached) map to D365 Task and Appointment entities using the same ActivityPointer model. Original timestamps, owners, and regarding-object links (Contact, Account, or Property__c) are preserved. Notes migrate as D365 Note (annotation) records with original create dates.

Propertybase file attachments on any record (listings, contacts, companies, offers) are downloaded and re-uploaded to D365's SharePoint document management or Dataverse file storage. File size limits (default 128MB per file in Dataverse) apply; files exceeding this threshold are flagged for manual handling.

Propertybase custom objects (any __c Salesforce objects beyond standard Company/Contact/Listing/Offer) map 1:1 to custom Dataverse tables in D365. Each custom object requires pre-creation of a corresponding Dataverse table with appropriate column types before migration. We deliver a schema specification for each custom object during the planning phase.

Propertybase owner IDs (Salesforce User records) are resolved against D365 SystemUser records by email address match. Unmatched owners are flagged before migration — your team either provisions the D365 user account first or assigns records to a designated fallback owner. No record lands without a valid D365 owner.