Migrate from Corteza CRM to HubSpot

Corteza Account maps directly to HubSpot Company. Fields including name, industry, website, employee count, and annual revenue map to their HubSpot equivalents. Parent-child company hierarchies in Corteza (where one account is the parent of another) map to HubSpot's Associated Companies field. Multi-account associations on a single contact require a primary company assignment with secondary associations noted.

Corteza Contact maps 1:1 to HubSpot Contact. All standard fields — first name, last name, email, phone, job title, address — map to HubSpot native properties. When a Corteza Contact is linked to multiple Accounts, the most-recently-modified Account is set as the primary HubSpot company association, and secondary associations are captured as a property note for manual review.

Corteza Lead conversion produces Account, Contact, and Opportunity in a single atomic operation. When migrating without converting, all Lead fields map to HubSpot Contact properties. The original Corteza Lead ID is preserved as a custom property (corteza_lead_id) so teams can reference the source record. Lead status values map to HubSpot's lifecycle_stage property via value mapping.

Corteza Opportunity maps to HubSpot Deal. The opportunity name, amount, expected close date, and probability map directly. The pipeline and stage stored in Opportunity fields map to HubSpot Deal pipeline and dealstage properties. If multiple Corteza pipelines exist, each maps to a separate HubSpot pipeline with stage pick-list values scoped per pipeline.

Corteza OpportunityContactRole defines which contacts are associated with an opportunity and in what role (such as Decision Maker or Influencer). These associations migrate as HubSpot deal-contact associations. Role labels that have no HubSpot equivalent are stored as a custom property on the deal-contact association for reference.

Corteza Task maps to HubSpot Task. Subject, body, due date, owner, and completion status migrate. Original timestamps (created_at, updated_at) are preserved as HubSpot activity timestamps. Task type distinguishes calls, emails, and general to-dos — this maps to HubSpot's task type property.

Corteza Event maps to HubSpot Meeting. Subject, body, start time, end time, owner, and linked contact/lead record migrate. Timezone handling in Corteza event records is preserved by storing the original timezone as a property note. Events without an assigned owner default to the migration operator for review.

Corteza Note maps to HubSpot Note. Body content migrates. If Corteza notes use rich text, the HTML content is converted to plain text for HubSpot compatibility. Notes are associated to their parent record (contact, company, or deal) using HubSpot's association model. Individual notes that span multiple Corteza records are split and linked to each parent.

Corteza file attachments do not have a direct HubSpot equivalent object. Files are downloaded from Corteza, re-uploaded to HubSpot's file manager, and attached to the corresponding CRM record by ID. Large files (over HubSpot's size limits per tier) are flagged for manual re-upload or alternative storage. Corteza file view modes (gallery, list, single image) do not translate — files are re-associated by record.

Corteza custom modules (created in the admin panel under Modules) map to HubSpot custom objects if they define required fields and a primary key. Modules without required fields or with unsupported field types (such as Record reference to an unmigrated module) require custom object creation in HubSpot or field consolidation into existing objects. Custom module associations that use N:N relationships map to HubSpot's association API.

Corteza Case maps to HubSpot Ticket. Subject, description, status, priority, owner, and related contact/company associations migrate. Case custom fields map to HubSpot custom ticket properties. If Corteza Cases use multiple pipelines with different stages, each maps to a separate HubSpot ticket pipeline with scoped stage values.

Corteza Campaign records (module type) have no direct HubSpot equivalent. Campaign names and descriptions are preserved as a custom property on associated contacts for reference. HubSpot's native Campaigns object serves a different purpose (marketing campaign tracking) and requires separate setup.