Migrate from JobTread to Freshsales

JobTread Customers map directly to Freshsales Leads. Name, email, phone, address, and any custom properties migrate as Lead fields by name and type. A JobTread Customer record that has associated Jobs carries those Job associations into Freshsales Deals owned by the same Lead record, preserving the customer-to-project relationship through migration.

JobTread Customer Contacts map to Freshsales Contacts on a one-to-one basis. Each Contact links to a parent Account representing the Company the contact belongs to in JobTread. Custom fields on the contact migrate to Freshsales Contact custom fields, preserving field types and values during the transfer.

JobTread Companies (business entities attached to customers or vendors) map to Freshsales Accounts. Company name, domain/website, address, industry, employee count, and revenue fields map directly to their Account equivalents. Company-specific custom fields migrate as Freshsales Account custom fields, maintaining all custom data associated with each business entity.

JobTread's core Job object maps to a Freshsales Deal. Job name becomes Deal name; Job close date becomes Expected Close; Job status (Draft, Pending Approval, Approved, In Progress, Completed) maps to Freshsales pipeline stage values. Construction-specific metadata (budget, change orders, selections) requires pre-planned custom fields on the Deal.

JobTread's single job-status pipeline maps to one Freshsales Deal Pipeline. Each JobTread status value (Draft, Pending Approval, Approved, In Progress, Completed) maps to a corresponding Freshsales stage name. Stage probability values are assigned based on Freshsales defaults and can be adjusted per pipeline.

JobTread custom fields migrate as Freshsales custom fields on the equivalent object (Lead, Contact, Account, Deal). Field type is preserved: picklist stays picklist, date stays date, phone stays phone. Multi-value picklists in JobTread are concatenated with semicolons into Freshsales text fields.

JobTread Vendors map to Freshsales Accounts with a Vendor_Type__c custom field flag set to true to distinguish them from customer Accounts. Vendor name, email, phone, address, and custom fields migrate as Account fields. Vendor Contacts map to Contacts linked to the vendor Account, maintaining the vendor-to-contact relationship.

JobTread Vendor Contacts map to Freshsales Contacts linked to the vendor Account. Name, email, phone, and custom fields migrate directly. The Primary contact flag from JobTread migrates as a custom field on the Contact record, preserving the designation of primary vendor contacts through the migration process.

JobTread Cost Items from the Cost Catalog migrate as Freshsales Products. Name, unit price, quantity, and SKU (if set) map directly. Cost Group membership is preserved as a Product custom field for reporting. Job-specific selections also map to Products with the Job linked as a Deal.

JobTread Tasks and Reminders migrate as Freshsales Tasks with full fidelity. Subject, due date, assigned user (resolved by email match), status, and priority carry over. Open vs. completed status is preserved through migration. Tasks tied to a specific Job link to the corresponding Deal, maintaining the relationship between task context and the project record.

JobTread Notes migrate as Freshsales Notes with the original body text preserved. Notes attached to a Job link to the corresponding Deal record. Note create date is preserved as a custom datetime field since Freshsales sets its own created date at migration time.

Tags from JobTread migrate to Freshsales Tags on the equivalent record. A tag applied to a Customer (Lead), Contact, or Job (Deal) is reapplied to the corresponding Freshsales record. Tag history is not preserved — only the current tag set per record.

JobTread Change Orders are construction-specific with approval workflows and line-item structures. Freshsales has no native change-order object. We migrate change order metadata (description, amount, status) as custom fields on the Deal. Full line-item detail migrates as Products linked to the Deal. Approval chain logic must be rebuilt in Freshsales Workflows.

JobTread Selections let customers choose options on a proposal. Freshsales has no native selection mechanism. Options migrate as Products; the selected option(s) per Job/Deal are stored in a Deal custom field. Customer-facing selection UX must be rebuilt as a Freshsales Customer Portal feature or external tool.

JobTread file attachments on Customers, Jobs, and Vendors migrate to Freshsales Files and Attachments linked to the equivalent record. Files are re-uploaded to Freshsales storage. Inline images embedded in notes are downloaded and rehosted within Freshsales. File size limits apply based on your Freshsales subscription plan tier.