Migrate from Markate to Pipedrive

Markate Customers with a company name field map to a Pipedrive Organization; the primary contact person maps to a Pipedrive Person linked to that Organization. Sole proprietors with no company name map to a Person only. We use the customer name as the Person name field and extract email and phone from the Markate contact fields. The Organization is created first, then the Person is linked via the org_id field at migration time.

Markate Estimates map to Pipedrive Deals. The Markate estimate status (sent, accepted, declined) maps to Pipedrive deal status (open, won, lost) with a custom field markate_estimate_status__c preserving the original Markate value. The estimate total amount maps to the Pipedrive deal value. We resolve the Person or Organization lookup from the linked Markate Customer before Deal insert.

Markate Work Orders are the core job ticket object and map to Pipedrive Deals. The Work Order number becomes the deal title, and the job description maps to the deal's notes field. Assigned team members require User lookup resolution in Pipedrive. Status fields (scheduled, in-progress, completed) map to open/deal stage values, with completed Work Orders set to Won or a custom closed stage. Job site address migrates to the deal's address fields or a custom address field.

Markate Invoices map to Pipedrive Deals when the invoice represents a billable project or service. The invoice total becomes the deal value, and the payment status (paid, partial, unpaid) is preserved in a custom field markate_invoice_status__c. For recurring service invoicing, the Invoice can also be documented as an Activity note rather than a deal, depending on the customer's business model decision made during scoping.

Markate Items (products and services) and Categories map to Pipedrive Products and Product Categories. Categories must be imported first to establish the product grouping structure. Items with prices map to Products with Standard Price Book entries. The Markate SKU becomes the Pipedrive Product code. Products are imported before Deals so that line-item associations can be resolved during Deal creation.

Markate Expenses track job-related costs and can map to Pipedrive Activities (as a logged note with a due date) or to a custom expense tracking object depending on the customer's reporting needs. The expense vendor, amount, and date migrate; the original receipt attachment is noted as a manual-rebuild item. We document the chosen mapping strategy during scoping based on how the customer uses expense data in Pipedrive.

Markate Team Members are billable users assigned to Work Orders and Invoices. We extract the team member list and attempt to match by email against the destination Pipedrive User records. Team members without matching Pipedrive Users go to a reconciliation queue for the customer admin to provision before record import resumes, since OwnerId references on Deals are required.

Markate does not expose custom field definitions via its CSV export interface. Any custom fields added by the customer in Markate are not visible in the exported data. We explicitly document this gap during scoping and create a custom field mapping worksheet for the customer to define which custom fields they need in Pipedrive, then pre-create those fields in Pipedrive before migration begins.

Markate's Data Migration tool does not export file attachments including photos, signed documents, and receipts. We flag all attachments as manual-migration items and provide a checklist of files organized by Customer, Work Order, and Invoice for the customer to re-upload in Pipedrive after migration. Photos from Work Orders are the highest-priority attachment category to address in the manual-migration checklist.

Markate's Customer Portal allows self-service booking and payment for clients. This portal data (booked appointments, payment history, customer-facing documents) does not live in Markate's CSV export and has no direct Pipedrive equivalent. We document the Customer Portal as a replaced-by-Pipedrive feature and recommend the customer configure Pipedrive's customer-facing capabilities or a third-party portal integration post-migration.