Migrate from Skyward CRM to Twenty CRM

Skyward CRM Contact records map directly to Twenty CRM Person. Standard fields (name, email, phone, address) map to their Twenty equivalents. Contact records are extracted from Skyward after Companies to satisfy the company-person relationship. If the customer uses both Contacts and Leads in Skyward, both map to Person in Twenty, and we preserve the original record type in a custom field for audit and segmentation.

Skyward CRM Lead records map to Twenty CRM Person with a lifecycle indicator preserved as a custom field. If the customer runs separate Contact and Lead lifecycles in Skyward, we map both to Person in Twenty and tag each record with the original object name to preserve the distinction. The email address serves as the dedupe key during import to prevent duplicate Person records.

Skyward CRM Company records map to Twenty CRM Company as the parent entity for Person records. We extract Companies first in the migration sequence to establish foreign-key relationships before importing Person records that reference them. The company domain becomes the Website field and is used as a secondary dedupe key alongside the primary name key.

Skyward CRM Deal records map to Twenty CRM Opportunity with deal value, stage name, and owner preserved. Pipeline stage names in Skyward are fully customizable and must be mapped explicitly to Twenty stage values during migration. We capture the complete Skyward pipeline configuration during scoping, produce a stage-mapping table, and configure Twenty stages before importing any Opportunity records. Closed-won and closed-lost reasons from Skyward custom fields map to custom Opportunity fields in Twenty.

Skyward CRM activity records of all types (calls, emails, meetings, tasks) map to Twenty CRM Task records. We add a type flag to each Task record to preserve the original Skyward activity type (call, email, meeting). Activity timestamps are normalized to UTC during import. Each Task is linked to the resolved Person and Opportunity parent records using Twenty's relationship fields.

Skyward CRM note records map to Twenty CRM Note objects linked to the parent Person, Company, or Opportunity. Rich text content and any attachments migrate as-is. Note creation timestamps are preserved to maintain the activity timeline ordering that sales teams rely on.

Skyward CRM's partner management module stores partner entities with a schema distinct from standard contacts, including partner type, commission structure, and shared lead attribution fields. Partner records do not automatically merge with contacts even when the partner is also a customer. We extract partner records into a separate staging table and map them to Twenty's equivalent objects based on the customer's intended use case: Company if the partner is an organization, Person if an individual, or a custom Partner object if commission and attribution tracking is required.

Skyward CRM supports custom fields on core objects, but the platform does not expose a public metadata API. We discover custom fields during the scoping phase by querying the Skyward CRM admin panel for each object. Each discovered custom field is documented in the field-mapping spreadsheet with its Skyward name, data type, and mapped Twenty field name. Fields must be pre-created in Twenty's data model before CSV import runs; the import creates records, not fields.

Skyward CRM team members assigned as record owners are mapped to Twenty CRM users. We extract the full user roster from Skyward and match by email address against the Twenty destination. Any Skyward owner without a matching Twenty user goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignments on Deals, Contacts, and Activities cannot be resolved until all users are provisioned.

Skyward CRM product catalog entries can be linked to Deals. We extract product records including name, SKU, pricing, and description. Product-to-deal associations require junction-table handling during import to preserve the many-to-many relationship between Opportunity and Product in Twenty.

Skyward CRM supports custom field extensions on core objects, and Twenty CRM supports full custom object creation. If the customer has a custom entity schema beyond standard objects, we create the equivalent custom object in Twenty during the schema design phase, including all custom fields, field types, and lookup relationships to standard objects. The customer's intended use of the custom data determines the relationship model in Twenty.

Skyward CRM Reports are generated from live data and are not stored as independent record sets. Reports do not migrate because they are configuration artifacts rather than data. We do not rebuild reports inside the migration scope. Customers recreate reports in Twenty as Views, which are interactive rather than static. We deliver a written inventory of every Skyward report with its filters and field selection for the customer's admin to rebuild as Twenty Views.