Migrate from Shark Byte CRM to Salesforce Sales Cloud

Shark Byte Customer records (representing the end-client organization or homeowner) map directly to Salesforce Account. Standard fields (company name, address, contact details) transfer to Account Name and address fields. We use the Shark Byte customer ID as an external ID on the Account for lookups during subsequent object imports. Customer records with multiple Contact records are resolved after Account creation so that Contact.AccountId is populated at insert time.

Shark Byte Contact records (individual points of contact at each Customer site) map to Salesforce Contact. Name, phone, email, and role fields transfer directly. We resolve Contact.AccountId via the Account external ID lookup after Account import completes. Any Contact without a parent Customer record is flagged for manual Account assignment before migration continues.

Shark Byte Estimates are the core product object and map to Salesforce Opportunity. Each Estimate's contract-term bucket (1-3 year, 3-5 year, 10+ year) is preserved in a custom field sb_contract_term__c on the Opportunity so that pricing logic tied to term length is not lost. Line items, labor rates, and material costs transfer to Opportunity fields or custom Opportunity Product fields depending on the customer's line-item complexity. The Estimate status maps to Opportunity StageName with a mapping table defined during scoping.

Shark Byte's contract-term classification buckets are calibrated to the customer's own historical data and are not standardized across installations. We extract each Estimate's term classification during scoping and create a custom picklist field on the Opportunity object with the customer's specific bucket values. This prevents term-length pricing from collapsing into a generic one-time quote structure.

Shark Byte Proposals (generated from Estimates with pricing, scope, and terms) map to Salesforce Quote if the destination Salesforce org includes Sales Cloud Professional or higher. Quote is a standard Salesforce object from Professional tier. Proposal PDFs and signed e-signature documents migrate as ContentDocument records attached to the Quote via ContentDocumentLink. If the destination org does not include Quote, Proposals migrate to a custom Proposal__c object with the same fields.

Shark Byte Service Agreements (recurring contracts between customer and service company, often tied to maintenance programs) do not have a direct Salesforce standard object equivalent. Salesforce Contracts is a post-sale document object; it does not track pre-sale recurring contract status. We create a custom object Service_Agreement__c with fields for agreement term, renewal date, coverage scope, and associated Account and Contact lookups. The contract-term bucket from Shark Byte maps to a picklist field on this custom object.

Shark Byte Work Orders (individual jobs dispatched to technicians) map to Salesforce Case if the destination org includes Service Cloud or Field Service. Work Order status, assigned technician, line items, and site condition data transfer to Case fields. If Field Service Lightning is in scope, Work Orders can map to FSL__Service_Appointment__c with technician assignment via Salesforce User lookup. We determine the appropriate mapping during scoping based on the destination org's installed products.

Photos and site condition data captured via Shark Byte's mobile surveying tools attach to Work Orders and Estimates. We extract all available attachments at original resolution where file format permits. Image formats, compression levels, and metadata vary based on the mobile device used; older mobile surveys may be compressed or missing EXIF metadata. We link ContentDocument records to the parent Work Order or Estimate (now Case or Opportunity) via ContentDocumentLink. Compression artifacts are documented in the extraction report.

Shark Byte supports custom fields on Estimates, particularly for industry-specific data like equipment specifications or contract classifications. We create matching custom fields on the Salesforce Opportunity object with equivalent data types during schema design. Custom fields are created in a Salesforce Sandbox first, validated, then deployed to production. Field-level security and field-level read/edit permissions are set per profile during deployment.

Shark Byte Service Agreements carry custom fields specific to the mechanical service and HVAC industry such as equipment model, service frequency, and coverage tier. These map to custom fields on the Service_Agreement__c custom object we create. We match data types (text, number, picklist, date) during scoping and create the fields in the Sandbox before production migration.

Shark Byte Owner records (sales reps and technicians assigned to Customers, Estimates, Work Orders) map to Salesforce User by email match. We extract every distinct Owner ID from source records, match against the Salesforce destination org's User table, and flag any Owner without a matching User in a reconciliation queue for the customer's admin to provision. Migration cannot proceed past object imports requiring OwnerId until this queue is resolved.

Shark Byte supports notes and tasks attached to Estimates, Proposals, and Work Orders. These migrate to Salesforce Task records linked to the parent record (Opportunity, Quote, Case) via WhatId. The ActivityDate preserves the original Shark Byte timestamp for timeline ordering. Note body migrates as Task Description or as a Salesforce Note if rich text formatting is present.