Migrate from Jarvis CRM to HubSpot

Jarvis person contacts map directly to HubSpot contacts. HubSpot stores contact properties as flat key-value pairs. Email, phone, address, and name fields transfer 1:1. Owner assignment resolves via email matching against HubSpot user records. During migration, any custom contact fields in Jarvis are created as HubSpot custom properties, and duplicate detection flags are applied based on email uniqueness.

Jarvis business records map to HubSpot companies. Company name, domain, industry, employee count, and revenue fields map to HubSpot company properties. Parent-child hierarchies in Jarvis require HubSpot custom fields for multi-level company relationships. Address and phone fields also transfer directly. If multiple Jarvis records share the same domain, FlitStack merges them into a single HubSpot company record to avoid duplication.

Jarvis deal or opportunity records map to HubSpot deals. Deal name, amount, stage, and close date transfer directly. HubSpot deal pipelines must be pre-configured with matching stage names before migration runs. Custom deal fields in Jarvis are created as HubSpot custom properties, and the owner field is resolved by email matching to ensure the correct HubSpot user is assigned.

Jarvis pipelines containing deal stages map to HubSpot deal pipelines. Each Jarvis pipeline becomes a separate HubSpot pipeline. Stage probability values do not transfer automatically and are re-applied during HubSpot configuration. You will define stage probabilities in HubSpot's pipeline settings, and FlitStack will remind you to set these before the migration to ensure accurate forecasting.

Jarvis tasks and activity records migrate as HubSpot engagement tasks. Subject, body, due date, and completion status transfer. Original timestamps and owner assignments are preserved. Call and email activities in Jarvis map to HubSpot engagement types. If Jarvis contains custom task types, FlitStack creates custom property flags in HubSpot to preserve those distinctions, and any attachments on tasks are exported as files for re‑attachment.

Jarvis notes migrate to HubSpot engagement notes attached to the relevant contact, company, or deal record. Rich-text formatting in Jarvis notes is preserved where HubSpot's note format allows. If a note includes embedded images or file references, FlitStack exports them as separate files and re‑links them to the HubSpot note record, ensuring no content is lost.

Jarvis project management records have no direct HubSpot equivalent. Projects migrate as a HubSpot custom object if your HubSpot tier supports custom objects, or as tickets in the support pipeline. Project status, milestones, and Gantt data become custom properties. FlitStack will provide a schema mapping sheet that lists each custom property name, data type, and any pick‑list options required to recreate the project structure in HubSpot.

Jarvis product and service records map to HubSpot products. Name, price, SKU, and description fields transfer directly. HubSpot products attach to deals via line items; Jarvis deal-to-product associations map accordingly. If a product has multiple pricing tiers in Jarvis, FlitStack creates separate HubSpot product records for each tier, linking them to the same base product via a custom parent‑product property.

Jarvis vendor management records (POs, bills, payments) have no HubSpot equivalent. Vendors migrate as HubSpot companies with a custom Vendor_Type__c pick-list field. Financial records (POs, bills) are exported as CSV for archival; they do not map to HubSpot objects. The Vendor_Type__c field uses values such as 'Supplier', 'Contractor', or 'Partner' to differentiate vendor roles, and you can expand the pick‑list as needed after migration.

Jarvis time tracking records (timecards, job time) have no HubSpot equivalent. These migrate as a custom object with employee name, date, hours, and project reference. Timesheet data does not affect HubSpot reporting natively and is maintained for historical reference. You can build custom reports in HubSpot that pull time entry data via the custom object, or export the data to analytics tools for deeper cost analysis.

Jarvis file attachments associated with contacts, companies, or deals re-upload to HubSpot Files. Files attach to the corresponding HubSpot record. File size limits of HubSpot apply (25MB per file for most tiers). If any file exceeds the size limit, FlitStack splits it into smaller chunks and reassembles them in HubSpot, preserving the original file name and metadata.

Jarvis users resolve to HubSpot owners by email address. Unmatched Jarvis users are flagged before migration; the team either creates HubSpot user accounts first or assigns records to a fallback HubSpot owner. FlitStack provides a pre‑migration owner worksheet listing each Jarvis user, their email, and the recommended HubSpot owner, so you can provision accounts ahead of the cutover.