Migrate from Shark Byte CRM to Freshsales

Shark Byte Customer records (representing the end-client organization or homeowner) map directly to Freshsales Account. The standard fields (company name, address, contact details) align to Freshsales Account fields. We use the company name or address as the dedupe key during import. Account is created before any Contact import so the Account-Contact relationship is satisfied at insert time.

Shark Byte Contact records (individual points of contact at each Customer site) map to Freshsales Contact. Fields including name, phone, email, and role map to their Freshsales equivalents. We resolve the parent Account by matching the Customer name or address from the source to the destination Account created in the prior phase.

Shark Byte Estimates are the core product object in the source platform, built using the contract-term estimating engine. We map Estimate records to Freshsales Deals, preserving line items, labor rates, and material costs as Deal product entries or as structured notes. The contract-term bucket (1-3 year, 3-5 year, 10+ year) migrates as a custom picklist field on the Deal so the term classification survives in Freshsales even without the native estimating engine.

Shark Byte Proposals generated from Estimates map to Freshsales Deals, with the proposal PDF and any signed documents migrating as files attached to the Deal. The proposal's pricing, scope, and terms migrate as structured Deal fields or product line entries. We link the Deal to the originating Account and Contact from the Estimate mapping.

Shark Byte Service Agreements (recurring maintenance contracts tied to the customer) do not have a direct Freshsales equivalent object. We map each Service Agreement as a Note attached to the relevant Account, capturing the agreement type, term bucket, pricing structure, and any associated equipment specifications. The customer creates a custom Contract object in Freshsales if they want a formal record type for recurring agreements; we document the recommended custom object schema during scoping.

Shark Byte Work Order records (individual jobs dispatched to technicians) map to Freshsales Case. We preserve Work Order status, assigned technician (as a custom Contact or User field), line items, and timestamps. The mobile building survey data attached to Work Orders migrates as files linked to the Case. Work Order-to-Estimate linkage is preserved by populating a custom What_ID reference or link field in the Case.

Shark Byte attachments on Customer, Estimate, Proposal, and Work Order records (scope documents, mobile survey photos, signed agreements) migrate as Freshsales Files linked to the parent record. We extract attachments at original resolution where available. Note that some images from older mobile surveys may be compressed or missing EXIF metadata; we document any format inconsistencies in the migration report for admin review.

Shark Byte custom fields on Estimates and Service Agreements (equipment specifications, contract classification, term-specific pricing logic) map to Freshsales custom fields on Deal and Account respectively. We create the corresponding Freshsales custom field schema before data import. Custom field types are mapped to their closest Freshsales equivalents (text, number, picklist, date, currency). Note that Shark Byte's estimating template logic (formula-driven pricing calibrated on historical contracts) does not migrate as functional code; we document the field-level values for manual reconstruction.