Migrate from Markate to HubSpot

Markate customers are person-or-organization records linked to work orders and invoices. We split the name field into HubSpot Contact firstname and lastname, create a HubSpot Company record from the business name, and link Contact to Company via the primary association. Phone, email, address, and notes migrate as Contact properties.

HubSpot has no native work-order equivalent. Markate work-order records (status, technician, service type, location, schedule) migrate into a HubSpot custom object with custom fields — or into the Ticket object if the team uses HubSpot's service hub. Status values map to a custom pick-list. GPS coordinates migrate as lat/long custom fields or text if HubSpot's geo-mapping is not enabled.

Markate invoices carry amounts, line items, payment status, due dates, and QuickBooks sync flags. HubSpot has no native invoice object. We migrate invoices as a custom Invoice__c object with Amount__c, Status__c, Due_Date__c, and Payment_Method__c custom fields. Alternatively, for simpler setups, invoice totals become deal amounts and line items are linked to the associated deal.

Markate estimates have acceptance status, expiry dates, and line items. HubSpot's Deals with line items serve as a functional equivalent — we migrate accepted estimates as closed-won or closed-lost deals; pending estimates become open deals. For teams that treat estimates as standalone documents, a custom Estimate__c object preserves the full document with acceptance status and expiry date as custom fields.

Markate line items (service descriptions, quantities, unit prices) map directly to HubSpot Products and associated Line Items. We preserve the product name, SKU, price per unit, and quantity. Products in HubSpot are reusable across deals, so each unique Markate item becomes a HubSpot product record.

Markate categories define service types (e.g., plumbing, electrical, HVAC) and item groupings. HubSpot has no native category object. We map categories to a custom pick-list field (Service_Category__c) on the work-order or contact record. If categories vary significantly by team, a custom object may be warranted.

Markate expense records (amount, category, date, linked work order) have no native HubSpot equivalent. We preserve them as a custom Expense__c object linked to the associated work order via a lookup relationship, or as a custom field on the deal if the team uses HubSpot deals for job profitability tracking.

Markate assigns work orders to owners or technicians. We resolve each Markate owner/technician by email against HubSpot users. Unmatched owners are flagged before migration — the team either creates HubSpot user accounts or assigns those records to a fallback owner. This prevents orphaned work orders landing without an owner.

Markate payment records (payment date, method, amount applied, QuickBooks sync status) migrate as custom fields on the Invoice__c custom object. Payment status maps to a pick-list: Paid, Partial, Overdue, Pending. QuickBooks sync flags are stored as a text field for reference — integrations must be rebuilt in HubSpot.

Markate stores business name, address, phone, website, and notes per customer organization. These map directly to HubSpot Company properties: name, address, phone, website. HubSpot's Company object supports industry, employee count, and annual revenue — we map where Markate provides those fields and leave the rest blank for enrichment post-migration.

Markate files attached to work orders, invoices, or customer records re-upload to HubSpot Files and are linked to the appropriate record. File size limits and inline-image handling follow HubSpot's file storage constraints. Photos and documents from CompanyCam integrations are downloaded and rehosted in HubSpot Files.

Markate's QuickBooks sync status (synced, error, pending) has no HubSpot equivalent. We preserve it as a custom text field (QB_Sync_Status__c) for reference. The actual QuickBooks integration must be rebuilt using HubSpot's native QuickBooks connector or a third-party integration — this is not migratable data.