Migrate from TeamWave to Freshsales

Discovery and data audit

We extract a full inventory of TeamWave objects in scope: Contacts, Companies, Deals, Projects, Tasks, Calendar Events, Users, and custom fields. We run test exports from each TeamWave module to assess export limits, row counts per export, and the presence of any data that requires splitting across multiple exports. We also identify whether TeamWave is on the free, Pro, or Enterprise tier because free-tier feature caps affect export scope. The discovery output is a written data inventory, a list of TeamWave custom fields with their types, and a recommendation on the Project-to-Freshsales mapping strategy (custom object or task tag).

Relationship reconstruction and CSV normalization

TeamWave stores foreign keys across separate CSV exports: Contact records reference a company_id, Deal records reference a contact_id or company_id, Tasks reference a project_id. We reconstruct these relationships by joining the exports on the shared keys before writing the normalized import CSVs. We deduplicate on email for Contacts and on company name for Accounts. We flag any records with broken foreign keys (orphaned Deals, Tasks with no linked Contact or Project) and escalate to the customer for resolution before import.

Freshsales schema setup and custom field creation

We create all required Freshsales custom fields (matching the types from TeamWave), set up the Project custom object if that strategy is chosen, configure pipeline stages to match the TeamWave deal stages, and configure the lead conversion field mapping if the customer has unqualified leads. We run this in a Freshsales trial or sandbox org first for validation. Territory assignment rules are set up if the customer uses territories, following Freshsales' best practices for territory-based data routing.

Test migration and reconciliation

We run a full test migration using production-like data volume into the Freshsales trial org. The customer reconciles record counts (Contacts in, Accounts in, Opportunities in, Tasks in, Events in), spot-checks 20-30 random records against the TeamWave source, and validates that the TeamWave lifecycle stage values appear correctly in the Freshsales custom field. Any mapping corrections (wrong field, wrong type, missing picklist value) happen in this phase, not in production.

Production migration in dependency order

We run production migration in record-dependency order: Users (validated), Accounts (from TeamWave Companies), Contacts (with AccountId resolved), Opportunities (with OwnerId resolved), Tasks and Events, Project records (if using custom object), then custom field data. Each phase emits a row-count reconciliation report before the next phase begins. We use Freshsales' CSV import via Admin > Data Import with the standard field mapper. Large imports (>5,000 rows) are chunked into batches of 2,000 to avoid import timeouts.

Cutover, validation, and automation rebuild handoff

We freeze TeamWave writes during the cutover window, run a final delta migration of any records modified during migration, then switch the customer to Freshsales as the system of record. We deliver the TeamWave workflow inventory document to the customer's admin for Freshsales automation rebuild. We hand off the attachment re-upload manifest. We support a three-day post-cutover window where we resolve any data issues surfaced by the sales team. We do not rebuild TeamWave automations inside the migration scope; that is a separate engagement.