Migrate from BSI CRM to Zoho CRM

BSI Contact records map directly to Zoho Contacts. Standard fields (Full Name, Email, Phone, Title) map to Zoho's equivalent field names. We preserve any BSI custom fields as Zoho custom fields created during the pre-import schema phase. BSI contact owner assignment maps to the Zoho Contact Owner field via email lookup against the migrated User records.

BSI Company records map to Zoho Accounts. The BSI industry classification and hierarchical parent-company structure map to Zoho Account custom fields if they exist in the BSI export. We create the Account first in the load sequence so that the Contact.AccountId lookup is satisfied at the moment of Contact insert.

BSI Deal records map to Zoho Deals with pipeline stage mapped explicitly to Zoho Deal Stage. BSI deal stage names and probabilities vary by industry configuration (banking, insurance, healthcare, retail), so we build an explicit stage mapping table during discovery that resolves BSI stage labels to Zoho stage values before migration. Deal value, expected close date, and owner assignment migrate directly.

BSI Activity records (logged calls, emails, meetings, tasks) map to Zoho Activities. Each activity record retains its parent linkage to the Contact or Deal. Activity timestamp migrates to the Zoho Activity Date field to preserve historical ordering. We schedule bulk activity extraction outside the customer's peak usage window per BSI's observed performance characteristics during discovery extraction testing.

BSI custom objects discovered during the manual schema audit phase migrate to Zoho Custom Modules. We pre-create the destination schema in Zoho (module name, field definitions, field types) before any data import so that lookup relationships to Contacts, Accounts, or Deals are valid at insert time. BSI custom objects without a documented export endpoint require the customer to request a manual extract from BSI Professional Services; we flag this as a dependency in the discovery report.

File attachments associated with Contacts, Accounts, or Deals in BSI are exported individually and linked back to their parent record in Zoho via the Zoho Attachment API. BSI's file storage structure varies by configuration; we enumerate file paths during discovery and handle naming normalization during the transform phase to avoid duplicate filenames.

BSI User records migrate first in the load sequence because all other objects reference them as foreign keys. We resolve owners by email match against the Zoho User table provisioned before migration. Any BSI User without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

BSI tagging and custom classification fields that have no direct Zoho equivalent are captured as custom multi-select picklist fields. We create the picklist values during the schema pre-creation phase and populate from the BSI export. Tags that represent content classification map to Zoho Tags where applicable.

BSI pipeline stages vary by industry configuration, so we build an explicit stage mapping table during discovery that pairs each BSI stage name and probability percentage with a corresponding Zoho stage. If the customer uses multiple BSI pipelines, we create separate Zoho Deal layouts or map to Zoho's multiple pipeline capability (available from Enterprise tier) based on the customer's Zoho edition selection.

BSI workflow automation rules are configuration artifacts that do not export. We document every active BSI workflow during discovery with its trigger conditions, branch logic, and CRM actions. Zoho's Blueprint and Workflow Rules are the rebuild target. The customer receives a written workflow inventory with recommended Zoho equivalents and must rebuild them post-migration; we do not rebuild automation as code within the migration scope.