Migrate from Briostack to Microsoft Dynamics 365 Sales

Briostack customers map 1:1 to Dynamics 365 Accounts. The customer name becomes Account Name, and the primary service address becomes the Account's primary address. Customer-level custom properties migrate as new_ custom fields on the Account table in Dataverse.

Briostack contact records map to Dynamics Contacts. The Contact is linked to the Account via the parentcustomerid lookup. If a Briostack customer has multiple contacts, all migrate as separate Contact records linked to the same Account. Contact-level custom properties become new_ fields on the Contact table.

Briostack service locations attached to a customer become secondary Account records representing physical properties. The primary Account represents the customer organization; each service location is a separate Account with a parent-child relationship using the Parent Account field in Dynamics. This preserves property-level history while keeping customer hierarchy intact.

Briostack work orders translate to Dynamics Opportunities. Job status (Scheduled, In Progress, Completed, Cancelled) maps to custom Opportunity stage values via explicit value_mapping since Dynamics stage labels differ from Briostack's service-status terms. Job amount maps to Opportunity Amount. Original job creation date becomes new_OriginalJobCreatedDate__c in Dataverse.

Individual services within a Briostack work order map to OpportunityLineItems in Dynamics. Each line item carries the service description as Product Description, quantity as Quantity, and price as Unit Price. If Briostack products are not pre-loaded in Dynamics, FlitStack creates placeholder product records first so OpportunityLineItem foreign keys resolve.

Briostack technicians map to Dynamics 365 system users by email match. Owner assignment on Opportunities resolves to the matched SystemUser's OwnerId. Unmatched technicians are flagged before migration; their work orders can be assigned to a fallback owner or a dedicated system user created for migration purposes.

Briostack job status values (Scheduled, In Progress, Completed, On Hold, Cancelled) require explicit value-by-value mapping to Dynamics Opportunity Stage or a custom status field. Probability weights are re-applied based on Dynamics stage defaults. Stage-entry timestamps are preserved as custom datetime fields for reporting continuity.

Briostack work order notes and internal comments migrate as Dynamics Annotations attached to the corresponding Opportunity. Original timestamps and author information are preserved. Rich-text formatting is maintained where the source format supports it.

Briostack custom properties beyond the standard schema map to new_ custom columns on the relevant Dataverse table. Briostack string properties become Text fields, numeric properties become Decimal or Whole Number fields, and date properties become DateTime fields. For each custom property, FlitStack creates the corresponding column in Dynamics before the migration run.

Briostack file attachments (photos, documents, signatures) attached to work orders are extracted and re-uploaded to SharePoint linked to the corresponding Opportunity record in Dynamics. File size limits of 10 MB per note attachment apply. Inline images in notes are downloaded and re-hosted in the SharePoint document library associated with the target Account.

Briostack invoices and billing records have no direct Dynamics 365 Sales equivalent — Sales handles Opportunities and Quotes but not AR/invoicing. Invoices are preserved as custom fields on the Opportunity and as PDF attachments; full accounting history requires Dynamics 365 Business Central for AR management, which is outside the scope of a CRM migration.

Briostack leads that have not been converted to customers map to Dynamics Lead records. Lead source, status, and rating migrate directly. Briostack lead scores map to a custom Integer field on the Dynamics Lead since no native lead-scoring field exists in Dynamics 365 Sales.