Migrate from Uptick to Salesforce Sales Cloud

Uptick Company maps directly to Salesforce Account. Company name, phone, address, website, and industry fields migrate as Account.Name, Phone, BillingAddress, Website, and Industry. Parent-child company hierarchies in Uptick map to Salesforce ParentId on Account, preserving the organizational structure. Uptick internal record IDs are stored as Source_System_ID__c custom fields on each Account for traceability and delta-run de-duplication. This direct mapping preserves the full company entity with all standard address and contact information intact.

Uptick Contact maps to Salesforce Contact with AccountId as the required parent lookup. Salesforce requires each Contact to have an AccountId — contacts without a primary company in Uptick attach to a default 'Unassigned Account' record or the Account representing the property owner. Email addresses serve as the primary matching key for duplicate detection during migration, and all standard contact fields (name, phone, title, address) migrate directly to their Salesforce equivalents.

Uptick Locations (physical properties with addresses where assets sit) have no direct Salesforce equivalent. We map Locations to a custom Location__c object or as address-specific Account records, depending on whether you need site-level reporting. Original Uptick location ID preserved as Source_System_ID__c for delta-run de-duplication. This custom object strategy preserves the site-level hierarchy essential for fire protection compliance reporting.

Uptick Asset maps to Salesforce Asset with custom fields for service history. Standard Salesforce Asset tracks installed product but not service-visit history — we create a custom Asset_Service_History__c object linked via AssetId to preserve inspection dates, technician, and work-order outcome for each asset visit. This ensures fire protection compliance audit trails are fully migrated, not truncated to the most recent service event.

Uptick Work Orders have no native Salesforce equivalent with equivalent dispatch semantics. We map to Salesforce Case with custom fields (Scheduled_Date__c, Technician__c, Work_Order_Status__c, Line_Items__c) to preserve the operational state. Alternatively, a custom Work_Order__c object provides full parity but requires a custom tab and page layout. The mapping preserves scheduled visit dates, technician assignments, and completion notes critical for field-service continuity.

Uptick Quotes map to Salesforce Opportunities with custom Quote fields. Salesforce's native Opportunity does not include quote line items without CPQ — we map quote headers to Opportunity and line items to a custom Quote_Line_Item__c object linked via OpportunityId. CPQ can be layered post-migration if needed. This transformation preserves the full quote-to-opportunity conversion workflow from Uptick.

Uptick Invoices require a custom Invoice__c object because Salesforce Billing Cloud is not included in base Sales Cloud. We preserve invoice number, date, amount, status, line items, and payment history as a custom object linked to the Account. Post-migration, Salesforce Billing or a third-party billing integration replaces this workflow. This ensures historical invoice data is available for reporting even without native billing functionality.

Uptick Products map to Salesforce Product2 records with the cost/sell price preserved as standard pricebook entries. Product types (Material M, Labor R, Equipment E, Subcontracted S, Expense X) migrate as a custom Product_Type__c pick-list on Product2. Estimated labor time in minutes migrates as Estimated_Labor_Minutes__c for service-visit planning. Pricebook entries are created against the standard Pricebook2, with custom pricebooks available post-migration for territory-specific pricing.

Uptick Employees and Technicians do not have a Salesforce equivalent as contacts. We match Uptick employee email addresses to Salesforce Users by email. Unmatched employees are flagged before migration — your team provisions Salesforce User accounts for them, or we assign their records to a fallback Owner. Technician location and shift assignments migrate as custom fields on the User record. This resolution step is mandatory before Case OwnerId can be populated.

Uptick file attachments on assets, work orders, and quotes re-upload to Salesforce Files (ContentDocument / ContentVersion). File size limits per Salesforce apply (25MB default per file). Photos from work order defect reports download and re-host under the corresponding Case or custom Work_Order__c record. Files are linked to the parent record via ContentDocumentLink to maintain the original attachment relationships.

Uptick notes and task checklists map to Salesforce Notes and Tasks linked to the parent record (Account, Contact, or Case). Original timestamps and author preserved. Uptick task status (pending/complete) maps to Task.Status. Activity history that predates the migration retains its creation date as a custom Original_Create_Date__c field since Salesforce sets CreatedDate at migration time. This preserves the complete audit trail for compliance and customer relationship history.

Uptick custom fields on any object require Salesforce custom fields (suffix __c) created before migration. FlitStack delivers a schema setup plan listing every Uptick custom field, its Salesforce data type, and the target object. Salesforce pick-list fields require value-by-value mapping when pick-list options differ between platforms. The schema plan includes page layout assignments so your Salesforce admin can configure visibility and editability for each custom field before data loads.