Migrate your Jobnimbus data

Contacts are the primary CRM records in JobNimbus, storing customer information, addresses, lead sources, and custom fields. Contacts can be exported via Custom Reports to CSV. We map contacts 1:1, preserving all standard fields and any custom field values attached to the contact record.

Jobs represent projects and contain the core work data: status, assigned contacts, financials, photos, and notes. Job V2 introduced a streamlined workflow structure that differs from the legacy Contact-as-project model. We map Jobs directly but flag which records used Jobs V2 vs legacy Contacts-as-jobs to ensure workflow continuity in the destination.

Boards are Kanban-style pipeline views tied to Job workflows. Limits apply by tier: Essentials allows 3 max, Pro allows 5 max, Premium and Enterprise allow unlimited. We preserve the board structure and stage assignments but note the tier ceiling for reconstruction in the destination platform.

JobNimbus generates estimates and proposals linked to Jobs and Contacts. The legacy Smart Estimates product is being retired in favor of current proposal tools. We map all estimate records including line items, quantities, and pricing, flagging any records still in the legacy system format.

Invoices are linked to Jobs and track payment status, amounts, and QuickBooks sync state. We preserve invoice records and their line items. Voided or cancelled invoices are flagged separately since they may not be relevant to migrate depending on the destination's handling of historical records.

Payments record collections via JobNimbus Payments, including credit card transactions and eCheck history. The Payments module has a $20 boarding fee and percentage-based transaction fees in the source system. We map payment records but note that payment gateway configuration does not transfer and must be re-established in the destination.

Automations are workflow rules triggered by events. Limits are strict by tier: Essentials caps at 10/month, Pro at 30/month, Premium at 100/month, Enterprise gets unlimited. We audit the automation inventory and map each rule's trigger, conditions, and actions. Complex automations involving QuickBooks sync require manual rebuild in the destination.

Custom fields can be created on Contacts and Jobs with types: Date, Decimal, Number, and Text. Once created, the field type cannot be changed. We map all custom field definitions and values, but the destination must support the same field type schema. Custom fields specific to contacts must be recreated under Jobs when migrating V1-style accounts.

Suppliers are vendor records used in JobNimbus for materials sourcing. We map supplier records including contact information and any associated data. These map cleanly to vendor objects in most destination platforms.

JobNimbus stores attachments on Contact and Job records. The official export path requires downloading documents individually from client records, which is not a bulk operation. We can extract attachment metadata and URLs, but file downloads may require a separate batch process depending on volume.

Custom Reports can be exported to CSV or Excel. The report definitions themselves (field selections, filters, groupings) do not transfer. We extract the underlying data from the reports and map it to the destination schema, then note which report definitions need manual reconstruction.

Email, document, and financial templates reference contact and job merge fields. Templates used from Job records reference JobPrimaryContact variables rather than standard Contact variables, a distinction introduced with Jobs V2. We map template content and flag variable references that need updating in the destination system.