Migrate from Lead Guerrilla to Twenty CRM

Lead Guerrilla Contact records map to Twenty's People object. Standard fields (name, email, phone, address) migrate directly. Lead scoring values stored as a custom numeric property migrate to a Twenty custom field for lead scoring. The Contact's original 1CRM cross-reference ID is preserved in a custom field for audit. Email addresses serve as the dedupe key during import to prevent duplicate Person records.

Lead Guerrilla Company records map directly to Twenty's Company object. The Company domain name maps to the Website field. Each Company is imported before its linked Contacts so that the Person-to-Company relationship resolves at insert time. If 1CRM cross-references exist, we audit and re-link them manually post-migration using the preserved custom field.

Lead Guerrilla Segments group contacts by form source, behavior, or demographic criteria. Segment membership translates into a dynamic Audience or a custom multi-select field on the Person record in Twenty. During scoping the customer chooses between a static tag-based approach (preserves exact segment membership as of migration date) or a filter-based approach (Twenty custom field conditions that recreate the segment logic). Segment definitions themselves are documented for the customer to rebuild as Twenty views or segments.

Multi-channel campaign configurations from Lead Guerrilla (email, SMS, Twitter, web notification sequences) do not have a direct Twenty CRM equivalent since Twenty's native campaign tracking is oriented toward sales opportunities. We create a custom Campaign object in Twenty matching the channel structure and enrollment history, and map completed campaign enrollments as activity records tied to the relevant Person. The campaign automation logic is cataloged separately for rebuild.

Landing pages created in Lead Guerrilla's builder cannot be exported as portable HTML or schema files. We export page metadata (title, URL slug, published status) and redirect configuration, but the rendering code and embed scripts are not portable. The customer must rebuild these assets in Twenty or a dedicated landing page tool. We deliver a page-by-page inventory with field-level mapping to guide the rebuild.

Web forms embedded as tracking widgets in Lead Guerrilla are content assets. We export form field definitions, submission mappings, and redirect behavior, but form logic (field visibility conditions, required field rules) cannot be extracted. The customer rebuilds forms in their new platform. We provide a field-level inventory of every form so the rebuild is guided rather than ad hoc.

Lead Guerrilla's automation engine defines time-based and trigger-based actions (email firing after X hours, campaign enrollment on form submit, score adjustments on page visit). There is no documented export path for these rules. We catalog every active automation via screenshots and admin UI configuration notes during discovery, then deliver a detailed reimplementation playbook mapping each rule to its recommended equivalent in the customer's new marketing automation platform. This is manual rebuild work the customer must budget for.

The current numeric lead score per Contact is preserved as a custom field on Twenty's Person object. The scoring model itself (point values per behavior, stage thresholds) is documented for the customer to reconfigure in their new platform, since it lives in the automation engine rather than the contact record.

Contact interactions tracked in Lead Guerrilla (email opens, page visits, form submissions, SMS sends, tweet engagement) are exported as activity history. Due to Lead Guerrilla's lack of API, high-volume activity records require page-by-page or screenshot-assisted cataloging. We import activity data as Task and Note records on the corresponding Person record in Twenty, with the original timestamp preserved for timeline ordering.

Contacts and Companies in Lead Guerrilla can be tagged. We export all tag assignments and reapply them as tags in Twenty. Tag naming conventions are preserved exactly as-is to maintain segmentation continuity. If a tag maps to a segment definition, we reference both in the reimplementation playbook.

User accounts in Lead Guerrilla map to campaign owners and assignment recipients. We export the user list including name and email. Twenty's workspace members are provisioned separately; we map Lead Guerrilla owner references by email match and flag any orphaned assignments for the customer's admin to resolve before migration completes.