Migrate from Lead Perfection to Nutshell

Lead Perfection's Prospect records map to Nutshell Person records flagged as Lead status. The Person's name, email, and phone pull from the Prospect's contact fields. Lead source attribution (Source + SubSource) migrates as custom fields since Nutshell's native lead_source is a fixed pick-list.

Lead Perfection's Job is a flat record combining customer contact info, address, phone types, lead source, and sales rep assignment. FlitStack splits each Job into a Nutshell Person (contact details) and a Nutshell Deal (the opportunity). The Job ID is preserved as Source_System_ID__c on both records for traceability.

Job Address fields (line_1, city, state, postal_code) map to the Nutshell Person's address fields. Lead Perfection's line_2 field, if populated, stores in a custom field since Nutshell Person has a single-line address model. If the line_2 contains apartment, suite, or floor information, the custom field retains this detail so your team can locate the property without losing context during the migration.

Lead Perfection allows multiple phone entries per Job, each with a type label (primary, AltPhone1, AltPhone2, etc.). The primary phone maps to Nutshell's standard phone field. Additional phones populate Nutshell custom fields named Additional_Phone_1__c and Additional_Phone_2__c with the type preserved as a label prefix.

Each Lead Perfection Appointment (with summary, notes, start_time, end_time) migrates as a Nutshell Activity of type 'Meeting' tied to the corresponding Person record via the Job's original contact. Original start/end times are preserved. Appointments without a linked contact are flagged for manual review before migration.

Lead Perfection Notes attached to Jobs migrate as Nutshell Activity records of type 'Note' on the corresponding Person. The note body and any linked appointment context are preserved in the Activity description field. During migration, any timestamps associated with the original note (such as created date) are also stored in custom fields on the Activity, ensuring full audit history is available in Nutshell for compliance and follow-up tracking.

Lead Perfection's SalesRep records (name, email) are resolved against Nutshell users by email address. Any Lead Perfection sales rep without a matching Nutshell user is flagged during the planning phase — the team either creates the Nutshell user first or assigns records to a designated fallback owner before migration runs.

Lead Perfection captures lead origin in two fields — Source (e.g., 'Website', 'Referral') and SubSource (e.g., specific campaign or partner). Nutshell's native lead_source is a single pick-list with limited values. FlitStack creates a custom field 'Lead_Source__c' in Nutshell and concatenates Source + SubSource with a delimiter so both data points are preserved.

Lead Perfection custom fields on Jobs (industry-specific data like 'Job Type', 'Product Category', 'Estimate Amount') are created as Nutshell custom fields on the target object (Person or Deal depending on the field's purpose). Field type is matched to the closest Nutshell equivalent — text, number, date, or pick-list.

Lead Perfection's Sales Rep Scheduling module — timeslot definitions, zip-code coverage areas, availability rules — has no Nutshell equivalent. This module does not migrate. Teams that rely on this scheduling logic need to implement a third-party scheduling tool (Calendly, HubSpot Meetings) post-migration and re-enter availability rules.

Lead Perfection workflows (automatic lead routing, assignment rules, follow-up triggers) do not migrate. Nutshell has its own automation tools for sequences and task creation. FlitStack exports Lead Perfection workflow definitions as a reference document so the admin can rebuild rules in Nutshell after migration.