Migrate from SuiteCRM to Zoho CRM

SuiteCRM Accounts map directly to Zoho CRM Organizations. The mapping preserves name, industry, website, billing address, and shipping address fields. SuiteCRM subpanel relationships (Account to related Contacts and Opportunities) require flattening during extraction — we export the relationship junction data and reconstruct the Organization-Contact and Organization-Deal linkages in Zoho using its module relationship model. Parent-child Account hierarchies become Zoho Organization hierarchy lookups if the destination Zoho edition includes that feature.

Contacts map 1:1 to Zoho Contacts with all standard fields preserved (name, email, phone, title, address). SuiteCRM's primary Account link becomes a Zoho Contact lookup to the Organization module. Custom fields added via SuiteCRM Studio require database-level extraction from the extended cstm_* tables and manual field creation in Zoho CRM before import. Email validation is applied during import to catch malformed addresses carried over from SuiteCRM.

Leads map directly to Zoho Leads. SuiteCRM lead status and lead source picklist values are mapped to Zoho Lead Status and Lead Source picklist values, with unmapped values created as new picklist entries during the sandbox validation phase. Custom fields on Leads follow the same Studio extraction and Zoho field creation process as Contacts and Accounts.

SuiteCRM Opportunities map to Zoho Deals. This mapping requires a pre-migration decision: Zoho CRM has a standard Opportunities field on the Deal module, and using both the Opportunities field and the Deal name simultaneously can cause confusion for Zoho administrators. We recommend renaming the Zoho Opportunities field or scoping its visibility before migration begins. Deal amount, stage, close date, and probability map directly. Pipeline and stage migration requires Zoho pipeline configuration to be completed before Deal records are imported.

SuiteCRM Products map to Zoho Products. The product name, SKU (product code), pricing, and description transfer directly. Products must be imported into Zoho before Quotes so that line item lookups resolve correctly. If SuiteCRM Products include a taxonomy or category structure, we map those to Zoho Product Categories. The product catalogue import is a prerequisite phase that completes before any Deal or Quote migration begins.

SuiteCRM Quotes map to Zoho Quotes. Quote metadata (number, date, expiry, terms, subtotal, tax, total) transfers directly. Quote line items reference Products already imported in the prerequisite phase. SuiteCRM PDF attachments associated with Quotes are extracted from the filesystem and migrated as Zoho Notes with the Quote linked, or as WorkDrive document references depending on the customer's preferred Zoho file management approach decided at scoping.

SuiteCRM Cases (tracked in the Bugs module) map to Zoho Cases. Case subject, description, status, priority, and resolution fields transfer directly. Case-related activities (notes, tasks, emails) migrate as Zoho Activity records linked to the Case. If the destination Zoho CRM edition does not include the Cases module, we flag this at scoping and discuss whether to upgrade the Zoho edition or treat Cases as a custom module reconstruction.

SuiteCRM Campaigns map to Zoho Campaigns with campaign name, type, status, start date, and budget preserved. Email campaign response data (opens, clicks, bounces) migrates as Zoho Campaign activity history. Campaign target list memberships from SuiteCRM's Target Lists module require conversion to Zoho Tags with Tag Assignment records, which is a configuration step performed during the sandbox validation phase.

SuiteCRM Documents store files on the server filesystem with database metadata records. We export the file blobs from the upload directory alongside their database metadata. The file migration strategy is decided at scoping: Zoho's native file migration tool supports WorkDrive destination; alternatively, files migrate as Zoho Notes attached to the related record. We validate file integrity checksums after extraction and flag any files with permission issues that may have become inaccessible on the source server.

SuiteCRM Studio custom fields are stored in extended database tables with naming conventions appended to the module name. We scan the database schema during discovery to enumerate every custom field, its data type, and the module it belongs to. Each custom field then requires manual creation in Zoho CRM (custom field name, type, and picklist values) before the corresponding records are imported. The translation from SuiteCRM field types to Zoho field types is documented in the mapping spreadsheet and validated in sandbox.

SuiteCRM Users map to Zoho Users via email address matching. Every record (Account, Contact, Lead, Deal, Case) carries an owner field referencing a SuiteCRM User. We extract the distinct set of Users and match by email against the destination Zoho CRM org. Any SuiteCRM User without a matching Zoho User is placed in a reconciliation queue for the customer's administrator to provision before the production migration begins. Owner resolution must complete before record import phases start.

SuiteCRM Invoices track payment status but have no connection to a general ledger or accounts-receivable system. We export Invoice records as-is, preserving invoice number, date, amount, line items, and payment status. For customers using SuiteCRM Invoices as their primary billing record, we flag that advanced accounting features (AR/AP ledger, credit memos, tax filing) do not exist in the CRM and require either Zoho Books integration or a dedicated accounting system. Invoice data is migrated as Zoho Invoice records if the destination edition includes the module.