Migrate from Shark Byte CRM to Microsoft Dynamics 365 Sales

Shark Byte Customer records (representing the end-client organization or homeowner for service work) map directly to Microsoft Dynamics 365 Account. The standard fields (company name, address, phone, email) map to Account.name, Address fields, and Telephone. We use Account as the parent record for all subsequent imports so that the AccountId lookup is satisfied at the moment Contact and Work Order imports run. Customer service history from Shark Byte migrates as Notes attached to the Account or as a custom field set.

Shark Byte Contact records (individual points of contact at each Customer site) map to Dynamics 365 Contact. Standard fields (name, phone, email, role) map directly. We create the parent Account before Contact import so that the AccountId lookup resolves at insert time. Any Shark Byte Contact without a matching Account receives a placeholder Account for migration continuity.

Shark Byte Estimates are the core product object in Shark Byte CRM and require the most translation work. Each Estimate maps to a Dynamics 365 Opportunity, with custom fields capturing the contract-term classification (1-3yr, 3-5yr, 10+yr bucket), labor rate assumptions, material markup logic, and pricing confidence level from the Shark Byte estimating engine. The estimate line items map to OpportunityLineItem records with Product2 references. If the customer has both active Estimates (ongoing opportunities) and expired Estimates (historical record), we migrate active Estimates as Opportunities and archive expired Estimates as a custom Entity with a closed status flag.

Shark Byte Proposals (generated from Estimates with pricing, scope, and terms) map to Dynamics 365 Quote. Quote status (draft, sent, accepted, rejected) migrates as QuoteStatus. The Proposal's linked Estimate reference migrates as a custom field on Quote pointing to the Opportunity that carries the Estimate's translated data. Proposal PDFs and signed documents migrate as SharePoint files linked via Dynamics 365's native document management to the Quote record.

Shark Byte Service Agreements (recurring maintenance contracts tied to 1-3yr, 3-5yr, or 10+yr term buckets) require a destination design decision during scoping. In Microsoft Dynamics 365 Sales alone (without Field Service), Service Agreements migrate as a custom Contract entity with contract-term classification fields, or as Account-level contract records with a custom duration field. If the customer licenses Dynamics 365 Field Service, the standard Contract entity becomes available. We flag this decision during scoping and configure the destination schema before any data moves.

Shark Byte Work Orders (individual jobs dispatched to technicians with status, assigned technician, and line items) have no direct Microsoft Dynamics 365 Sales equivalent. If the customer licenses Dynamics 365 Field Service, Work Orders map to Work Order records with Bookable Resource Bookings tracking technician assignments. Without Field Service, Work Orders map to a custom entity with fields for job status, site address, assigned technician (User lookup), and service type. We pre-create the custom entity schema before migration so that Work Order data imports cleanly.

Shark Byte attachments (scope documents, photos from mobile surveys, signed agreements) attached to Customer, Estimate, Proposal, and Work Order records migrate as SharePoint files in the Dynamics 365 native document management library. We extract files at original resolution from Shark Byte exports, create matching SharePoint folder structures aligned to the Account and record hierarchy, and link each file to the corresponding Dynamics record via SharePoint integration. Some images from older mobile surveys may be compressed; we document any format anomalies during extraction.

Shark Byte custom fields on Estimates and Service Agreements (equipment specifications, contract classification codes, term-length pricing buckets) map to Dynamics 365 custom fields on the corresponding entity. We pre-create the destination schema in a Dynamics 365 Sandbox before migration, using the Shark Byte custom property API names as a naming reference and mapping field types to their closest Dynamics equivalents (text to Single-Line Text, numeric pricing fields to Decimal or Currency, term classifications to Option Sets).