Migrate from Upvise to HighLevel

Upvise Contact records transfer directly to HighLevel Contacts using field-by-field mapping. Standard fields including name, email address, phone number, physical address, and any custom fields migrate as matching HighLevel custom fields. Upvise contacts may include a role or title property that does not have a direct HighLevel equivalent — we preserve this as a custom pick-list field named Role__c. The original contact creation timestamp transfers as a custom date field for reporting continuity.

Upvise Company records map one-to-one to HighLevel Company records. All standard fields including company name, website domain, industry classification, phone, full address components, employee count, and annual revenue transfer directly. Any Upvise company properties not covered by HighLevel's standard Company fields are captured as HighLevel custom fields on the Company object, maintaining full data fidelity from the source system.

Upvise Projects do not have a direct HighLevel equivalent. We create a HighLevel Custom Object named 'Project' with a field schema matching the Upvise structure. Project status, priority level, assigned user, and due date migrate as custom fields. Related Contacts and Companies are stored as lookup fields on the Custom Object, linking back to the migrated HighLevel records by email-matched IDs.

Upvise form submissions are records scoped to a specific form definition. We map these to a HighLevel Custom Object with fields capturing submitted values, submission timestamp, and a contact lookup linking to the submitting Contact record via email resolution. The original form structure is documented in a separate specification file for manual recreation in HighLevel's Forms module.

Upvise Jobs app records map to a HighLevel Custom Object. Job status, assigned technician, service location, and line-item totals transfer as custom fields on the Job Custom Object. Historical job data including creation and completion timestamps is preserved in the migrated records. Job scheduling logic and calendar-based availability checks require rebuild using HighLevel's Calendar integration and Workflow automation tools post-migration.

Upvise custom fields exist per object (Contact custom fields, Company custom fields, etc.). HighLevel supports custom fields natively on Contacts, Companies, Opportunities, and Custom Objects. We create matching custom fields in HighLevel, applying type-aware transformations: Upvise text fields map to HighLevel text fields, Upvise date fields map to HighLevel date fields, and Upvise pick-list fields map to HighLevel pick-list fields with value correspondence.

Upvise user accounts map to HighLevel users by matching email addresses. Active Upvise users who have login credentials become HighLevel users with the same email. Users in Upvise who lack email-based login access cannot be provisioned in HighLevel and their ownership on records is reassigned to a designated fallback user during migration with notes for administrator review.

Upvise file attachments associated with Contacts, Companies, or Projects are downloaded from Upvise and re-uploaded to HighLevel's Cloud Storage. Each file is then linked back to its originating record in HighLevel. Large file attachments exceeding 25MB are flagged separately with the original Upvise-hosted URL preserved as a custom text field on the record for manual retrieval and re-upload.

Upvise notes attached to Contact or Company records migrate as HighLevel Contact Notes with the original creation date, author information, and note body preserved. Rich-text formatting is maintained where the source format is compatible. Notes containing complex HTML markup are simplified to plain text with a reference link back to the original Upvise record.

Upvise invoice and quote records have no direct HighLevel equivalent. We map them to a Custom Object named 'Invoice' with custom fields for line items, totals, currency, and status. Links to payment processors like Stripe and PayPal cannot be preserved and require rebuild in HighLevel Payments. PDF attachments for invoices are preserved as HighLevel Files linked to the corresponding Invoice Custom Object record.