Migrate from Markate to Nutshell

Markate's single Customer object contains both residential contacts and commercial accounts. We split on a pre-scoping rule agreed with the customer: organizations with a company name or commercial flag map to Nutshell Company; individuals or residential contacts map to Nutshell Person. Company records are imported first so that Person records referencing a commercial customer can link via the CompanyId lookup. Email address is used as the dedupe key across both objects. Markate's customer phone, address, and notes fields map directly to Nutshell's corresponding Person or Company fields.

Markate Estimates map to Nutshell Quotes. Estimate status (sent, accepted, declined) maps to Nutshell Quote status values. Line items from the Estimate migrate to Quote line items with product reference, quantity, and unit price. The linked Customer reference resolves to the Nutshell Person or Company created in the prior step. Amount totals and any accepted date carry over as metadata on the Quote record.

Markate Work Orders are the primary job-ticket entity and have no direct Nutshell equivalent. During scoping, the customer chooses one of two strategies: (A) seed Work Orders as Nutshell Deals with the Customer linked as the Account, job description in the Deal name or notes, status mapped to a Deal stage, and the Work Order amount as the Deal value; or (B) archive Work Orders as Notes linked to the Person or Company record for historical reference without creating pipeline clutter. Strategy choice affects the object count and mapping complexity. Assigned team member references require User provisioning in Nutshell (see Team Member mapping).

Markate Invoices carry line items, payment status, and amounts. If the customer chose Strategy A for Work Orders and created Deals, Invoices can be attached as Notes to the related Deal with payment status and balance noted. If Strategy B applies, Invoices link to the Person or Company. Partial payment history and totals migrate as note content. Nutshell does not have a native accounts-receivable or invoice object; the customer may use a separate accounting tool post-migration.

Markate Items and Categories define the product and service catalog used in Estimates and Invoices. Items map to Nutshell Products with the item name as Product Name and any SKU as Product Code. Categories map to Nutshell Tags on the Product record, since Nutshell Products do not have a native category hierarchy. Categories must import before Items to satisfy the tag reference. Unit price and description carry over from the Markate Item record.

Markate Expenses track job-related costs linked to Work Orders or Customers. They have no Nutshell equivalent object. We migrate expense records as Notes on the linked Person or Company, with vendor, amount, and date preserved in the note body. Receipt attachments are flagged as manual-recreate items because Markate's Data Migration tool does not export attachments.

Markate Team Members are billable users assigned to Work Orders and Invoices. We import team member records to provision the corresponding Nutshell Users, using email as the match key. Any Markate team member without a corresponding Nutshell User account goes into a reconciliation queue for the customer's admin to provision before Work Order import begins, since Deal and Work Order assignment requires a valid OwnerId. Active status, role name, and phone migrate to Nutshell User fields.

Markate does not expose custom field definitions or values through its CSV export interface. Any custom fields the customer configured in Markate (for Customers, Estimates, Work Orders, or Invoices) are not visible in the exported data and cannot be migrated. We document each identified custom field during scoping and provide a re-entry checklist for the customer to recreate them as Nutshell custom fields post-migration.

Markate's Data Migration tool does not export or import file attachments including photos, signed documents, and receipts associated with Customers, Work Orders, Estimates, or Invoices. We flag all attachment-containing records during pre-flight analysis and deliver a manual-migration checklist enumerating every file to re-upload in Nutshell after cutover. Photos linked to Work Orders via CompanyCam require a separate CompanyCam reconnection step in Nutshell if that integration is in use.