Migrate your Method CRM data

Contacts are the primary customer record in Method CRM, storing name, email, phone, address, and custom fields. The schema is stable and well-documented. We migrate Contacts 1:1, preserving all standard fields and any CRM-only custom properties.

Method CRM uses Companies as distinct records alongside Contacts, with the ability to associate multiple Contacts to a single Company. We map Companies to Accounts or Companies in the destination CRM with all linked Contact associations intact.

Opportunities track deals in a pipeline with stages, amounts, and close dates. Method stores pipeline stages as enumerated values. We migrate Opportunities with their stage history and associate them to the correct Contact or Company.

Activities include calls, meetings, tasks, and notes logged against a Contact or Company. We preserve activity type, date, description, and owner assignment during migration.

Estimates are transactional documents synced bidirectionally with QuickBooks. On the Pro and Enterprise tiers, we migrate Estimates preserving line items, totals, status, and QB linkage metadata so reconciliation is straightforward post-migration.

Invoices are QuickBooks-synced transactional records with line items, tax codes, and payment status. We preserve the full invoice schema including payments received and outstanding balance.

Sales Orders are available on Pro and Enterprise tiers. We migrate Sales Order records with all line items, statuses, and QB entity references.

Cases are introduced on the CRM Enterprise tier and represent customer support tickets. The case object schema is present but tier-gated. We map Cases to Tickets in the destination CRM, preserving description, status, priority, and agent assignment.

Method CRM allows custom fields on standard objects. Custom field names and data types vary by account configuration. We map each custom field to the destination's equivalent property, handling type differences (text vs. picklist vs. date) at the field level.

Pipeline stages are stored as picklist values associated with Opportunities. Method CRM supports customizable stage names and order. We preserve stage names and sequence during migration.

Method CRM user records map to Owner or User records in the destination. Email, name, and role are migrated; role-based permissions may not translate directly if the destination uses a different permission model.

Method CRM supports tagging Contacts and Companies for segmentation. Tags migrate as flat label strings and are re-created in the destination CRM as tags or custom list fields depending on the target platform's model.

Method CRM's REST API exposes Files endpoints for upload, download, and listing. We extract file metadata and binary content, then re-associate attachments to the correct parent record in the destination CRM.

Customer Portal records (portal users, access logs, approved documents) are accessible via API on Enterprise. We migrate portal access associations and link them to the corresponding Contact record in the destination.

Method CRM's calendar stores events with start/end times, assignees, and linked entities. We extract event records and map them to the destination calendar or activity model, noting that recurring event rules may not translate 1:1.