Migrate your Corteza CRM data

Leads are a first-class module with standard fields (first name, last name, email, phone, rating) and a conversion workflow that creates Accounts, Contacts, and Opportunities. We migrate lead records with their assigned owner, status, and related notes and tasks intact.

Accounts represent companies and are the parent entity for Contacts. The module supports industry classification, address data, social media URLs, and related records lists. We preserve the account-contact relationship by sequencing imports so parent records exist before child records are created.

Contacts represent individual people linked to Accounts. Standard fields include first name, last name, email, phone, job title, and a relation to the parent Account. We map the contact-account relationship using the foreign key stored in each contact record.

Opportunities track sales deals with stage, amount, probability, and close date. Each opportunity can relate to an Account and multiple Contacts via OpportunityContactRole records. We preserve opportunity-account and opportunity-contact linkages by importing roles after opportunity records are committed.

Campaigns group marketing activities and track campaign member responses. CampaignMember records link Contacts and Leads to a Campaign. We migrate campaigns with their member associations, though activity history per member may require supplemental import.

Cases track customer support issues with status, priority, origin, and resolution fields. Cases can link to Accounts and Contacts. We map case-account and case-contact relationships by maintaining the foreign key references during import.

Contracts store agreement details with line items (ContractLineItem), related Accounts, and Contact roles (ContractContactRole). Contract data including terms and pricing is migrated as structured records with their relationship chain preserved.

Tasks can be standalone or related to any parent record (Lead, Account, Contact, Opportunity). Each task has status, due date, assignee, and optional description. We migrate tasks independently and then link them to their parent records using the stored relation metadata.

Corteza's low-code environment lets administrators create entirely custom modules beyond the standard CRM set. These custom modules may have non-standard field types, custom validation rules, or non-standard naming. We audit custom module schema before migration and map fields individually to their destination equivalents.

File fields store attachments per module. The export path handles individual file records, but bulk attachment export with folder structure intact may require supplemental handling. We confirm file storage path accessibility during scoping and include file metadata in the migration package.

Corteza workflows automate CRM operations (such as lead conversion, quote creation, and task assignment) but can break after system restore or upgrade. Workflow linkage to automation buttons is not always preserved across namespace import. We document workflow definitions during scoping and re-create or re-link them post-import.

Quotes represent pricing proposals linked to Opportunities with line items (QuoteLineItem), pricing (via Pricebook and PricebookEntry), and related Products. We migrate quote records with their full line-item hierarchy and product pricing references preserved.

Events represent calendar items (meetings, calls) related to any CRM record. Each event stores datetime, duration, organizer, and attendee references. We migrate events with their parent-record linkage intact and normalize datetime formats to the target system's timezone expectations.

Products define items available for sale with pricing information stored in PricebookEntry records linked to Pricebooks. We migrate the product catalog, pricebook structure, and pricing entries as a coordinated set to preserve quote functionality.

Corteza organizes CRM content into namespaces that can be exported and imported between instances. The namespace export path has documented edge cases: pages referencing deleted modules prevent export. We audit namespace integrity before export and clean up orphaned page references to ensure a clean migration package.