Migrate from Legl to Freshsales

Legl business records (representing law firm client entities) map 1:1 to Freshsales Accounts. Company name, domain, address, and industry fields migrate as Account standard fields. Legl business custom fields (jurisdiction, firm_type) become Freshsales Account custom fields. Original Legl business creation timestamps are preserved as custom datetime fields for audit continuity.

Legl engage_request objects representing new matter requests or prospective client intake map to Freshsales Leads when the request is pre-contact, or to Contacts when the request already references a known business. The engage_request type field determines routing: 'new_matter' → Lead, 'existing_client_matter' → Contact. Request status and owner email are preserved as custom fields.

Legl engage_request records that reference an existing Legl business are split: the person making the request becomes a Freshsales Contact associated with the mapped Account, and the request metadata (request_type, priority, deadline) becomes Contact custom fields. This ensures sales reps see the client relationship and the legal request in one record.

Legl risk_assessment objects have no Freshsales native equivalent. FlitStack creates a Freshsales Custom Module named 'Risk Assessment' on Enterprise plans, or maps key fields to Contact and Account custom fields on Growth/Pro. Assessment outcome (risk_level, risk_score, status), PDF reference URL, and completed date migrate. AML compliance flags map to a custom pick-list field on the linked Contact or Account.

Legl payment records (representing legal fee transactions) map to a Freshsales Custom Module on Enterprise, or as a custom related list on the Account for Growth/Pro plans. Payment amount, currency, payment_date, payment_method, and associated Legl business_id are stored. For teams on Growth/Pro, the most recent payment summary fields (last_payment_amount, last_payment_date) are added as Account custom fields for quick visibility.

Legl business_report objects (company reports, sanctions checks) do not map to a Freshsales standard object. On Enterprise plans, a 'Business Report' custom module stores report_type, report_date, outcome, and linked Legl business reference. On lower plans, report status and date are stored as Contact or Account custom fields, with the full report preserved as a Freshsales File attachment.

Legl workflows (internal escalations, AML checks, client onboarding sequences) are automation configurations, not data records. They cannot be exported as migrateable data. FlitStack exports Legl workflow definitions as a structured JSON reference document that documents triggers, conditions, and actions — your Freshsales admin uses this to rebuild equivalent Automation Rules in Freshsales.

Legl owner IDs are resolved to Freshsales users by email match. If a Legl owner email has no corresponding Freshsales user account, FlitStack flags the owner before migration — your team either creates the Freshsales user or assigns those records to a fallback owner. Legl organisation-level metadata is stored as a reference note on the Freshsales Account record.

Legl ongoing monitoring records (periodic AML checks on business entities) have no Freshsales equivalent. Key monitoring status fields (last_check_date, monitoring_status, next_review_date) migrate as Account custom fields. Recurring monitoring tasks are generated as Freshsales Tasks linked to the Account with due dates, ensuring compliance review does not lapse after migration.

Legl file attachments (PDFs of risk assessments, sanctions reports, client documents) are downloaded and re-uploaded as Freshsales Files linked to the corresponding Contact, Account, or custom module record. File size limits apply: Freshsales default 25MB per file. Inline document references in Legl notes are preserved as Freshsales Notes with the file link intact.