Migrate from Markate to Salesforce Sales Cloud

Markate Customers map directly to Salesforce Account. The customer's company name becomes Account.Name; phone, email, address, and notes fields map to typed Salesforce fields (Phone, PersonEmail, BillingAddress). We run pre-flight duplicate analysis on the exported CSV against existing Salesforce Account names using fuzzy matching and present a deduplication report before importing, because Markate's Data Migration tool does not check for duplicates at import time.

If the Markate Customer record includes individual contact names separate from the business name, we also create Salesforce Contact records linked to the Account. This is most relevant for enterprise customers where the Account represents the company and the Contact represents the primary decision-maker or job site coordinator. We resolve the AccountId reference before Contact insert to satisfy the Lookup relationship.

Markate Items and Categories define the product and service catalog used in Estimates and Invoices. Categories must be imported first to establish the parent reference structure. Items map to Salesforce Product2 records with the item name, SKU (if populated), and unit price. We create a Standard Pricebook entry during import so that line items on migrated Estimates and Invoices can reference the price. If Markate Categories do not map cleanly to Product2 families, we document the gap and recommend a Category-to-Product Family mapping decision during scoping.

Markate Estimates map to Salesforce Opportunity at the header level, with line items preserved as OpportunityLineItems. The Estimate status (sent, accepted, declined) maps to Opportunity StageName values that we configure before migration — accepted maps to a won stage, declined to closed lost, and sent to a mid-funnel stage. If the customer uses Salesforce Field Service Lightning, Estimates may alternatively map to Work Order objects with custom fields carrying Estimate metadata.

Markate Work Orders are the job ticket object and map to Salesforce Case. We map Work Order status to Case Status, assigned team members to Case Owner (User lookup), job details and description to Case Description, and scheduled date to Case Created Date or a custom date field. If Salesforce Field Service Lightning is in scope, Work Orders map to the FSL Work Order object with ServiceResource and WorkOrderLineItem relationships preserved.

Markate Invoices map to Salesforce Invoice (if Salesforce Billing is enabled) or to Opportunity with invoice-specific custom fields capturing invoice number, amount, payment status, and payment method. Line items migrate as OpportunityLineItems referencing the Product2 records created from Items. Partial payment status migrates as a custom field since Salesforce Invoice supports partial payment recording. If Salesforce Billing is not enabled in the destination org, we default to the Opportunity-with-custom-fields pattern.

Markate Expenses track job-related costs and link to Work Orders or Customers. Since Salesforce does not have a native Expense object in Sales Cloud, we pre-create a custom Expense__c object with fields for Amount, Vendor, Date, Description, and Work_Order__c lookup. We migrate expense records as Expense__c records linked to the parent Case (Work Order). Receipt attachments do not migrate through Markate's Data Migration tool and are flagged as manual-recreate items.

Markate Team Members are billable users assigned to Work Orders and Invoices. We import Team Member records to preserve assignment history, but map User IDs carefully since Salesforce uses a different User ID schema. We resolve Team Members by email match against Salesforce Users. Any Team Member without a matching Salesforce User is held in a reconciliation queue for the customer's admin to provision before record import resumes, since OwnerId references are required on Case and Opportunity.

Markate's Data Migration tool does not export or import file attachments — photos, signed documents, and receipts associated with Work Orders, Invoices, or Estimates are not included in the CSV export. We flag all attachments as manual-migration items and provide a checklist organized by object (Work Order ID, Invoice ID) that the customer's admin uses to re-upload files to Salesforce ContentDocument records linked to the parent Case, Opportunity, or Account. No data transformation is possible for this gap.

Markate does not expose custom field definitions via its CSV import interface. Any custom fields added by the customer in Markate are not visible in the exported CSV data. We document the full list of custom fields identified during scoping as a gap report, and the customer re-enters these values as custom fields on the Salesforce object post-migration or maps them to existing Salesforce fields during the handoff call. No automated migration is possible for this gap.

Markate Estimate line items (quantity, unit price, description) map to Salesforce OpportunityLineItem. We resolve the Pricebook2 reference and Product2 reference at migration time. Total amounts are calculated from quantity and unit price and stored as Salesforce LineItemAmount. If an Estimate references an Item that does not exist in Salesforce Product2, we create the Product2 record at migration time to satisfy the foreign key.

Markate Invoice line items map to Salesforce OpportunityLineItem in the same manner as Estimate line items, using the same Pricebook2 and Product2 resolution logic. Invoice-level discounts and tax amounts map to custom fields on OpportunityLineItem or Opportunity depending on the customer's discount structure. Payment status (paid, partial, unpaid) maps to a custom field since Salesforce Invoice standard status does not cover partial payment cleanly without custom configuration.