Migrate from Jobnimbus to Freshsales

JobNimbus contacts map 1:1 to Freshsales Contacts. Freshsales requires an AccountId lookup — contacts without a primary company link to a default 'Unassigned' account. Custom fields (Date, Decimal, Number, Text) map to Freshsales custom fields by type. If a contact has multiple phone numbers, the primary goes into phone_number and additional numbers are stored in custom number fields. The JobNimbus contact ID is preserved in a custom field for traceability.

JobNimbus contacts that have never had a sold job can route to Freshsales Leads instead of Contacts. Lead routing is configurable — your team decides which lifecycle state maps to Lead vs Contact in Freshsales lifecycle stage terms. This flexibility lets you align the lead qualification process with your existing sales funnel and prevents unqualified contacts from cluttering the CRM.

JobNimbus companies map to Freshsales Accounts. Address, phone, industry, and employee-count fields map directly. Parent-company hierarchies in JobNimbus map to Freshsales Account hierarchy via the Parent Account field. If a parent company does not yet exist in Freshsales, we create a placeholder Account and link child companies after the parent is present, preserving the original hierarchy.

JobNimbus job records become Freshsales Deals using a Job-as-Deal pattern. The job name maps to Deal name, job amount or estimate total maps to Deal amount, and job workflow status maps to pipeline stage. JobNimbus does not have a native opportunity equivalent — this translation is the closest fit.

JobNimbus boards (columns representing workflow stages) become Freshsales pipeline stages. Each board translates to one pipeline in Freshsales, with each column becoming a stage name. Stage order and probability mapping is configurable per pipeline. We recommend defining win‑loss probabilities for each stage to enable accurate forecasting in Freshsales.

JobNimbus automations (triggers and actions for task creation, email, QuickBooks sync, Engage) do not migrate. Freshsales workflows must be rebuilt manually. We export automation definitions as a reference document for your Freshsales admin to use during setup. The reference includes trigger conditions, action sequences, and any associated QuickBooks event mappings to ease recreation.

JobNimbus estimates with line items map to Freshsales Deal Products attached to the corresponding Deal. Each estimate line becomes a product on the deal. Estimate templates do not transfer — these require Freshsales template rebuild or CPQ add-on. Pricing and quantity data are preserved as product attributes, allowing you to recreate quotes using Freshsales CPQ if needed.

JobNimbus invoices (QuickBooks-synced billing records) have no Freshsales equivalent. Invoice history is preserved as a custom text field on the Deal for reference. Actual invoicing should remain in QuickBooks or be rebuilt via Freshsales invoicing features. This ensures that financial references are accessible during the transition while you maintain a single source of truth for billing.

JobNimbus Engage conversation history does not migrate to Freshsales built-in telephony or chat. Conversations are preserved as custom note attachments on the Contact for reference, but Freshsales does not support a full conversation thread import. You may export Engage data to a CSV for long‑term storage or link to external conversation archives if required.

JobNimbus custom fields on contacts and jobs map to Freshsales custom fields with type-aware mapping: Date → Date, Decimal/Number → Number, Text → Text. Freshsales requires the Custom Fields module (Pro tier or higher) for non-standard field types beyond text.

JobNimbus users and owners are resolved by email match against Freshsales users. Unmatched owners are flagged before migration — your team either creates Freshsales users first or assigns records to a fallback owner. Role and permission sets require Freshsales-side configuration.

JobNimbus file attachments on contacts, companies, and jobs re-upload to Freshsales file attachments on the corresponding record. File size limits apply per Freshsales plan (Growth: 2GB storage, Pro: 5GB per user). We recommend verifying attachment count and total size during scoping to ensure you remain within the allocated storage quota after migration.