Migrate from WORKetc to Zoho CRM

WORKetc Lead records with status prior to conversion map to Zoho CRM Leads. The WORKetc lead status, source, and converted flag migrate as standard Zoho Lead fields. Any scoring data stored in custom fields carries over to custom Lead fields. We resolve the Owner by email match against the Zoho destination User table. Lead records that have already been converted in WORKetc route to Contacts attached to Accounts (see Contact mapping) rather than Leads.

WORKetc Company records map directly to Zoho CRM Accounts. The company domain and name become the Account Name and Website fields respectively. Company-to-Contact relationships are preserved by creating Account records before any Contact inserts, satisfying the Account-Contact lookup at the moment of import. This dependency order is enforced in every migration run.

WORKetc's unified Contact object splits into Zoho CRM Leads and Contacts. Contacts with WORKetc lifecycle stages of prospect or unqualified map to Zoho Leads. Contacts with stages of qualified, customer, or converted map to Zoho Contacts attached to Accounts. The original WORKetc lifecycle stage is preserved as a custom field on the Zoho record for audit and reporting. The split is computed at migration time using the WORKetc contact record's lifecycle property.

WORKetc Deals map to Zoho Potentially Lost or Won with the stage, amount, probability, and expected close date preserved. The deal-to-company association migrates as the Zoho Account lookup, and the deal-to-contact association migrates as a secondary lookup. We resolve the AccountId before inserting Deals to avoid orphaning the relationship.

WORKetc Projects use Types and Stages with weighted percentage progress that does not map directly to any standard project management field. We export the full stage configuration including each stage's custom weight percentage, then map progress to a duration-based equivalent in Zoho Projects. For organizations not licensing Zoho Projects, project names, statuses, and milestones migrate as Zoho CRM Tasks with custom fields carrying the stage and type information. The original weighted stage data is documented in a configuration reference file delivered alongside the migration.

WORKetc support tickets migrate to Zoho CRM Cases with status, priority, and full conversation history preserved. Ticket-to-company and ticket-to-contact links become Zoho Case Account and Contact lookups. Ticket conversation threads migrate as Zoho Case Email Messages linked to the Case. This mapping assumes the destination org does not have Zoho Desk; if Zoho Desk is in scope, Cases route there instead of the CRM module.

Invoice headers and line items migrate to Zoho Books Invoices if Zoho Books is part of the destination stack. If only Zoho CRM is in scope, invoices migrate as Zoho Quotes with a custom invoice number field and payment status preserved. We export invoice headers, line items, totals, and payment status; linked bank transaction records and reconciliation history are exported as a separate CSV for manual entry because these do not map to standard CRM fields.

WORKetc custom field definitions and values export with their data types (text, dropdown, date, numeric, checkbox). We map these to equivalent Zoho CRM custom fields, but Zoho requires custom fields to be pre-created in the destination before data import. We provide a field creation specification document listing each WORKetc custom field, its type, and the equivalent Zoho field type and module, and the customer or Zoho admin creates these before migration begins.

WORKetc active User records map to Zoho CRM Users by email match. We resolve every distinct WORKetc owner referenced on CRM records before migration and place any unmatched owners in a reconciliation queue for the customer's admin to provision Zoho User accounts. Active status, role, and permission level are noted in a User mapping document for the admin to configure roles and profiles post-migration.

WORKetc Contractor Portal users are a separate identity class with different permission scopes and may lack standard email credentials. We map contractor records to Zoho CRM Contacts with a custom field Contractor__c set to true. Contractors do not become Zoho Users because they have no seat on the CRM and the Zoho platform has no contractor portal equivalent. Their contact information migrates with the same field structure as standard Contacts.

File metadata, URL references, and linked record associations export from WORKetc. Binary file export depends on whether the destination Zoho org has Zoho Docs enabled. We export file metadata and URL references as a mapping file and migrate file binaries to Zoho Docs where the module is available, or flag for manual re-upload where it is not.

WORKetc Knowledge Base articles and category assignments export as content with category metadata. Article body content, title, and category assignments migrate to Zoho KB entries. Rich formatting, embedded media, and any linked images require post-migration review because formatting translation between the two platforms is not always lossless. We deliver a KB migration report listing every article, its category, and its status (clean migrate, requires review, or flagged for manual recreation).