Migrate from Leadtrekker Lead Management to Zoho CRM

Leadtrekker Leads map directly to Zoho CRM Leads. The Lead Name (Last Name is Zoho's only mandatory field), email, phone, status, lead source, owner, and creation timestamp migrate as standard fields. We preserve the Leadtrekker lead status label in a Zoho custom field ltk_original_status__c for reporting continuity. If Leadtrekker uses a compound name field rather than separate first/last, we split on the first space and populate Last Name accordingly.

Leadtrekker has no separate Contact or Account concept — all records are Leads. Zoho CRM separates unqualified prospects (Lead) from qualified buyers (Contact linked to Account). We migrate all records as Leads first. If the customer requires Contact and Account records, we recommend a post-migration Zoho Lead Convert batch process. The customer decides the conversion trigger (e.g., stage equals Won, or manual selection). We do not auto-convert during migration because that creates orphaned Contacts without the correct Account hierarchy.

Leadtrekker stores source attribution (website form, campaign, referral, etc.) as a Lead property. We migrate source labels into Zoho CRM's standard Lead Source picklist. If Leadtrekker uses a custom source taxonomy not present in Zoho's default picklist values, we extend the picklist during schema setup before import so that no source value is silently dropped.

Leadtrekker call logs attached to a Lead migrate to Zoho CRM Tasks with TaskSubtype set to Call. Call duration, disposition, and user attribution migrate to custom task fields. ActivityDate is set to the original Leadtrekker timestamp to preserve the timeline ordering. We resolve the Leadtrekker owner email to a Zoho User record via the User mapping before Task insertion.

Leadtrekker email events (sent, opened, replied) attached to a Lead migrate to Zoho CRM Tasks with the email body and headers stored in the Task description. Each email event becomes one Task record with Subject carrying the email subject line and ActivityDate set to the original timestamp. We preserve the email direction (inbound/outbound) in a custom field.

Leadtrekker notes attached to a Lead migrate to Zoho CRM Notes (the legacy Notes object) linked via ContentDocumentLink to the parent Lead. Note body migrates as plain text. If Leadtrekker stores notes with rich text formatting, we preserve content and flag image attachments for manual handoff if they exceed Zoho's attachment size limit (25MB per file).

Leadtrekker follow-up reminders carry a due date and owner assignment. We convert these to Zoho CRM Tasks with the same Subject, due date (mapped to ActivityDate), and Owner resolved via the User email mapping. The Leadtrekker reminder status (pending/completed) maps to Zoho Task Status (Not Started / Completed). Open reminders migrate as Not Started; completed reminders migrate as Completed.

Leadtrekker custom fields on Lead require explicit field-level mapping because Leadtrekker does not publish a stable field taxonomy in its public documentation. We conduct a discovery probe during scoping to enumerate all custom field names, types, and sample values, then create equivalent custom fields in Zoho CRM before migration. Field types are mapped: text to Single Line, long text to Multi Line, number to Numeric, date to Date, checkbox to Checkbox, picklist to Picklist.

Leadtrekker user accounts store login credentials and profile data. We export the user roster and match by email address against Zoho CRM User records. Leadtrekker passwords and session tokens do not transfer. If a Leadtrekker user has no matching Zoho User, the record is held in a reconciliation queue and the customer's Zoho admin provisions the User before record migration resumes. Active/inactive status is preserved from Leadtrekker.

Leadtrekker user groups define which users can view and edit specific lead subsets. Zoho CRM uses Roles (job function), Profiles (field-level and module access), and Data Sharing Rules (record-level access) which have different semantics from Leadtrekker's group model. We extract the full group membership roster and build a mapping table to Zoho Roles and Profiles. The customer's Zoho admin rebuilds the access logic manually post-migration using our mapping table as the reference document.

Leadtrekker Lead status values (e.g., New, Contacted, Qualified, Lost) map to Zoho CRM's Lead Status picklist. We extend Zoho's default picklist during schema setup to include all Leadtrekker status values so no record is rejected during import. Status probability percentages from Leadtrekker (if stored) migrate as custom fields rather than Zoho native probability, which is derived from the Sales Stage on converted Opportunities.

Leadtrekker file attachments on Leads migrate to Zoho CRM Attachments linked to the parent Lead. We chunk attachments larger than 25MB and flag them for manual handoff. Attachment filename and Content-Type are preserved. If Leadtrekker stores attachments in a format Zoho does not render inline, we note the file and provide a download reference for the customer's admin.