Migrate from Jubilee to Salesforce Sales Cloud

Direct map to Salesforce Contact. Jubilee contacts without a primary company association land against a default placeholder Account; Jubilee's contact-level lifecycle stage and engagement score migrate to custom fields since Salesforce has no native equivalent. The custom fields (Lifecycle_Stage__c, Engagement_Score__c) are created during the schema setup phase, and any unmatched company references are logged for admin review before final insertion.

Jubilee lifecycle stages 'prospect' and 'marketing_qualified' route to Salesforce Lead; 'sales_qualified' and 'customer' route to Salesforce Contact. The split is determined by the final lifecycle value at migration time, preserving the last known stage. Any contact with an 'evangelist' stage is routed to Contact as it represents an established customer advocate. All Lead records receive the Lifecycle_Stage__c custom field populated with the source stage for consistent reporting.

Direct map to Salesforce Account. Jubilee company hierarchies (parent/child) map to Account.ParentId. Multi-company associations on Jubilee contacts collapse to one primary AccountId plus Account Contact Relations for secondary links. If a Jubilee company lacks a parent reference, it becomes a top-level Account; domain information is used to populate the Website field where available. Any circular parent references are flagged for manual resolution before insertion.

Direct map to Salesforce Opportunity. Each Jubilee deal pipeline requires a corresponding Salesforce Record Type so stage pick-list values are scoped correctly. Deal owner resolves via email match to Salesforce User before insertion, and any unmatched owners are assigned to a fallback user. Probability and forecast category are re-applied from the Salesforce stage configuration, and custom fields such as Priority__c and Original_Create_Date__c are populated from the Jubilee record.

Jubilee pipelines become Salesforce Sales Processes keyed by RecordTypeId. Each pipeline needs its own record type with a page layout, stage pick-list values, and validation rules. This is the primary schema step before data lands, allowing every deal to be inserted with the correct RecordTypeId and stage mapping. Admins receive a checklist to create record types, assign page layouts, and define stage sets per sales process.

Stage names map value-by-value per record type, linking each Jubilee stage to the matching Salesforce stage pick-list value. Probability and forecast category are re-applied from Salesforce's stage configuration to keep forecasting accurate. Jubilee stage-entry timestamps are preserved as custom datetime fields (Stage_Entered_Date__c) for reporting continuity. Any Jubilee stages lacking a direct Salesforce match are flagged for admin review and may be consolidated or mapped to a custom stage.

Salesforce has no native lifecycle_stage equivalent, so FlitStack creates Lifecycle_Stage__c as a custom pick-list on both Lead and Contact, populating it with Jubilee's exact stage values. A companion datetime field (Lifecycle_Stage_Updated__c) stores the last transition timestamp, enabling time-based reporting and segmentation. Teams can use these fields in Salesforce Flow or reports to trigger follow-up actions, monitor customer progression, and maintain visibility into the full lifecycle journey after migration.

Jubilee calls and emails map to Salesforce Tasks (Type=Call or Email). Meetings map to Salesforce Events with original start and end times preserved, and any meeting location details are stored in the Event's Location field. Notes map to Salesforce Notes, preserving rich-text formatting where possible. Original timestamps, owner assignments, and any inline file attachments are retained on all activity records to ensure a complete activity history in Salesforce.

Jubilee custom objects map 1:1 to Salesforce custom objects (named with the __c suffix). All fields on the Jubilee object are translated to custom fields in Salesforce, preserving data types where possible. If the Jubilee object uses N:N relationships, FlitStack creates a junction object with two lookup fields and presents the design to the admin for approval, ensuring the schema aligns with business logic.

Jubilee file attachments on records are re-uploaded to Salesforce Files, preserving file name and hash. Salesforce's default file size limit is 25MB per file; larger files are split into chunks or flagged for manual handling and logged for admin action. Inline images in notes are extracted, downloaded, and re-hosted as Salesforce Files, with the note updated to reference the new file URLs. File sharing settings default to the record's visibility.

Jubilee owner IDs resolve to Salesforce User records by email match. Unmatched owners are flagged before migration, allowing the team to invite them to Salesforce or reassign their records to a fallback owner. If a matched user is inactive, FlitStack logs a warning and defaults to the fallback owner to prevent integrity issues. All OwnerId assignments are recorded in the migration audit log.

Jubilee sequences, workflows, and automation rules do not migrate and must be recreated in Salesforce. FlitStack exports all workflow definitions as a JSON reference file that includes trigger conditions, action steps, filter logic, and associated object references. The admin can use this document to rebuild equivalent logic using Flow or Process Builder, prioritizing the critical automations. Any dependencies on custom fields are noted to ensure those fields exist before activation.