Migrate from Sugarcrm to monday CRM

Sugarcrm Accounts map to Monday.com Companies (an entity type within the People board). The Account name becomes the Company name, and website, phone, and address fields map to Monday's built-in Company columns. We preserve the parent-child account hierarchy as a top-level Company with nested sub-companies using Monday's Group structure. Account type and industry classification map to custom columns on the Company record.

Sugarcrm Contacts map to Monday.com People. The Person is linked to the target Company via Monday's native relationship column. Sugarcrm's support for multiple email addresses per contact (Primary, Invalid, Opted Out flags) requires a decision: Monday's Person record holds a single primary email; we import the primary address and flag opt-out status in a custom column, with secondary addresses held for manual reconciliation during the reconciliation window.

Sugarcrm Leads map to Items in a dedicated Leads board. Lead status, source, and conversion data transfer as column values. Sugarcrm's lead_score field maps to a custom numeric column in Monday. Any Leads that were converted in Sugarcrm are flagged with their conversion date and linked target Contact if the conversion record exists in the source export.

Sugarcrm Opportunities map to Monday Deals on the CRM board. Stage, amount, close date, probability, and loss reason transfer to corresponding Monday column types. The opportunity-to-account linkage is preserved by linking the Deal Item to the target Company record via Monday's relationship column. If the opportunity has a primary contact, we link that Person record as well.

Sugarcrm Revenue Line Items attach to Opportunities as product-quantity-revenue entries. Monday Deals hold a single monetary amount by default, but we model multi-line deals as either column splits or as sub-Items on the Deal. The parent Opportunity linkage is maintained in Monday by placing all line items as sub-Items under the parent Deal Item. Product name, quantity, and unit price transfer to sub-Item columns.

Sugarcrm Quotes map to Monday Deals with quote-specific columns added: quote number, expiration date, approval status, and total amount. Quote line items migrate as sub-Items following the same pattern as Revenue Line Items. Any quote PDF attachments are noted as manual re-upload items in the reconciliation handoff document.

Sugarcrm Cases migrate to Items in a dedicated Cases board. Case number, status, priority, resolution fields, and resolution date transfer as column values. Case conversations (threaded comments and email history) migrate as Activity log entries or item updates on the Monday Item. We preserve the case-to-contact linkage via Monday's relationship column pointing to the Person record.

Sugarcrm Notes linked to Accounts, Contacts, Leads, or Opportunities migrate as notes or update entries on the corresponding Monday Item. Rich-text formatting is preserved where Monday's text support allows. Notes without a parent record migrate to a general Notes board for reconciliation.

Sugarcrm Products migrate to Items in a Products board with columns for product name, SKU, cost, list price, and description. We set a single price per product and note any tiered or volume-based pricing in a text column for admin review.

Sugarcrm Tasks linked to Accounts, Contacts, Leads, or Opportunities migrate to Items in a Tasks board. Assigned owner, due date, priority, and status transfer to Monday column types. The task is linked to the parent record via a relationship column. Overdue status flags carry over as a boolean column.

Sugarcrm Campaigns migrate to Items in a Campaign board. Campaign status, type, start date, and budget transfer as column values. Campaign targets (Contacts and Leads assigned to the campaign) are not migrated as a linked relationship because Monday's CRM does not have a native campaign targeting model; instead we flag the campaign assignment on the contact record as a text column and note the rebuild in the automation handoff document.

Sugarcrm custom fields created in Studio or Module Builder require explicit audit and column-level mapping. Custom fields do not auto-export in Sugar's standard CSV template; we extract them by querying the field metadata via the Sugar API and adding corresponding custom columns in Monday before data import. The mapping is documented field-by-field with the Sugar field label, API name, and data type matched to the equivalent Monday column type (text, number, date, dropdown, checkbox).