Migrate from BoldTrail BackOffice to Microsoft Dynamics 365 Sales

BoldTrail agent hierarchy requires manual Dataverse user provisioning before migration

BoldTrail's Agent object is a first-class entity with onboarding workflows, commission splits, and team membership. Dynamics 365 Sales treats agents as Dataverse SystemUser records, which require explicit licensing. Agents who will not receive Dynamics licenses must map to Contact records, and their transaction ownership must reassign to a licensed Dataverse user. We flag every unresolved agent before migration and require a decision (license or reassign) before the full run commits — no record lands without an owner.

Real-estate transaction type has no native Dynamics 365 Sales field — custom columns required

BoldTrail transaction types (Listing, Buyer Representation, Lease, Referral) are standard fields. Microsoft Dynamics 365 Sales Opportunity has no native real-estate transaction type attribute. We create new_transactiontype__c as a custom picklist on the Opportunity table, but this means your Dynamics 365 admin must add the column through the Power Apps maker portal before the migration runs. Additionally, any Dynamics 365 Sales views or reports that reference transaction type must be rebuilt after migration.

Dynamics 365 Sales Professional caps custom tables at 15 — complex BoldTrail setups may require Enterprise

If your BoldTrail configuration includes more than 15 custom property fields or custom objects, a migration to Dynamics 365 Sales Professional will exceed the custom-table limit. The platform will block creation of additional custom tables. We audit your custom field count during the planning phase and recommend Sales Enterprise if your field count exceeds the Professional threshold. This is a licensing decision that affects the entire migration scope, not a data issue.

Commission calculation logic does not migrate — exported as JSON for Power Automate rebuild

BoldTrail calculates agent commission splits, cap splits, and tiered rates natively. Microsoft Dynamics 365 Sales has no commission calculation engine. The commission data migrates as custom fields (new_commissionrate__c, new_agentsplit__c) but the calculation logic — tiered rates, cap adjustments, ACH disbursement triggers — must be rebuilt in Power Automate or a custom Power Apps component. We export the BoldTrail commission-rule configuration as a structured JSON file your admin uses as the rebuild specification.

Transaction documents re-upload to SharePoint — e-signature state does not transfer

BoldTrail's e-signature status (signed, pending, voided) is embedded in its transaction workflow. When documents migrate to Dynamics 365 Sales SharePoint locations, the e-signature audit trail resets — signed PDFs appear as standard files with no signature status flag. We re-upload documents but do not preserve the BoldTrail e-signature state. Teams using BoldTrail's built-in e-signature must re-initiate signature workflows in Dynamics 365 using Microsoft Purview Compliance Manager, DocuSign, or AdobeSign after migration.