Migrate from TeamWave to Zoho CRM

TeamWave Contact records map to Zoho CRM Leads. We extract Contact fields (name, email, phone, address, lifecycle stage) via CSV export and map them directly to Zoho Lead fields. The TeamWave lifecycle stage property is preserved as a custom text field lead_original_stage__c for audit and segmentation post-migration. If the customer uses TeamWave's lead-versus-contact distinction, unqualified records go to Lead and pre-converted records to Contact based on the scoping decision made during discovery.

TeamWave Company records map to Zoho CRM Accounts. The TeamWave company_id foreign key is preserved during extraction and used as the dedupe key in Zoho. Account is inserted before any Contact or Lead migration so that the Account Lookup field on Contact is satisfied at the moment of insert. Website, industry, phone, and address fields map directly to Zoho Account fields.

TeamWave Deals map to Zoho CRM Potentials (Opportunities). The dealstage, amount, owner, expected_close_date, and pipeline association from TeamWave export directly to Zoho Potential fields. We configure Zoho pipeline stages to match TeamWave's pipeline stages before migration so that stage assignments are valid at insert time. Closed-won and closed-lost reasons from TeamWave custom fields become Zoho Loss Reason and Won Reason custom fields.

TeamWave deal pipeline stages are replicated in Zoho CRM as Potential Stage values under the corresponding pipeline. We configure Zoho pipeline stages in the CRM before any Potential records are inserted to avoid validation errors on stage name mismatches. Stage probabilities are set to match TeamWave values where documented, defaulting to Zoho standard probabilities where they are not.

TeamWave Project records carry name, description, status, client association (linked Company), and start/end dates. Zoho CRM does not include a native Project module in the standard CRM tier. During scoping, we assess whether Projects should map to a custom Projects module created via Zoho's Data Migration wizard (using _C filename convention) or be flattened to Zoho Tasks with a project identifier tag. The customer chooses the strategy; we configure the destination schema accordingly before migration.

TeamWave Tasks linked to Projects or Contacts map to Zoho CRM Tasks. We preserve the project_id and contact_id foreign keys from TeamWave as custom lookup fields or task subordination in Zoho depending on whether a custom Projects module is configured. Assignee, due date, status, and priority migrate directly to Zoho Task fields. Tasks without a linked Project are inserted as standalone Zoho Tasks.

TeamWave User records (name, email, role, department) map to Zoho CRM Users. We resolve owners by email match against the Zoho destination User table. Any TeamWave User without a matching Zoho User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignments on Deals and Tasks are updated to the resolved Zoho OwnerId during migration.

TeamWave Calendar Events (event title, date/time, linked entity, attendees) map to Zoho CRM Activities. We export as date-stamped activity records and insert into Zoho's Activity module. Attendees are mapped to Zoho Activity lookup relationships where the destination User or Contact can be resolved by email. Events without resolvable attendees are inserted as single-participant records.

TeamWave HR module holds employee profiles including name, role, department, and basic metadata. Zoho CRM does not include a native HR module; Zoho People is a separate product in the Zoho One bundle. We assess during scoping whether to migrate employees as Zoho CRM Contacts (with a custom is_employee__c flag), or to stage them for a separate Zoho People import if the customer licenses Zoho One. The chosen path is documented and configured before migration begins.

TeamWave custom fields on Contacts, Deals, Projects, and Tasks are exported alongside standard fields. We create matching custom fields in Zoho CRM via the Data Migration wizard (which prompts for new field creation during import) or pre-create them during schema configuration. Field types are mapped: TeamWave text fields to Zoho single-line text, date fields to Zoho date fields, and multi-select values to Zoho multi-select picklists. Any field types without a Zoho equivalent are flagged for the customer's admin to resolve.

TeamWave provides no bulk attachment export mechanism. We snapshot attachment metadata (filename, size, linked object type and ID) and generate a re-upload manifest listing each file, its original location, and the target Zoho record URL. Customers complete attachment re-upload manually in Zoho CRM after migration. This is not a migration failure; it is a documented scope exclusion because TeamWave's UI does not expose binary file export.