Migrate from Lead Perfection to Salesforce Sales Cloud

Lead Perfection's Prospect object maps directly to Salesforce Lead. Lead status values (New, Contacted, Qualified, etc.) map to Salesforce Lead Status via value mapping. Original Prospect create date preserved as a custom datetime field since Salesforce CreatedDate reflects migration time.

Lead Perfection Contact maps to Salesforce Contact. Requires AccountId — contacts without a primary company link to a default 'Unassigned Account' record or your admin pre-creates placeholder accounts. Email match resolves owners where available. If the Contact's email matches a Salesforce User, that User becomes the OwnerId; otherwise, the fallback owner is assigned. The original Contact create date is stored in a custom datetime field.

Lead Perfection Company maps to Salesforce Account. Company hierarchies (parent/child) map to Account.ParentId. Multi-contact companies get primary contact flagged via Account Contact Relationships in Salesforce. If the company has multiple locations, each location can be represented as a separate Account with a shared ParentId to preserve regional hierarchy. The original Company create date is stored in a custom datetime field.

Lead Perfection's appointment records become Salesforce Events. The timeslot-based availability model does not translate natively — each appointment generates one Event with original start/end times, assigned sales rep as OwnerId, and linked Contact or Lead. Slot availability logic must be rebuilt in Salesforce Flow or a scheduling app.

Lead Perfection's Sales Rep records resolve to Salesforce User objects by email match. Territory assignments and availability preferences do not map — they become Salesforce custom fields or are rebuilt using Salesforce's territory management tools post-migration. Unmatched Sales Reps are flagged for manual user creation before the final migration run, ensuring every record has an OwnerId.

Lead Perfection Job records — which track the estimate-to-installation lifecycle — map to a Salesforce Opportunity for the commercial stage and a custom Job__c object for installation tracking. The opportunity name, amount, and stage reflect the commercial transaction; Job__c stores trade-specific fields like material type, measurements, and installation crew assignment.

Lead Perfection's lead source values (Website, Referral, Door Knocker, etc.) map to Salesforce LeadSource picklist values. Trade-specific sources that don't match Salesforce defaults become custom picklist values on the Lead object. These custom picklist values are added to the Lead object's LeadSource field in Salesforce, and the original Lead Perfection source is preserved in a custom field for reference and reporting.

Lead Perfection territory definitions by zip code require a custom Territory__c object or zip-code-based custom field on Account. Salesforce's native territory management requires Enterprise territory account assignment — your admin chooses the implementation approach. If you opt for the Territory__c object, each territory record includes the zip code range and assigned sales rep, with a lookup field on Account to link customers to their coverage area.

Lead Perfection custom fields for industry-specific data (window measurements, material type, permit status, installation crew) migrate as Salesforce custom fields with __c suffix on the corresponding object. Custom fields on non-standard objects require custom object creation in Salesforce. Each migrated field retains its original data type and any picklist constraints, and the original Lead Perfection field label is stored in a reference field for audit purposes.

Lead Perfection file attachments on prospects, contacts, or jobs re-upload to Salesforce Files. File size limits apply (Salesforce default 25MB per file). Inline images in notes are downloaded and rehosted in Salesforce's file storage. All migrated files retain their original file name and content hash for integrity verification, and are linked to the corresponding record via the ContentDocumentLink object.

Lead Perfection's internal record ID is stored as Source_System_ID__c on each migrated record. This enables delta-run de-duplication, cross-referencing during reconciliation, and audit traceability back to the original Lead Perfection entry. The Source_System_ID__c field also supports future integrations, allowing other systems to reference the original Lead Perfection identifier without re-entry, and facilitates rollback scenarios by mapping records back to their source state.