Migrate from Method CRM to Freshsales

Method Contacts store name, email, phone, address, and custom fields as distinct records linked to a parent Entity. Freshsales Contacts map directly from Method Contacts with standard field mapping (firstname, lastname, email, phone, address). The key resolution step is confirming whether Method Contact custom fields belong to the contacts table (contact-specific) or the entity table (organization-level) because the mapping target differs. We preserve the contact's email as the dedupe key and link to the Freshsales Account created from the parent Entity.

Method Entity records represent companies, vendors, or employees synced from QuickBooks. Freshsales Accounts map directly from Method Entities with the Entity name becoming Account Name, the QB-linked address becoming the primary address, and balance or credit limit carried as custom fields. We resolve the parent relationship: any Method Contact with a parent Entity becomes a Freshsales Contact linked to the corresponding Account. This is the critical mapping that prevents orphaned Contact records in Freshsales.

Method Opportunities with stage, amount, close date, and owner map to Freshsales Deals. The pipeline stage names from Method transfer to Freshsales deal stages, and we preserve stage probabilities as percentages on each stage. Deals with a linked Contact and Entity map to Freshsales Deals with Contact and Account lookups resolved. Closed-won and closed-lost amounts and dates migrate as-is for historical pipeline reporting.

Method Activities (calls, meetings, tasks, and notes) linked to Contacts or Entities migrate to Freshsales Activities. We preserve the activity type, date, description, duration, owner, and any linked record references. Freshsales supports first-class activity recording; calls, meetings, and tasks appear in the contact and account timelines. Notes migrate as note objects linked to the parent Contact or Account.

Method Estimates are QuickBooks-synced transactional documents with line items, totals, and QB linkage metadata. Freshsales does not have a native estimate or quote object on all tiers. We map Estimates to Freshsales Deals with line item data stored as custom fields or, if the customer is on a Freshsales tier with quote capability, we create Quote records. QB linkage metadata is preserved in a text field for reference. The customer decides whether to re-create formal estimates in Freshsales or a connected quoting tool.

Method Invoices are QuickBooks-synced with line items, tax codes, and payment status. Freshsales has no native invoice creation; invoices live in QuickBooks. We map paid Invoices to closed-won Deals with invoice amount and payment date preserved in custom fields, and outstanding balances carried as deal amount notes. Unpaid invoices flagged in Method require the customer to decide whether to record them as open Deals or handle them in QuickBooks post-migration.

Sales Orders (available on Method Pro and Enterprise) map to Freshsales Deals with closed-won status and order details preserved in custom fields. Line items, order total, and QB entity references migrate as custom JSON or delimited text stored on the Deal record. The customer configures any order fulfillment workflows in Freshsales post-migration.

Method Customer Cases are Enterprise-tier-only and tied to the customer portal. Freshsales has a native Cases module on paid plans. Cases migrate with description, status, priority, owner, and linked Contact or Entity. If the customer uses Freshdesk for service alongside Freshsales CRM, we map Cases to Freshdesk Tickets via the native integration. Portal access associations map to Contact records with portal access noted in a custom field.

Method custom fields on Contacts, Entities, and Opportunities map to Freshsales custom fields with type translation: text fields, picklists, dates, numbers, and checkboxes translate to Freshsales field equivalents. The critical distinction is whether the custom field lives on the Method contacts table or the entity table because that determines whether it maps to a Contact custom field or an Account custom field in Freshsales. We extract and document all custom field definitions during scoping before migration.

Method Users map to Freshsales Users by email match. We extract all owners referenced on Contact, Entity, Opportunity, and Activity records and match by email against the Freshsales User table. Any Method Owner without a matching Freshsales User enters a reconciliation queue for the customer's admin to provision before record import resumes.