Migrate your Sugarcrm data

Standard CRM Account object. Sugar uses field labels for CSV import mapping rather than internal field names. We extract all database fields via the Sidecar UI export and map them 1:1 into the destination Accounts module.

Contacts module supports multiple email addresses per record with Primary, Invalid, and Opted Out flags. We preserve email address roles and opt-out status during migration to avoid re-triggering consent workflows in the destination system.

Leads is a standard Sugar module available across all tiers. We map Lead status, source, and conversion data into the destination's Lead or Contact object depending on whether the target platform has a separate Lead concept.

Opportunities represent deal records and are associated with Accounts and Contacts via Sugar's relationship model. We preserve the opportunity-to-account linkage and stage history during migration.

Revenue Line Items represent product-quantity-revenue entries attached to Opportunities. The import wizard supports bulk insert of line items via CSV, but we must validate that the parent Opportunity ID exists in the destination before loading to avoid orphaned records.

Quoted Line Items mirror Revenue Line Items but attach to Quotes. We map them to the destination's quote line item structure and flag any custom pricing formulas that may not translate directly.

Quotes inherit from the product catalog and carry expiration dates and approval statuses. We transfer quote records with their associated line items and preserve approval workflow state flags where the destination supports them.

Cases in Sugar Serve track customer support tickets with status, priority, and resolution fields. We migrate Cases with their conversation threads and attachments into the destination's ticket module.

Sugar's Product catalog includes pricing, cost, and inventory data. We export the full product record and map it to the destination's product or item catalog.

Campaigns module uses a Legacy UI in Sugar, which affects the export method. We handle this by exporting Campaigns via the legacy list view export and map campaign targets and status fields into the destination marketing module.

Tasks are standard Sugar activities linked to Accounts, Contacts, Leads, or Opportunities. We preserve assigned owner, due date, and status fields and map them to the destination's task or activity object.

Sugar allows custom fields via Studio and Module Builder. Custom fields do not auto-export in the standard CSV template and must be explicitly added to the export. We audit custom field definitions in the source instance and generate field-level mappings for each destination.

Sugar user records include role assignments, team memberships, and manager hierarchies. We map active Users to the destination user object and flag inactive users for customer decision on whether to migrate as inactive or exclude them entirely.