Migrate from Less Annoying CRM to Twenty CRM

LACRM Contacts map directly to Twenty People records. All standard fields (name, email, phone, address, tags) map 1:1. Custom contact fields migrate by name and type, with LACRM dropdowns mapped to Twenty select options. The LACRM UID primary key is stored as a string throughout the pipeline to avoid precision loss from float rounding. We preserve the LACRM contact-to-company link using Twenty's relationship field on the People object, which must be configured in the Twenty data model before import.

LACRM Companies map to Twenty Company records. Company domain becomes the Website field and serves as a dedupe key during import. Because LACRM maintains Companies as a separate object from Contacts, we create Company records first during migration so that the People-to-Company relationship resolves correctly at the time of People import.

LACRM links Contacts to Companies via a dedicated relationship table rather than embedding a company reference inside the contact record. We call LACRM's relationship API endpoint explicitly to retrieve every contact-company link, then set the corresponding Twenty relationship field on each People record during import. We validate that every contact has a resolved company link before closing the migration, flagging any orphaned contacts that have no matching Company.

LACRM Pipeline Items map to Twenty Opportunities. LACRM pipeline stages are free-text and fully customizable per account; we map each distinct stage value to a Twenty Opportunity stage during schema design. Pipeline Item custom fields migrate as typed Opportunity custom fields. The opportunity amount, close date, and owner all map directly.

LACRM's free-text pipeline stages become Twenty Opportunity stage values configured in the data model before migration. We extract every distinct stage name from the LACRM pipeline, create corresponding stage values in Twenty, and map the stage ordering so that the pipeline view in Twenty reflects the original workflow sequence.

Notes attached to contacts, companies, or pipeline items migrate with their timestamp, author, and body content preserved. Notes are treated as standalone objects in LACRM and migrate as Twenty Comments or Note records linked to the parent People, Company, or Opportunity. Rich text formatting is preserved where the source note contains HTML content.

Tasks associated with contacts, companies, or pipeline items migrate including due date, assignee, completion status, and linked record reference. Open tasks migrate as open; completed tasks migrate with their completion timestamp. Task assignment is resolved by matching the LACRM owner email to the corresponding user in Twenty's Members list.

Calendar events (meetings, calls) logged against contacts migrate as Twenty Activities with their timestamp, title, description, and linked People or Opportunity reference intact. Events are one of the cleanest object mappings in this migration because both LACRM and Twenty support datetime-stamped activity records with relationship links.

Files attached to contacts or companies are exported as base64-encoded content from LACRM and re-created in Twenty linked to the corresponding People or Company record. Unlike the reverse migration path (into LACRM), Twenty's API supports file uploads to records, so file attachments migrate as first-class objects rather than requiring manual re-upload. We include the original filename and MIME type in the migration package.

Tags applied to contacts or companies migrate as-is into Twenty's tag field on People or Company. Multi-select tag fields are preserved as comma-separated values in Twenty's tag field. No transformation is required since both platforms use a flat tag model.

Custom fields exist on Contacts, Companies, and Pipeline Items in LACRM. We map them by name and type (text, date, number, dropdown) to their Twenty equivalents. LACRM dropdown options are created as select options in Twenty. Any field type that requires transformation (such as LACRM multi-checkbox stored as a delimited string) is flagged during scoping and handled as a string-to-array transformation during import.

LACRM automations are not exposed via the public API and cannot be read or exported by our migration tools. We document every automation found in the LACRM admin panel as a structured JSON handoff document during scoping, describing the trigger, conditions, and actions for each rule. The customer's team rebuilds these in Twenty's workflow builder. This is manual effort: budget 1-2 hours per automation depending on complexity. This is the highest-impact non-migratable object in this pair.