Migrate your Less Annoying CRM data

Contacts is LACRM's primary object. Standard fields (name, email, phone, address, tags) map 1:1. Custom contact fields are fully supported and migrate as typed properties. The UID primary key must be stored as a string to avoid float precision loss from its 31-digit length.

LACRM maintains Companies as a separate object from Contacts. We preserve the Contact-to-Company relationship explicitly during migration since LACRM links them via a relationship table rather than embedding company data inside contact records.

Pipeline Items migrate as the destination's equivalent Deals or Opportunities. LACRM pipeline stages are free-text and fully customizable per account; we map them to the destination's pipeline stages and flag any that have no natural equivalent.

Notes attached to contacts, companies, or pipeline items migrate with their timestamp, author, and body content preserved. Notes are treated as standalone objects linked by relationship records.

Tasks associated with contacts or pipeline items migrate including their due date, assignee, completion status, and any linked contact or pipeline item. Open tasks are migrated as open; completed tasks are migrated with their completion date.

Calendar events (meetings, calls) logged against contacts migrate with their timestamp, title, description, and linked contact reference intact.

Files attached to contacts or companies are exported as base64-encoded content and re-created in the destination system linked to the corresponding record. LACRM's 25GB per-user storage allocation does not carry over; we flag total file volume during scoping.

Tags applied to contacts or companies migrate as-is. Multi-select tag fields are preserved as comma-separated values or mapped to the destination's native tag or label object depending on the target platform.

Custom fields exist on Contacts, Companies, and Pipeline Items. We map them by name and type (text, date, number, dropdown) and flag any field types that require transformation (e.g., LACRM dropdowns that need value remapping in the destination).

Automations are not exposed via LACRM's public API. We export the automation rules as a structured JSON document during scoping so your team can rebuild them manually in the destination. No automation logic migrates automatically.

LACRM syncs emails via IMAP with Gmail or Outlook accounts. Email records associated with contacts migrate as Notes or Activity records in the destination, but the IMAP connection itself must be re-established in the new system.

User accounts, names, email addresses, and permission levels migrate as User records. LACRM's role model is simple (admin vs. standard user); we map this to the destination's user roles and flag any granular permissions that cannot be replicated 1:1.

Groups are LACRM's team-segmentation feature for controlling access. We map group membership to the destination's Teams or Sharing Groups. Note that LACRM Groups control both visibility and data access — these concepts may need to be represented differently in the destination CRM.