Migrate from Onsite CRM to monday CRM

Onsite CRM Contact records export as CSV rows with name, email, phone, company association, and any custom field values. We map these directly to Monday.com CRM Contacts board Items. Monday.com's native contact fields (name, email, phone) accept the standard fields; any Onsite CRM custom fields map to Monday.com custom columns of the closest type (text, number, date, dropdown, or checkbox). Company association maps to the Contacts board's account link column if configured, or is preserved as a text company name column and reconciled against the Accounts board Items after import.

Onsite CRM Company records map to Monday.com CRM Accounts board Items. The company name becomes the Item name, and standard fields (domain, address, industry) map to corresponding Monday.com custom columns. We preserve the company-contact relationship by resolving the Monday.com Account Item ID and linking it back to each Contact Item after both boards are populated. If Onsite CRM exports company records without a unique ID column, we generate a stable hash from the company name and domain for deduplication during Monday.com import.

Onsite CRM Deal records map to Monday.com CRM Opportunities board Items. Deal name becomes the Item name, deal value maps to a Number column, close date maps to a Date column, and the pipeline stage name maps to a Status column. We extract the pipeline stage name from Onsite CRM's export and create corresponding Status column values in Monday.com's Opportunities board before importing the Deals. Owner assignment maps to Monday.com's Person column if the team member exists in the Monday.com workspace.

Onsite CRM pipeline stages are extracted from the CSV export header or from screenshots provided during scoping. Each stage name becomes a Status column value in Monday.com's Opportunities board. Stage order and any probability percentages (if exported) are preserved in a separate Number column as reference values for reporting. The customer chooses whether to use Monday.com's default color scheme for stage values or to match the Onsite CRM color coding if visible in screenshots.

Onsite CRM activity records (call logs, email threads, meeting records, and notes) require disaggregation because Monday.com does not have native engagement objects. We load activity history as Subitems on the relevant Opportunity Item, or as Updates on the Contact Item depending on the customer's preferred visibility model. Each activity record becomes a Subitem with type, date, duration, and notes fields. If Onsite CRM exports activities without a parent deal reference, we attach them to the Contact Item instead. Activity history volume is the primary driver of migration timeline for data-heavy accounts.

Onsite CRM tags applied to contacts and deals migrate as Monday.com Tags attached to Items. Alternatively, if the customer prefers a structured column for reporting, tags migrate to a Labels or Multi-Select column on the relevant board. We confirm the preferred strategy during scoping based on how the customer uses tags in Onsite CRM. Tag taxonomy normalization happens at this stage: duplicates, misspellings, and case variations are cleaned before import.

Onsite CRM user records map to Monday.com workspace members. We extract user email addresses and names from the owner field on exported records and map them to Monday.com team member accounts by email match. Any owner without a Monday.com user account is flagged for the customer to provision before production migration. Owner assignments on Deals and Contacts map to Monday.com's Person column, which assigns the Item to the team member in the workspace.

Onsite CRM custom fields on Contacts, Companies, and Deals require manual identification during scoping. We request screenshots of the field configuration in Onsite CRM and map each to a corresponding Monday.com custom column type: text fields become Text columns, picklist values become Dropdown or Labels columns, dates become Date columns, and numeric values become Number columns. Any unsupported field type (such as a complex conditional field or a formula-based calculation) is flagged for manual review and documented as requiring post-migration configuration in Monday.com.