Migrate from Empire SUITE to Zoho CRM

Empire Suite contacts map directly to Zoho CRM Contacts. Email, phone, and address fields transfer as-is. If the source record has no associated company, it lands as a standalone Zoho Contact with no AccountId — your admin links it manually or via import matching on email domain.

Empire Suite contacts marked as archived or inactive route to Zoho CRM Leads to preserve a historical record without cluttering the active Contact list. Active contacts remain Contacts in Zoho. The split is based on a status field value in Empire Suite identified during discovery.

Empire Suite companies map to Zoho CRM Accounts using direct field translation. Company name becomes Account Name, while the website, industry classification, and employee count fields transfer directly without transformation. Parent-company hierarchies in Empire Suite map to Zoho's Account hierarchy via the Parent Account lookup field, maintaining organizational structure across the migration.

Empire Suite deals map to Zoho CRM Deals with stage value mapping applied to match the target pipeline layout. Deal name, amount, expected close date, and owner all transfer directly. Stage names are translated value-by-value against Zoho's Stage pick-list options for the designated pipeline, ensuring consistent deal lifecycle representation in the destination system.

Empire Suite pipelines map to Zoho CRM Deal Pipelines on a 1:1 basis. Each pipeline's stage sequence transfers as-is. Stage probabilities transfer as optional numeric fields if the source stores them — Zoho's Stage probability field is scoped per pipeline layout.

Empire Suite call and email records map to Zoho Tasks with Type field set to Call or Email respectively. Meetings map to Zoho Events with original start and end times preserved. Each activity links to its parent Contact or Deal record via the WhatId field in Zoho.

Empire Suite notes migrate as Zoho CRM Notes, preserving the original content where possible. Plain-text notes transfer directly without modification. When source notes contain rich-text formatting with unsupported HTML markup, FlitStack extracts the underlying text content and strips incompatible tags to ensure readability and proper display within Zoho's Note module interface.

File attachments against Empire Suite records are downloaded and re-uploaded to Zoho CRM Attachments. Zoho's 25 MB per file limit applies — files exceeding this are flagged for splitting or alternative delivery. Attachments link to the same parent record in Zoho that they referenced in Empire Suite.

Empire Suite custom objects map to Zoho CRM custom modules. The _C naming convention is applied to the module's API name. Custom module relationships that use N:N linking in Empire Suite require manual junction module setup in Zoho — we document the required relationships in the migration plan.

Empire Suite owner references resolve to Zoho CRM Users by email address match. Unmatched owner IDs are flagged before migration so your team either creates the corresponding Zoho user first or assigns records to a fallback owner. No record lands without a valid Zoho OwnerId.

Empire Suite workflows, approval rules, and automated assignment logic do not migrate to Zoho CRM. FlitStack audits the source automation configuration and delivers a Zoho Blueprint + Workflow rebuild plan organized by module and trigger type. Rebuilt automations are your admin's responsibility using Zoho's visual workflow builder.

Empire Suite reports and dashboards do not transfer. The underlying data migrates, so Zoho CRM's native reporting picks up the same records. FlitStack delivers a report inventory document listing every source report's metric and filter logic so your admin can rebuild each one in Zoho Analytics or the native report builder.