Migrate from The Customer Factor to Salesforce Sales Cloud

The Customer Factor's flat Customer record merges into two Salesforce objects: Account (from the company name and address in TCF) and Contact (from the contact name and email). The primary company in TCF becomes Account.Name; the contact name becomes Contact.FirstName and Contact.LastName. This is mandatory because Salesforce requires AccountId on Contact and OpportunityContactRole on Opportunity.

The Customer Factor Prospect object maps directly to Salesforce Lead. TCF Prospect fields (name, email, phone, notes) map to standard Salesforce Lead fields (Name, Email, Phone, Description). Prospect status from TCF migrates as a custom pick-list field (TCF_Prospect_Status__c) since Salesforce Lead Status is a separate pick-list with its own values.

The Customer Factor Estimate has no direct Salesforce equivalent. FlitStack maps Estimates to Salesforce Opportunities using the estimate name as Opportunity Name, estimate amount as Amount, and TCF-specific fields (scheduled date, technician, job type, tax) as custom Opportunity fields. If your team uses Salesforce CPQ, the same estimate data can alternatively populate Quote objects.

TCF estimate line items map to Salesforce OpportunityLineItems when CPQ is in scope. The line item description, quantity, and unit price map to OpportunityLineItem Description, Quantity, and UnitPrice respectively. Without CPQ, line item details are stored as custom fields on the Opportunity record.

Salesforce has no native invoicing object. FlitStack creates a custom Invoice__c object to preserve TCF invoice records with fields for invoice number, date, amount due, amount paid, balance, payment status, and payment method. Active recurring billing logic from TCF does not migrate — CPQ or Salesforce Revenue Cloud handles that post-migration.

TCF notes on customers and estimates map directly to Salesforce Notes. Note Title becomes Note Title; Note Body becomes Note Body. Notes are linked to the parent Contact or Opportunity record via the ParentId field. Rich-text formatting in TCF notes is preserved as plain text in Salesforce Notes.

TCF file attachments re-upload to Salesforce Files (ContentDocument model). Each file is linked to its parent record (Contact, Account, or Opportunity) via ContentDocumentLink. Salesforce's 25MB per-file limit applies; files exceeding this are flagged before migration so your team can split or compress them.

TCF staff member records (technicians, account managers) resolve to Salesforce Users by email address match. Unmatched users are flagged before migration — your team either creates Salesforce User accounts for them first or assigns their records to a fallback owner. TCF role or title data migrates as a custom field on the User record.

Any custom fields created within The Customer Factor migrate as Salesforce custom fields on the corresponding object (custom fields on Customer → custom fields on Contact; custom fields on Estimate → custom fields on Opportunity). Custom field data type is preserved where possible — text, number, date, and pick-list types map directly. TCF's custom field API names are stored in the migration field map for traceability.

TCF recurring billing or subscription setups do not have a direct Salesforce CRM equivalent. FlitStack does not attempt to map this data — it is documented in the migration plan as a post-migration item requiring Salesforce CPQ or Revenue Cloud configuration. Historical subscription records can be imported as Invoice__c records for reporting continuity.