Migrate from GBuilder to Salesforce Sales Cloud

GBuilder contacts migrate directly to Salesforce Contacts. The Salesforce Contact requires an AccountId (lookup to Account) — contacts without a primary company in GBuilder are attached to a default 'Unassigned Account' record, or your admin specifies a default mapping rule.

GBuilder company records map 1:1 to Salesforce Accounts. Company hierarchies (parent/child construction firms) map to the Account.ParentId field. Multi-company contacts that GBuilder allows natively collapse to one primary AccountId in Salesforce plus Account Contact Relationships for secondary affiliations. This maintains proper hierarchical relationships in the target system.

GBuilder projects can map to Salesforce Opportunities if the project pipeline mirrors a sales process (estimate → proposal → won/lost). For construction-specific projects with phases and cost codes, FlitStack creates a custom Project__c object with Phase__c child records. Your admin chooses the architecture before migration validates.

GBuilder phases (Pre-Construction, Design, Procurement, Construction, Closeout) map to a custom Phase__c child object on Project__c if a custom object is used, or to Opportunity Stage values if Projects migrate as Opportunities. Each phase carries its own start date, end date, and status — these become Salesforce custom fields.

GBuilder tasks migrate as Salesforce Tasks. Original timestamps, assigned owners (resolved by email), and parent-record links (WhatId for projects, WhoId for contacts) are preserved. Large task volumes may require Bulk API batching on the Salesforce side to handle the data volume efficiently and avoid API limits.

RFIs have no Salesforce standard equivalent. FlitStack creates an RFI__c custom object with fields for RFI number, subject, status, priority, due date, and linked Project__c. RFI responses migrate as Notes or as a custom Response__c child object depending on your admin's preferred schema.

Submittals track specification compliance for materials and equipment. A custom Submittal__c object maps submittal number, specification reference, status, submitted date, and approved date to Salesforce custom fields, linked to Project__c or Opportunity as the parent record. This preserves the full audit trail of submittal approvals.

GBuilder file attachments (drawings, PDFs, BIM models) are downloaded and re-uploaded to Salesforce Files. The ContentDocumentLink ties each file to its parent Project__c or Contact record. CAD files and large BIM model archives may exceed Salesforce's 25MB per-file default — FlitStack batches large files and flags any that require manual re-upload.

GBuilder custom fields for CSI division codes, cost codes, BIM coordination flags, and union compliance data have no Salesforce standard equivalent. FlitStack creates Salesforce custom fields (CustomField__c) with appropriate types — pick-list for codes, text for flags, currency for cost fields — and maps values value-by-value.

GBuilder user IDs are resolved by email against Salesforce users. Unmatched owners are flagged before migration so your team can either invite them to Salesforce first or assign their records to a fallback owner. No record lands in Salesforce without a resolved OwnerId.

GBuilder project estimates and budgets map to Opportunity.Amount if projects migrate as Opportunities, or to a custom Estimated_Value__c currency field on Project__c. Original estimate vs. final cost variance is preserved in a separate field for reporting. This enables accurate financial tracking and variance analysis post-migration.

GBuilder logged calls and emails migrate as Salesforce Tasks (Type = 'Call' or 'Email'). Meetings migrate as Salesforce Events with original start/end times. Activity timestamps and owner assignments are preserved. GBuilder's internal notes on activities migrate as Salesforce Notes. This maintains complete activity history and communication records.