Migrate your Sage CRM data

Companies is the primary account object in Sage CRM, holding address, industry, and classification data. Export via SQL query or API is straightforward; we map it directly to the destination Account/Company object. Parent-company hierarchies are preserved via the PrimaryCompanyLink relationship.

Contacts link to Companies via the PrimaryCompanyLink foreign key. We extract all standard fields plus custom Contact fields and preserve the company association during import. Duplicate detection can be configured using Sage CRM's match-rule settings, which we review during scoping.

Sage CRM uses a separate Lead entity distinct from Contacts. Leads have their own lifecycle stages, qualification fields, and source tracking. We map Lead records to the destination CRM's Lead or Contact object depending on whether the destination has a separate Lead object; we preserve Lead_Status as a custom property to retain source context.

Opportunities track pipeline stages, revenue amounts, expected close dates, and owner assignments. We export all stage data and pipeline configuration. Custom opportunity fields and multi-currency amounts are preserved, but pipeline stage names require manual remapping in the destination CRM's pipeline editor.

Cases are the service/ticket object in Sage CRM, with severity, status, and assignment fields. Case-threaded communications are stored in a separate Communication table linked by case ID. We export Cases and flatten the communication thread into a notes/history field unless the destination CRM supports threaded conversations natively.

Sage CRM stores email, call logs, and meeting notes in the Communication table linked to entity IDs. These are entity-type agnostic (can belong to Company, Contact, Lead, Opportunity, or Case). We export Communications and associate them to the correct destination records by entity type and ID, which requires a mapping table built during discovery.

Sage CRM supports user-defined Custom Entities with their own fields and relationships. Each Custom Entity maps to the destination CRM's Custom Object or Notes/Related Items structure depending on complexity. We inspect the entity schema during discovery and determine the best-fit mapping strategy per entity.

Sage CRM workflow rules are defined in the database and include ASP-scripted actions and escalation triggers. These cannot be exported as data and are not portable across CRM platforms. We document every active workflow and escalation rule so the customer can manually rebuild them in the new CRM, prioritizing revenue-critical automations first.

Reports are stored in the Sage CRM report schema and reference entity fields by internal IDs. We export report definitions and data, but report formatting, formulas, and scheduling must be recreated in the destination CRM's reporting tool. We provide a report inventory to the customer at migration close.

Sage CRM Users have role-based security profiles controlling object and field access. User accounts are exported with role assignments, but destination CRM permission models differ structurally. We map Sage CRM roles to the closest permission tier in the destination CRM and flag discrepancies for manual review.