Migrate from Wice CRM to HubSpot

HubSpot's German-language interface requires explicit locale and property-label configuration

Wice CRM is primarily built for German-language environments, and its German field labels and display text do not automatically map to HubSpot's English-language internal property names. When we create HubSpot custom properties for migrated Wice custom fields, we preserve the original Wice label as the HubSpot display name — but HubSpot's internal API property names use the original field identifier. Additionally, HubSpot's German language pack applies to the UI labels but not to system property names. Your team should plan a brief review of all migrated custom property labels in HubSpot's settings to confirm they match your German-language workflow expectations before go-live. This is a configuration step, not a data-loss issue — all values transfer correctly regardless of label language.

Wice call and email logs require association re-linkage after parent-record migration

HubSpot associates engagement records (calls, emails, notes) to contacts, companies, and deals via its association API using the newly created HubSpot record IDs. Wice stores call logs and email logs with their own internal record IDs and links to contacts and deals. Because HubSpot IDs are assigned at migration time (not copied from Wice), we cannot pre-populate association records during the Wice export — we re-link each activity to its parent record in a post-processing step after contacts and deals land in HubSpot. For Wice deals with multiple associated contacts, the primary contact from Wice receives the primary deal association; additional contacts receive secondary deal associations via HubSpot's multi-association model. If Wice records reference parent contacts that were not migrated (e.g., deleted or archived records), those associations are logged and your team decides whether to create placeholder associations or skip them.

HubSpot's API returns maximum 200 records per page — large Wice datasets require iterative pagination

HubSpot's CRM Search API returns a maximum of 200 records per page with an after cursor for pagination. Wice CRM's API has its own rate-limit tiers (Starter 500 req/min, Professional 2,500 req/min, Enterprise 10,000 req/min). For Wice CRM instances with over 10,000 contacts or 5,000 deals, our migration engine uses server-side cursors and iterative fetches to pull all records — this extends the extraction phase but does not affect data quality. We batch writes to HubSpot using the HubSpot Bulk Import API where possible to stay within HubSpot's throughput limits. The extraction and load phases run as separate background jobs with a checkpoint model so that any API timeout or rate-limit pause resumes from the last confirmed record rather than restarting.

HubSpot's marketing contact billing model does not apply to Wice CRM contacts

Wice CRM does not have a marketing-contact billing flag equivalent. When contacts migrate to HubSpot, all migrated contacts land as standard HubSpot CRM contacts. If your HubSpot plan uses the marketing contacts billing model, only contacts that receive marketing emails are counted — but this is a HubSpot plan configuration, not a migration artifact. We flag every migrated contact's original Wice contact type (if present) as a HubSpot custom property so your team can apply HubSpot marketing contact status rules after migration based on the historical source data. No contacts are inadvertently flagged as marketing contacts at migration time.

Wice workflows, automation rules, and sequence triggers do not migrate to HubSpot workflows

This is the highest-severity limitation for teams with complex Wice automation. Wice CRM stores workflow logic, automation rules, assignment rules, and sequence triggers in its own execution engine. HubSpot's workflow builder (HubSpot workflows) operates independently and has no import path from Wice. Every Wice automation — lead routing rules, stage-change triggers, follow-up sequences, internal alerts, and SLA timers — must be rebuilt from scratch in HubSpot's workflow interface. We export a structured JSON representation of your Wice workflow definitions as a rebuild reference for your HubSpot admin. The rebuild effort depends on automation complexity: simple if-then rules take under an hour each to recreate, while multi-step sequences with conditions and time delays require 2–4 hours per automation. Budget for this rebuild phase in your migration timeline.