Migrate from Lemon Tech to Freshsales

Standard Lemon Tech entities with contact-type data (individuals) map to Freshsales Contact. Entities representing organizations map to Freshsales Account. We determine the entity type from the Lemon Tech entity definition exported during discovery. The original Lemon Tech entity name is preserved in a metadata field for audit. Email, phone, and address fields map directly to Freshsales standard fields.

Lemon Tech custom entities map to Freshsales custom objects provisioned via the Freshworks developer platform's entity storage feature. We pre-create the custom object schema in Freshsales during migration setup, including all custom fields and any lookup relationships to native objects (Contact, Account, Deal). Custom entity naming conventions vary by customer; we normalize API names to Freshworks standards during mapping.

Lemon Tech Matters map to Freshsales Deals as the primary case or project container. Matter fields including status, dates, responsible attorney, practice area, and linked contacts migrate to corresponding Deal fields or custom Deal fields. The Matter timeline and time entries link to the Deal as custom fields or associated activity records. If the customer uses Freshdesk for service tickets, Matter records can alternatively map to Case objects.

Standard contact records with name, email, phone, and address fields map directly to Freshsales Contact. Custom contact properties defined in Lemon Tech migrate to Freshsales custom contact fields. The contact's primary Matter association migrates as a Deal lookup or custom field on the Contact record.

Lemon Tech User records with name, email, and role information map to Freshsales User. We match by email address. Any Lemon Tech user without a matching Freshsales User record goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission context is preserved in a custom field for reference during post-migration access configuration.

SQL Wrapper exports depend on definition complexity. Simple wrappers that export single-table data map directly to Freshsales custom objects. Complex wrappers with multi-table joins, computed columns, or third-party data require manual field mapping during migration and may require restructuring as multiple related custom objects in Freshsales. We inventory all SQL Wrapper definitions during discovery and flag any with nested logic or external data sources as requiring custom mapping work before migration.

File attachments associated with Lemon Tech entities or matters export as binary files. We preserve filenames, parent record associations, and timestamps. Files migrate as Freshsales attachments linked to the corresponding Contact, Account, or Deal record. Large attachment volumes may require staged migration to avoid timeout issues.

Time entries and billing records linked to Matters export via the Entity export. Billable amounts, dates, and linked contact references migrate to Deal custom fields or line items. If the customer uses Freshsales for invoicing or has a separate billing workflow, we map billing records to the appropriate destination during scoping. The original billing status from Lemon Tech is preserved for reconciliation.