Migrate from GleanView to Twenty CRM

GleanView Company records map directly to Twenty Company. The company name, website, industry, address fields, and any custom company properties migrate as flat field values. We deduplicate by company name during import and flag any GleanView company records that share the same domain or name for the customer's admin to resolve before insertion. Twenty's Company object is created before any Person import so that the person-to-company relationship (People associated with a Company) is satisfied at the moment of Person insert. Owner assignments on Companies are resolved by email match against Twenty Users.

GleanView Contact records map to Twenty Person. We map name, email, phone, lifecycle stage, and owner to their Twenty equivalents, and preserve any custom Contact properties as custom fields in Twenty's data model. Deduplication uses email as the primary key. The GleanView Contact-to-Company relationship maps to the Person's company link in Twenty. If the source Contact references a GleanView Company that has not yet been created in Twenty, we hold the Person record in a staging queue and resolve the link after the Companies phase completes.

GleanView Lead records carry lifecycle stage, source, status, and owner. We evaluate each Lead's status to determine whether it maps directly to a Twenty Person record (for early-stage, not-yet-qualified leads) or to an Opportunity with an associated Person (for leads that have progressed to a deal stage in GleanView). The original GleanView lead status is preserved in a custom field on the Twenty Person for audit and reporting continuity. Any custom lead statuses that exist only in GleanView are flagged during scoping for the customer to decide whether to map them to Twenty stage values or archive them.

GleanView Deal records map to Twenty Opportunity. Deal stage, amount, close date, owner, and custom deal fields migrate directly. GleanView does not natively track deal stage history as a timeline; we store the current stage as Opportunity stage in Twenty and preserve the full stage progression (if tracked in custom fields in GleanView) as a custom text field opportunity_stage_history__c for reporting continuity. Owner assignments are resolved by email match against Twenty Users at migration time.

Each GleanView pipeline with its custom stage names and order maps to a Twenty Opportunity pipeline. We create the stages in Twenty in the same ordinal order as GleanView before any Opportunity records are imported, so that the stage values on imported Deals correspond to valid Twenty stage picklist values. If GleanView uses stage-specific actions or automations, we document them in the automation inventory for the customer to rebuild in Twenty's workflow builder.

GleanQuote product catalog entries — including product name, SKU, base price, cost, margin, and attributes — map to Twenty Product records. Formula-driven pricing fields (conditional pricing rules, volume pricing, cost-plus-markup) are flagged as empty or zero in the CSV export and are documented per product in a separate worksheet so the customer can re-enter or re-evaluate pricing in Twenty. Bundle products are flagged as composite products requiring manual bundling in Twenty or a third-party CPQ integration if the deal complexity warrants it.

GleanView Quotes reference Products, Contacts (as customers), and pricing rules. We extract quote headers and line items from the CSV exports and re-create them in Twenty as Opportunities with associated line items. The quote template attachments and PDF history stored in GleanSpaces are not included in the CSV export; we provide a file manifest listing each linked PDF, its associated Quote record, and its URL so the customer can re-upload after migration. Proposal content from GleanQuote templates is documented as a rebuild recommendation rather than migrated.

Engagement records (calls, emails, meetings, tasks, notes) attached to GleanView Contacts or Deals export as activity records. We map call engagements to Twenty Tasks with a call subtype flag, emails to Tasks with an email subtype flag, meetings to Tasks with a meeting subtype flag, and standalone notes to Twenty Notes linked to the parent Person, Company, or Opportunity. Multi-select or rich-text activity notes may require reformatting; we apply a normalization step before insert. Activity batches exceeding 10,000 records are chunked and loaded in sequence with parent-record lookup resolution to avoid referential orphans.

GleanView owner assignments on Contacts, Companies, Deals, and Engagement records are resolved by email match against Twenty User accounts. We extract the complete list of distinct GleanView owners from all migrating records during discovery, cross-reference against the Twenty workspace User table, and place any owners without a matching Twenty User in a reconciliation queue. The customer provisions the missing Users in Twenty before the migration proceeds past the discovery phase, because OwnerId references are required on most standard object imports.

GleanView custom fields on Contacts, Companies, Deals, and Leads require pre-creation in Twenty's data model before any records are imported. We read the field schema from GleanView CSV headers during discovery, generate a field creation worksheet specifying each custom field's name, type (text, number, date, select, multi-select, checkbox, currency), and target object, and the customer or we create these fields in Twenty at Settings → Data Model before the migration begins. Fields that do not exist in Twenty at import time are silently skipped by the CSV loader, which is why schema creation is sequenced as a distinct step before any record import.

GatherSpaces file attachments — proposal PDFs, product images, and content library files — are stored outside GleanView's data model and are not included in CSV exports. We generate a file manifest listing every linked attachment with its URL, associated GleanView record type (Quote, Product, or Contact), and the record ID it was attached to. The customer uses this manifest to re-upload files to Twenty manually or via the Twenty API if the file hosting approach (external URL, S3, or inline upload) is confirmed. This gap is unavoidable without a GleanView API and is disclosed before migration scoping begins.