Migrate from Shark Byte CRM to HubSpot

Proposal status to dealstage mapping requires a value map for every Shark Byte status value

Shark Byte stores proposal lifecycle data in a custom proposal status field that has no direct HubSpot equivalent — the HubSpot dealstage pick-list is the closest model but Shark Byte status values such as Under Review or Revision Requested need explicit one-to-one mapping to HubSpot dealstage values. If a Shark Byte account has custom status values beyond the standard Draft, Sent, Accepted, Declined, those require HubSpot custom dealstage values to be created before migration. We deliver a full value map as part of the migration plan and configure the HubSpot pipeline stages accordingly before data lands. Without this pre-work, proposals in Revision Requested status land in a generic stage and lose their operational meaning in HubSpot reporting.

Service agreement and estimating custom fields need HubSpot custom properties created before migration

Shark Byte stores service agreement types, labor rates, contract periods, and building survey results as custom fields on the Deal or Company object. HubSpot has no native equivalents for these — Shark Byte's Labor_Rate field, for example, has no corresponding built-in HubSpot Deal property. We create each custom property in HubSpot under Settings > Properties before the migration run, which requires Owner or Admin access to your HubSpot portal. If your HubSpot plan tier restricts custom property creation, this step may require an upgraded portal. We confirm your plan tier during discovery and include property creation in the pre-migration setup checklist.

Proposal document attachments require re-upload and re-association in HubSpot

Shark Byte proposal documents are stored as file attachments on Deal records. When migrating to HubSpot, these files download from Shark Byte and re-upload to HubSpot's file manager, then attach to the corresponding Deal record manually or via API. HubSpot's file size limit is 25MB per file. If your Shark Byte proposals include large PDF bundles or multiple attached documents exceeding this limit, those files must be split or hosted externally with a link stored in HubSpot. We identify oversized attachments during the discovery audit and surface them in the migration plan so your team can decide whether to split documents before migration or accept the external-link approach.

HubSpot lifecycle stage is not automatically populated from Shark Byte contact data

HubSpot uses lifecycle_stage as the primary contact classification property and many HubSpot automation workflows trigger based on lifecycle stage transitions. Shark Byte contacts have no equivalent single property — they are categorized by proposal history and deal association rather than a lifecycle model. We do not assign lifecycle_stage values automatically because doing so without business input creates false customer records in HubSpot's marketing attribution data. Your team should define which Shark Byte contacts qualify as Customers (those with Accepted proposals or active service agreements) versus Leads (proposals sent but not accepted) and communicate that logic to us before we run the migration so we can apply the correct lifecycle values during import.

Shark Byte integrations with field-service tools do not transfer to HubSpot

Shark Byte integrates with XOi for visual site capture and Cosential for project management — these connections are native to the Shark Byte account and store tokens and webhook configurations that cannot be exported. When you move to HubSpot, these integrations must be rebuilt using HubSpot's App Marketplace, Zapier, or custom API connections. We can provide the technical specifications for your current integration endpoints as a rebuild reference for your HubSpot admin or integration developer, but the connection itself is outside the scope of the data migration.