Migrate from GBuilder to Zoho CRM

GBuilder Contact maps directly to Zoho CRM Lead. All standard fields (name, email, phone, address) transfer directly. GBuilder contacts without a primary company association land as unassociated Zoho Leads. If GBuilder tracks a lifecycle or status field, it maps to a custom pick-list on the Lead record.

GBuilder Contacts that have a primary company association map to Zoho CRM Contact linked to the corresponding Account via the Account Name lookup. The Account record must exist in Zoho first — FlitStack sequences Accounts before Contacts to satisfy the foreign-key dependency.

GBuilder Company maps 1:1 to Zoho CRM Account. Standard fields — Account Name, Website, Industry, Phone, Annual Revenue, Number of Employees — transfer directly. Parent-company relationships in GBuilder map to the Parent Account lookup in Zoho; circular parent references are flagged before migration.

GBuilder Deal (or Project, depending on GBuilder configuration) maps to Zoho CRM Deal. The Deal Name, Amount, Close Date, Owner, and Stage fields transfer directly. Stage pick-list values undergo value-by-value mapping because GBuilder stage names rarely match Zoho's default stage set.

GBuilder pipeline stages are preserved as a Zoho Deal custom multi-select pick-list field (Stage_Name__c). Zoho Blueprint workflows tied to stage transitions are not transferred — FlitStack exports the GBuilder stage sequence and transition logic as a rebuild reference for Zoho Blueprint configuration.

GBuilder task records map directly to Zoho CRM Tasks. Subject, Status, Priority, Due Date, Related To (linked to the parent Contact or Deal), and Description fields transfer directly. FlitStack preserves the original created date as Created_At__c on the Zoho Task record.

GBuilder event records map to Zoho CRM Events with start datetime, end datetime, and venue/details fields preserved. Recurring events are imported as a single recurring series — Zoho's ICS export consolidates recurring instances into one entity; individual modified instances retain their RECURRENCE-ID.

GBuilder notes migrate as Zoho CRM Notes. Title, Body (plain text), and the parent record link (Contact, Account, or Deal) transfer directly. Rich-text formatting is stripped to plain text to avoid HTML injection issues in Zoho's note viewer. Inline images are extracted as separate file attachments and linked to the same parent record.

GBuilder file attachments are downloaded and re-uploaded to Zoho CRM's file storage. Files over 25MB are flagged for chunked upload or alternative storage (Zoho Drive). The original file URL is stored in Source_File_URL__c for audit reference. Inline images embedded in notes are extracted and rehosted as separate attachments.

GBuilder custom objects map 1:1 to Zoho CRM Custom Modules, available on Professional plan and above. FlitStack creates the Custom Module in Zoho using the _C file-naming convention in the migration package, and the wizard auto-detects and provisions the module. N:N relationships between custom objects become custom junction modules in Zoho.

GBuilder owner/user IDs are resolved by email address against Zoho CRM Users. If a GBuilder owner has no matching Zoho user, their records are assigned to a designated fallback Zoho user and flagged in the migration report. Unmatched owners require Zoho user provisioning before migration or post-migration reassignment.

GBuilder workflows and automations are platform-native and cannot be exported in a transferable format. FlitStack documents every GBuilder workflow trigger, condition, and action as a Zoho Blueprint rebuild specification. Zoho Blueprint uses a state-machine model — your admin configures deal-stage transitions, SLA rules, and notification sequences in the Blueprint designer.