Migrate from Jobnimbus to HighLevel

JobNimbus Contact maps directly to HighLevel Contact. Name, email, phone, address, and owner assignment carry forward. JobNimbus owner resolved by email match against HighLevel user list. Custom fields on the contact record become HighLevel custom fields on the Contact object.

JobNimbus Company maps to HighLevel Company. Company name, address, phone, and industry classification transfer directly. Contacts linked to a primary company in JobNimbus attach to the corresponding HighLevel Company via the contact–company relationship. Multi-contact accounts collapse to one primary company association per contact in HighLevel.

JobNimbus Jobs require a choice: (a) migrate as a HighLevel Custom Object when the job tracks a project with materials and line items, preserving job number, status, primary contact, and trade-specific fields; or (b) migrate as a HighLevel Opportunity if the job represents a sales pipeline stage (e.g., sold job, estimate stage). The choice depends on whether the job lifecycle maps to a sales funnel or an operational project log. We document both options in the pre-migration plan.

JobNimbus Boards define workflow stages for jobs (e.g., New Lead, Scheduled, In Progress, Complete). Each board becomes a HighLevel Pipeline. Board columns map to HighLevel Opportunity stages with stage names and probabilities carried forward. Jobs in 'New Lead' or 'Estimate' columns map to open Opportunity stages; jobs in 'Complete' map to Closed Won.

JobNimbus supports Date, Decimal, Number, and Text custom field types on Contact records. Each custom field requires a corresponding custom field to be created in HighLevel before migration. JobNimbus field types map to HighLevel field types: Number → Number, Decimal → Decimal, Date → Date, Text → Text. We deliver a field creation checklist as part of the migration plan so HighLevel schema is ready before data loads.

Trade-specific job fields (Xactimate code, roof type, material, labor hours) migrate as HighLevel custom fields on the target object (Custom Object or Opportunity, depending on the mapping choice in Step 3). Boolean and picklist fields in JobNimbus map to HighLevel Checkbox and Dropdown fields. We preserve the exact field label from JobNimbus in the HighLevel field name.

JobNimbus Engage stores SMS conversations threaded to contact records. HighLevel has its own Conversations feature tied to its SMS gateway. We export Engage message content as an attachment on the contact record in HighLevel for reference. Full conversation threading must be rebuilt in HighLevel's Conversations inbox using your own SMS number setup.

JobNimbus Automations (action limits 10–100/mo by plan) do not export in a transferable format. We extract the automation definitions — trigger events, conditions, and action sequences — and deliver them as a structured document your HighLevel admin can use to rebuild equivalent Workflows in the HighLevel Workflow builder. No automation logic is transferred automatically.

JobNimbus Estimates created via SumoQuote contain line items, materials, and pricing. HighLevel has no native estimating module. We migrate the estimate as a linked Custom Object record (line items stored in a JSON or multi-line text field for reference) and as an Opportunity with the estimate total in the Amount field. Rebuilt proposals must be created in HighLevel using the Opportunities and custom fields model.

JobNimbus's QuickBooks Desktop and Online integration settings are destination-side configuration with no export capability. Invoice and payment records that synced to QuickBooks are migrated as data but the QuickBooks connection must be re-established and mapped in HighLevel's native integration settings. FlitStack does not migrate accounting sync rules.

JobNimbus file attachments (photos, contracts, Xactimate estimates) stored on Job and Contact records are downloaded and re-uploaded to HighLevel Files, attached to the corresponding Contact or Custom Object record. File size limits of 25MB per file apply. Inline images in JobNimbus notes are downloaded and re-hosted as HighLevel file attachments.

JobNimbus Supplier records and material line items do not have a native HighLevel equivalent. We migrate Suppliers as a HighLevel Custom Object with name, contact info, and material fields. Material line items attached to jobs can be stored as a Custom Object linked to the Job record, or flattened into a text/notes field for reference. Rebuilt material catalogs require manual setup in HighLevel.