Migrate from Jarvis CRM to HighLevel

Jarvis Contact records extract via FileMaker export scripts or direct table access using the contact's primary key. We preserve the contact ID as an external reference field for relationship audit. Standard fields (First Name, Last Name, Email, Phone, Address) map directly. Any custom contact properties identified during the schema audit migrate to GoHighLevel custom fields scoped to the Contact object. Owner assignment maps to GoHighLevel User by email match.

Jarvis Company records map to GoHighLevel Companies. Company ID is preserved as an external reference. We resolve the Account-Contact relationship at import time using the foreign key stored in the FileMaker table rather than name-matching. Any custom company properties migrate to GoHighLevel custom fields on the Company object.

Jarvis Opportunity records map to GoHighLevel Opportunities. Pipeline stage names from Jarvis (which vary per deployment) map to GoHighLevel pipeline stage values that we configure before migration. Deal value, close date, owner assignment, and associated contacts carry over directly. We use GoHighLevel's Opportunities API with batch chunking to handle volumes over 500 records.

Each distinct sales stage sequence in Jarvis becomes a GoHighLevel pipeline. We configure the pipeline stages, stage order, and stage probabilities before Opportunity import. Stage names from the source FileMaker instance are recreated verbatim so that historical pipeline reporting reflects the original labels.

Jarvis Project records (Gantt, templates, task structures) do not have a native equivalent in GoHighLevel's standard object model. We flag Projects as a migration decision item: customers may choose to create a GoHighLevel Custom Object named Projects with custom fields (Project Name, Start Date, End Date, Status, Assignee) or to link Projects as Opportunities with a custom field indicating project type. GoHighLevel limits Custom Objects to 10 per sub-account. We identify which approach fits the customer's workflow during scoping.

Jarvis task flows and activity records (follow-ups, assignments, activity timestamps) map to GoHighLevel Tasks. Activity type (call, meeting, note, general task) maps to GoHighLevel's Task Category or custom fields. Owner assignment migrates by resolving the Jarvis user's email to a GoHighLevel User. Activity dates and descriptions preserve. The exact schema depends on how the deployment has structured activities in FileMaker, which we identify during the schema audit.

Jarvis user records and record-level ownership extract from FileMaker ACL and ownership fields. We match Jarvis users to GoHighLevel Users by email address. Any Jarvis owner without a matching GoHighLevel User goes to a reconciliation queue for the customer's admin to provision before record import. We do not provision GoHighLevel users; that is a permission the customer's admin controls.

Every Jarvis deployment has custom fields unique to its FileMaker schema. During the schema audit we identify every custom field and classify it by object (Contact, Company, Opportunity). We pre-create the corresponding GoHighLevel custom fields before any data import. Fields with no equivalent in GoHighLevel are flagged as unmapped and documented for the customer's admin to review.

Jarvis time tracking records (billable and non-billable hours linked to projects, contacts, or vendors) have no direct GoHighLevel equivalent. If the customer needs to preserve time data, we create a Custom Object named Time Entries with fields for Date, Hours, Billable flag, and linked Contact or Project. If the customer does not need time tracking in GoHighLevel, we export the data and deliver it as a structured CSV for reference. Custom Object availability is limited to 10 per sub-account.

Jarvis ERP vendor records and purchase order data have no native GoHighLevel equivalent. If the customer maintains vendor relationships for project billing or service procurement, we map Vendors to a Custom Object named Vendors with fields for Vendor Name, Contact Info, and PO Reference. If the customer does not need vendor management in GoHighLevel, we export the data as a structured CSV. Companies and Vendors are often confused in migration; we clarify the distinction during scoping.