Migrate from FastTrack to Nutshell

FastTrack Person maps directly to Nutshell People. Nutshell People store name, email, phone, address, and custom fields. FastTrack person properties that do not have a direct Nutshell equivalent become custom fields on the People record. All FastTrack person timestamps and owner assignments migrate with original values preserved.

FastTrack Company maps to Nutshell Company. Company name, domain, industry, employee count, and revenue map directly to Nutshell Company fields. FastTrack company hierarchies (parent-child relationships) map to Nutshell Parent Company field. FastTrack custom company properties migrate as Nutshell custom fields.

FastTrack Lead maps to Nutshell Lead. Nutshell Lead includes status, source, and assignment fields. FastTrack lead score or rating properties migrate as a Nutshell custom field. FastTrack lead custom properties map to Nutshell Lead custom fields. Owner assignment resolves by email match against Nutshell users.

FastTrack Deal maps to Nutshell Deal. Nutshell Deal includes name, amount, stage, probability, close date, and owner. FastTrack deal properties migrate as Nutshell Deal custom fields. Stage names map value-by-value to Nutshell stage names. Pipeline association in FastTrack maps to Nutshell Deal's linked Company and assigned user.

FastTrack event logs (calls, emails, meetings) map to Nutshell Activities. Call logs migrate as Nutshell Tasks with type='Call'. Email logs migrate as Nutshell Tasks with type='Email'. Meetings migrate as Nutshell Events with start/end times and linked person or deal. Original timestamps and owner links are preserved.

FastTrack notes map to Nutshell Notes. Notes attached to specific records (people, companies, deals) link to the corresponding Nutshell record by ID. Rich-text formatting in FastTrack notes is preserved as HTML in Nutshell notes. Note create and update timestamps migrate with original values.

FastTrack custom objects require transformation. If the FastTrack custom object represents a property of an existing Nutshell object (Person, Company, Lead, Deal), the data migrates as a Nutshell custom field on that object. If the FastTrack custom object has a many-to-many relationship, we create a junction record in Nutshell linking the two related objects. The mapping plan is delivered before migration runs.

FastTrack users migrate by email match against Nutshell users. Active FastTrack users who have a corresponding Nutshell account (matched by email) retain their assignments. FastTrack users without a Nutshell match are flagged before migration — your team either creates Nutshell accounts for them or reassigns records to a fallback owner.

FastTrack file attachments on records migrate as file attachments in Nutshell. Files are downloaded from FastTrack and uploaded to Nutshell's storage. File size limits apply (Nutshell supports standard file sizes). Inline images in rich-text fields are downloaded and rehosted as Nutshell file attachments.

FastTrack workflows and sequences do not migrate. These automation constructs have no equivalent in Nutshell's data model and must be rebuilt manually in Nutshell or using Nutshell's automation tools. We export FastTrack workflow definitions as a structured JSON reference to assist your team in the rebuild.

FastTrack integrations (connected apps, third-party data sources, webhook endpoints) do not migrate. Each integration must be reconfigured in Nutshell's AppConnect marketplace or rebuilt using Nutshell's API. We document your active FastTrack integrations as part of the discovery phase and provide a rebuild checklist that maps each connection to its Nutshell equivalent.

FastTrack reports and dashboards do not migrate. The underlying data migrates, but report definitions are platform-specific. We recommend rebuilding key reports in Nutshell after migration using the migrated data. Nutshell's native reporting tools support standard pipeline, activity, and performance reports that can be configured based on your migrated records.