Migrate from GENIEE to Zoho CRM

GENIEE SFA/CRM Contacts map to Zoho CRM Contacts. Japanese field labels (stored in the GENIEE SFA/CRM tenant schema) are discovered during scoping with Japanese-speaking data engineers and machine-assisted translation. We map each Japanese field name to a corresponding Zoho CRM field using the English alias where available, or we create a Zoho Custom Field to receive the data. Contact ownership resolves by email against Zoho Users. Any GENIEE Contact without a matching Zoho User is placed in a reconciliation queue for the customer's admin to provision before import resumes.

GENIEE SFA/CRM Account records (called Companies internally) map to Zoho CRM Accounts. The account hierarchy and regional location data use Japanese regional conventions (prefecture names, Japanese address formats) that we preserve as text values in Zoho Account fields rather than normalizing to Western address formats. Department and division data may not map to a standard Zoho field; we create Custom Fields as needed during scoping.

GENIEE SFA/CRM Deals map to Zoho CRM Potentials. Pipeline stages from GENIEE are tenant-defined and may use Japanese stage names. We map each GENIEE stage to a Zoho Stage value and configure the Zoho Sales Process before migration so that stage ordering and probability percentages carry through. Stage history (all historical stages with timestamps) migrates as a Zoho Notes or Custom Field record attached to the Potential for audit.

GENIEE MA Campaigns with UTM attribution data, source, and medium migrate to Zoho Campaigns. Campaign attribution data stored per Contact in GENIEE (UTM source, UTM medium, UTM campaign) is mapped to Zoho Custom Fields on the Contact record since Zoho Campaigns use Campaign Members rather than per-contact attribution fields. The customer chooses during scoping whether to maintain UTM data on Contacts, Campaigns, or both.

GENIEE DSP campaigns include budget, targeting parameters, ad formats, flight dates, and performance metrics. These do not map to standard Zoho CRM objects. We create a Zoho Custom Module named DSP Campaigns with fields for Budget, Targeting_Type, Ad_Format, Flight_Start, Flight_End, DSP_Platform, and Campaign_ID. We link DSP Campaign records to Zoho Accounts or Contacts via Lookup fields. Performance metrics (impressions, clicks, bid logs) export separately and are mapped to Zoho Custom Fields on the same custom module. DSP data is scoped separately from SFA/CRM data because it requires a distinct export workflow from the DSP subsystem.

GENIEE SSP publisher inventory includes slot IDs, floor prices, telco/mobile/desktop classifications, and publisher IDs. This is SSP-specific and has no standard CRM equivalent. We create a Zoho Custom Module named Publisher Inventory with fields for Slot_ID, Floor_Price, Inventory_Type (telco/mobile/desktop), Publisher_ID, and SSP_Platform. Records are linked to Zoho Accounts representing publishers via Lookup. The customer chooses whether to include historical inventory snapshots or current-state only.

GENIEE SFA/CRM Users as record owners map to Zoho Users by email address. Role and department data from GENIEE migrates to Zoho Custom Fields on the User record. Any GENIEE User without a matching Zoho User is placed in the reconciliation queue; the customer provisions the Zoho User before record import continues. Role-based access from GENIEE maps to Zoho Profiles and Roles, though a full security model redesign is recommended post-migration rather than as part of the data migration scope.

Attachments on GENIEE Contacts, Accounts, and Deals are exported as binary blobs and re-uploaded to Zoho CRM attached to the corresponding Contact, Account, or Potential record. We preserve original file names, MIME types, and file sizes. File size limits are tenant-specific on GENIEE and Zoho has internal attachment size limits that we verify during scoping. Attachments are migrated after the parent record exists in Zoho to maintain referential integrity.

GENIEE SFA/CRM custom fields on Contacts and Accounts are tenant-defined. We discover the full custom property list during scoping, generate a field map with type conversions (Japanese text to string, Japanese numeric formats to decimal, Japanese dates to ISO 8601), and create Zoho Custom Fields before import. If GENIEE custom properties include multi-level hierarchies or cross-object references, we may recommend a Zoho Custom Module instead of individual fields. Zoho's 300-field per module limit and the Standard Edition's exclusion of custom fields require the customer to have at least the Professional tier for full custom field support.

GENIEE Tags on Contacts and Companies are tenant-defined vocabulary. We export tags as label arrays and map them to Zoho Tags on the Contact and Account records. If the tag vocabulary is extensive (more than 50 distinct tags per record), we may recommend a Zoho Multi-Select Picklist field on the relevant module instead of Tags for better filtering and reporting. The customer chooses the strategy during scoping.