Migrate from Shark Byte CRM to monday CRM

Shark Byte Customer records map to Monday.com Company Items. Standard fields including company name, address, and service history migrate as text or address Column types. Customer is the parent record for Estimates, Proposals, and Work Orders, so we insert all Company Items before any child record migration to satisfy lookup Column references. The dedupe key is company name plus address normalized to lowercase.

Shark Byte Contact records (individual points of contact at each Customer site) map to Monday.com People Items. Name, phone, email, and role fields migrate as Name, phone, email, and text Column types. We resolve the parent Company lookup using the Customer reference on each Contact record and set the linked Company Column on the People Item. Any Contact without a resolved parent Company is placed in a reconciliation queue for manual Company assignment before production cutover.

Shark Byte Estimates are the core product object and map to Monday.com Deal Items. Line items, labor rates, material costs, and pricing totals migrate as number Column types. Contract-term classification (1-3 year, 3-5 year, 10+ year) migrates as a Select Column, preserving the Shark Byte pricing bucket as a structured field rather than a free-text note. We flag any Estimate that lacks a linked Customer for the customer's admin to resolve before import because Deals require a Company link.

Shark Byte Proposals (generated from Estimates with pricing, scope, and terms) map to the corresponding Monday.com Deal Item. We migrate the proposal text as a long-text Column or Notes Column on the Deal, and any attached proposal PDFs or signed documents migrate as Files attached to the Deal Item. If Shark Byte exports Proposals as separate records rather than Estimate derivatives, we create a Proposal Items board with a Deal lookup Column to maintain the Estimate-to-Proposal relationship.

Shark Byte Service Agreements (recurring contracts tied to maintenance programs) map to Monday.com Deal Items with custom Columns for contract-specific fields. Term duration, equipment covered, maintenance scope, and billing frequency migrate as Select and text Columns. We preserve the original Shark Byte contract-term bucket classification and create a Select Column for contract type (preventive maintenance, full service, warranty). The parent Customer maps to the Deal's Company Column.

Shark Byte Work Orders (individual jobs dispatched to technicians) map to Items on a dedicated Work Orders board in Monday.com. Status, assigned technician, line items, and schedule migrate as Status, person, text, and date Column types. Mobile survey data (photos and site condition notes attached to Work Orders) migrate as Files. We create the Work Orders board during schema setup before migration, with a Company lookup Column linking each Work Order Item to the originating Customer.

Shark Byte file attachments on Customer, Estimate, Proposal, and Work Order records (including scope documents, mobile survey photos, and signed agreements) migrate as Files attached to the corresponding Monday.com Item. Image formats, compression levels, and EXIF metadata vary from the source mobile device; we extract at original resolution where possible and note any images with missing metadata. Attachment migration runs after parent Item creation to ensure the Item ID exists for the File attachment reference.

Shark Byte custom fields on primary objects (particularly Estimates and Service Agreements for equipment specifications, contract classification, and industry-specific data) migrate to Monday.com custom Columns. We define the Column type during scoping based on the source field data type: equipment model numbers become text, inspection outcomes become select, contract values become number. Custom field schema is deployed into the Monday.com workspace before any record migration begins.