Migrate from JobTread to Pipedrive

JobTread Customers store both contact information and company details within a single record. FlitStack splits this into a Pipedrive Person record (containing name, email, and phone) and an Organization record (holding company name, address, and domain). The Organization is always created first in Pipedrive; the Person record is then created and linked to the Organization via the org_id field to establish the proper relationship between contact and company data.

JobTread Jobs map directly to Pipedrive Deals as the primary record translation. The job name becomes the deal title, and the job status maps to an appropriate Pipedrive pipeline stage value based on the job's current state. JobTread's internal job ID is stored as a custom field (jobtread_id__c) on the Pipedrive Deal for traceability, audit purposes, and to support delta-run de-duplication logic.

JobTread phases such as Prospecting, Design, Under Construction, and Completed are mapped value-by-value to corresponding Pipedrive pipeline stages. Each phase name in JobTread receives a direct translation to a Pipedrive stage. Phase order and probability weight settings are reapplied from the Pipedrive side after the mapping is configured to ensure pipeline forecasting accuracy is preserved.

JobTread Estimates are budget documents rather than transactional records, so they do not become separate Pipedrive Deals. We extract the total estimate amount and store it as a custom currency field (Original_Estimate__c) on the corresponding Pipedrive Deal. All line-item details are preserved as a JSON blob in a separate long-text custom field (Estimate_LineItems__c) for future reference without cluttering the deal interface.

JobTread cost catalog entries including materials, labor, and markup line items per job have no native equivalent in Pipedrive's standard object model. These entries become custom fields on the Deal record. Cost group names from JobTread are used as field labels; individual line-item amounts are serialized into a custom text field (Cost_Catalog__c). For catalogs exceeding 20+ items per job, we recommend a separate spreadsheet export linked by job ID for easier reference.

JobTread job budget totals migrate as a custom currency field (Budget_Total__c) on the Pipedrive Deal to preserve financial context. When JobTread exports include budget-versus-actual variance data, that metric is stored separately as Budget_Variance__c to support post-migration financial analysis and reporting against original budget projections.

JobTread Vendors are mapped to Pipedrive Organizations representing the vendor company with all associated contact details. An optional Person record is created for the primary vendor contact when contact information exists in JobTread. Vendor trade type (electrical, plumbing, HVAC, or other categories) is preserved as a custom picklist field (Vendor_Type__c) on the Organization to maintain categorization.

JobTread file attachments including photos, PDFs, and signed documents are downloaded during the migration process and re-uploaded to the corresponding Pipedrive Deal via Pipedrive's Files API. Original filenames and original upload timestamps are preserved during re-upload. The per-file size limit in Pipedrive is 100MB; any files exceeding this threshold are flagged and included in a separate download package.

JobTread team member assignments are mapped to Pipedrive users by matching email addresses. Unmatched owners are flagged before migration begins so the team can either invite them to Pipedrive first or assign their records to a designated fallback user. Job-level permission assignments from JobTread are not preserved as Pipedrive has a separate permission model based on visibility groups and item visibility settings.

JobTread change orders representing scope or budget changes that occur after contract signing are stored as a custom text field (Change_Orders__c) on the Pipedrive Deal. Each change order entry includes the change description, amount delta, and approval status if that data is available in JobTread's export. This preserves the full change order history for project financial review.

JobTread selections representing client-picked finishes, fixtures, and materials have no native Pipedrive equivalent. These selection sets are serialized into a custom long-text field (Client_Selections__c) on each Deal. If selections were tracked as separate line items with associated costs in JobTread, those amounts are rolled into the primary deal value to maintain accurate revenue projections.

JobTread workflows including phase-change triggers, reminder actions, and automatic task creation do not migrate to Pipedrive and must be rebuilt in Pipedrive's Automation builder. FlitStack exports your complete JobTread workflow definitions as a structured JSON reference file that your Pipedrive administrator can use as a rebuild guide to reconstruct equivalent automation logic in Pipedrive.

JobTread's native QuickBooks synchronization does not have a direct equivalent in Pipedrive's data model. Invoices and payments tracked in JobTread are preserved as deal notes and custom fields on the migrated records. A separate accounting integration such as QuickBooks Online, Xero, or FreshBooks must be connected in Pipedrive after migration to resume financial sync workflows.