Migrate from Markate to Freshsales

Markate Customers map to Freshsales Contacts. We resolve the Contact-Account relationship by creating a Freshsales Account for each Customer (using the customer name or company name field as the Account Name) before importing Contacts, then setting the AccountId lookup on each Contact record. Email is the dedupe key; first name, last name, phone, address, and notes fields map directly. If Markate has separate contact-level records (multiple contacts per customer), we split them into individual Contact records under the same Account.

Markate Customer records also populate Freshsales Account fields. The customer address maps to Account ShippingAddress; customer phone maps to Account Phone; customer email maps to Account Email if no Contact-level email exists. We run a pre-flight duplicate analysis to detect Markate customers that may represent the same business entity and present a deduplication report before import, since Freshsales Account deduplication by name is configurable but Markate's CSV loader does not enforce it.

Markate Items map to Freshsales Products (Product Name, SKU, Unit Price, and Description). Markate Categories map to Freshsales Product Categories. We import Categories first to establish the parent reference for Items, then import Items. If a Markate Item references a Category that does not yet exist in Freshsales, we create the Category during the Items migration phase. Product images and attachments do not export from Markate and are noted as manual-recreate items.

Markate Estimates map to Freshsales Deals. Estimate total amount and status (sent, accepted, declined) map to Deal Amount and Deal Stage. We create a Freshsales Pipeline with stages that correspond to Markate estimate statuses before migration. If the destination is Freshsales Pro or Enterprise, Estimates with line items can map to the native Quote object; on Free or Growth tiers, we store estimate data on the Deal record using custom fields for line-item totals and item names. We resolve CustomerId as a Contact lookup on the Deal.

Markate Work Orders map to Freshsales Cases. Work Order job details, scheduled date, assigned team members, and status fields map to Case Subject, Created Date, Owner (User lookup), and Status. We configure Freshsales Case Record Types before migration so that Work Orders from Markate receive a dedicated Case type distinct from support tickets. If Freshsales Service Hub is not licensed, Work Orders map to Deals with a custom Work Order number field; the customer confirms the preferred mapping during scoping.

Markate Invoices map to Freshsales Deals with invoice-specific custom fields. Invoice amount, balance due, payment status (paid, partial, overdue), and payment method map to Deal Amount and custom fields on the Deal record. We set the Deal Stage to Closed Won upon import if the Markate invoice status is paid, preserving the revenue recognition date. Partial payments are stored in a custom multi-select field. Freshsales has no native invoice object; invoice PDF attachments are excluded from Markate export and listed in the manual-migration checklist.

Markate Expenses map to Freshsales Note records linked to the parent Case or Deal. Expense vendor, amount, date, and description fields map to Note Title, Note Body (formatted as structured text), and Created Date. Receipt attachments do not export from Markate and are noted in the manual-recreate checklist for the customer to re-upload as Freshsales attachments. If expenses represent billable costs that affect invoice amounts, we store expense data as custom fields on the related Deal rather than standalone Notes.

Markate Team Members (employees assigned to Work Orders and Invoices) map to Freshsales Users. We resolve assignments by matching the team member name or email to a Freshsales User record. If a Markate team member has no corresponding Freshsales User, we flag them in a reconciliation report for the customer's admin to provision the User before import resumes. OwnerId references on Work Orders and Invoices are resolved at migration time using this User mapping. Active versus inactive status on the team member record maps to Freshsales User Active flag.