Migrate from Wice CRM to HighLevel

Wice Organizations map to GoHighLevel Companies. We export Organizations first and use the Organization ID as a lookup key stored in a temporary field so that when Contacts are imported, their Organization linkage is resolved to the correct GoHighLevel Company record. Wice Organization custom fields map to GoHighLevel Company custom fields by name and type match during the import phase.

Wice Contacts map to GoHighLevel Contacts. The Organization-to-Contact relationship migrates via the lookup key we stored during Organization export. Standard fields (first name, last name, email, phone, address) map directly. Custom fields on Contact migrate as GoHighLevel Contact custom fields; any picklist-style custom fields require value translation if the destination picklist values differ from the source.

Wice Deals map to GoHighLevel Opportunities. Deal stage maps to GoHighLevel pipeline stage using the stage-mapping table generated during discovery. Deal value, expected close date, owner assignment, and linked Organization all migrate. We capture the raw Wice stage name in a custom field wice_original_stage__c for audit and reconciliation after migration.

Wice allows full customization of pipeline stages per installation. We generate a stage-mapping table during discovery that pairs each Wice stage name with a specific GoHighLevel pipeline stage. Probability values from Wice map to GoHighLevel stage probability percentages. The customer approves the stage map before any Deal records are written.

Wice Projects contain tasks and custom fields that do not map directly to a standard GoHighLevel object. We map Projects to GoHighLevel Opportunities if the customer's project workflow aligns with a sales pipeline, or we map them to a GoHighLevel Custom Object if the project is operational rather than sales-oriented. The customer's use of the Project object drives the mapping decision during discovery.

Wice Tasks exist standalone linked to Contacts or Deals, and also inside Projects. We export both contexts and create GoHighLevel Tasks linked to the migrated Contact or Opportunity. Task status, due date, assignee, and description migrate. Tasks that were orphaned in Wice (no parent) are flagged for customer review before import.

Wice Notes attached to Contacts, Organizations, and Deals migrate to GoHighLevel Notes linked to the equivalent Contact or Opportunity. Note content migrates as plain text. Any formatting (bold, lists) is simplified to plain text per GoHighLevel's note model. Source-object linkage is preserved so notes appear in the correct contact or opportunity timeline.

Wice Tickets are support records that do not map to a native GoHighLevel object. We discuss with the customer whether to migrate tickets as Opportunities in a support pipeline, as notes on the related Contact or Company, or to omit tickets from migration if they will use a dedicated helpdesk tool. Custom ticket fields map to GoHighLevel Opportunity custom fields if the support pipeline approach is chosen.

Wice uses a category system for contact classification that does not map 1:1 to any GoHighLevel object. We export category assignments as a comma-separated text value and either map them to GoHighLevel Tags (created dynamically during import) or store them in a custom Contact field. The customer chooses the approach during scoping.

Wice custom fields on Contacts, Organizations, and Deals migrate to GoHighLevel custom fields of equivalent type. Text fields map to text, date fields to date, picklist fields to dropdown or multi-select depending on GoHighLevel's field model. Any Wice picklist values that do not exist in GoHighLevel are flagged for the customer to create in the destination before migration proceeds.