Migrate from Corteza CRM to HighLevel

Corteza Leads are a first-class module with a separate conversion workflow. GoHighLevel does not have a separate Lead object; unqualified prospects are stored as Contacts. We migrate Corteza Leads as GoHighLevel Contacts and tag them with a lead_source custom field (value: 'Corteza Lead') so the customer's admin can identify converted versus non-converted records. If the Corteza instance used lead scoring, we map the score to a GoHighLevel Contact custom field. The Corteza conversion workflow (which creates Account, Contact, and Opportunity) is not migrated as code; we document the conversion logic for the admin to implement in GoHighLevel Automations.

Corteza Accounts are standalone company records with industry, address, and social media fields that serve as the parent entity for Contacts. GoHighLevel has no explicit Account object; company information is stored as Location records attached to the primary Contact. We migrate each Corteza Account as a GoHighLevel Contact record representing the company (using the company name as the Contact name) with a Location record containing the address and industry. The original Contact records previously linked to the Account migrate as additional Contacts under the same Location.

Corteza Contacts represent individual people linked to a parent Account. We migrate these as GoHighLevel Contacts with the contact-account relationship preserved via Location linkage (the merged Account above). Standard fields (first name, last name, email, phone, job title) map directly to GoHighLevel Contact standard fields. Custom Contact fields from Corteza map to GoHighLevel Contact custom fields (see custom module note).

Corteza Opportunities track sales deals with stage, amount, probability, and close date linked to an Account. We map these to GoHighLevel Opportunities, using the merged Account Contact as the primary contact on the Opportunity. Corteza dealstage maps to a GoHighLevel Pipeline stage. We configure the GoHighLevel pipeline stages to match the Corteza stage names and probabilities before migration. Deal amount and expected close date migrate as Opportunity monetary_amount and expected_close fields.

Corteza Campaigns group marketing activities and track CampaignMember responses linking Contacts and Leads. GoHighLevel does not have a native Campaign object; campaign membership is tracked via Tags, custom fields, and Pipeline stages. We migrate active Campaigns as GoHighLevel Tags on the relevant Contacts and Opportunities, preserving the campaign name as the tag value. CampaignMember status (sent, responded, bounced) migrates as a Contact custom field if the customer has active campaign tracking requirements.

Corteza Cases track customer support issues with status, priority, origin, and resolution linked to Accounts and Contacts. GoHighLevel's CRM is not a full service desk; support cases are typically tracked via Opportunities with status tags or via the built-in Tasks and Appointments. We migrate Cases as GoHighLevel Opportunities with a 'Support Case' pipeline or as tagged Tasks, depending on the customer's preferred tracking method chosen during scoping. Case priority and resolution details migrate as Opportunity custom fields.

Corteza Tasks can be standalone or related to any parent record (Lead, Account, Contact, Opportunity). Each task has status, due date, assignee, and description. We migrate Tasks as GoHighLevel Tasks with status (open, complete), due date, and description preserved. Task assignment migrates by resolving the Corteza assignee to a GoHighLevel User by email match. Parent-record linkage migrates via GoHighLevel's Opportunity and Contact lookup fields.

Corteza Events represent calendar items (meetings, calls) related to any CRM record, storing datetime, duration, organizer, and attendee references. We migrate Events as GoHighLevel Appointments with start time, end time, location, and description preserved. Attendee references migrate as related Contact lookups. Note that GoHighLevel's Appointment scheduling (Calendar feature) is separate from migrated Event records; we migrate the calendar content but do not configure GoHighLevel's Availability settings.

Corteza's low-code module builder can create entirely custom modules beyond the standard CRM set. Personal attributes (lead type, birthday, preferred contact method, referral source) that were stored in Corteza custom modules map to GoHighLevel Contact custom fields. We design the Contact custom field schema during scoping: field types are matched (text, number, date, dropdown) and fields are created in GoHighLevel before migration. Note: GoHighLevel Contact custom fields cannot be switched to Opportunity custom fields after creation, so the field partitioning decision is made during scoping.

Corteza custom modules storing deal-specific attributes (budget range, urgency, timeline to close, property type) map to GoHighLevel Opportunity custom fields. We create the GoHighLevel Opportunity custom fields before migration, matching Corteza field types to GoHighLevel supported types (text, number, date, dropdown, multi-select). The Opportunity custom fields appear within the Opportunity record and are used in pipeline views and Opportunity-level automations.

Corteza file fields store attachments per module. GoHighLevel supports file attachments on Contacts and Opportunities via its native file storage. We extract files from Corteza module records and attach them to the corresponding GoHighLevel Contact or Opportunity records. Folder structure from Corteza does not map directly to GoHighLevel's flat file organization; files are attached without the original folder hierarchy. We flag any file attachment exceeding GoHighLevel's size limits for the customer's admin to handle separately.