Migrate from Jubilee to Microsoft Dynamics 365 Sales

Jubilee contact records map directly to Dataverse Contact. Dynamics 365 requires AccountId on most contact views — contacts without a primary company land on a placeholder account or require Account creation in the same migration batch. Standard fields like name, email, phone, and address transfer as‑is, and custom attributes are written to custom columns on Contact. We verify email uniqueness and flag duplicates before insert to avoid duplicate Contact rows.

Jubilee company records map to Dataverse Account. If Jubilee supports parent‑company hierarchies, the top‑level company migrates as Account, and child companies map to ChildAccounts via ParentAccountId lookup — circular references are flagged before the run. Standard fields (name, domain, industry, address) transfer as‑is, and any custom attributes are written to matching custom columns on Account. Each Account owner is resolved by email match to a SystemUser before insert.

Jubilee deal records map to Dataverse Opportunity. Each Opportunity requires AccountId — deals without a linked company are attached to a default account and flagged for review. Pipeline stage in Jubilee maps to the Opportunity StageName pick-list; if Jubilee stages don't match Dynamics stages exactly, we apply a value-mapping table during migration.

Jubilee custom fields stored as extended attributes are enumerated via API. We create matching custom columns in Dataverse (prefixed with new_ by default) before migration begins. The field type is inferred from Jubilee's type metadata — text, number, date, pick-list — and the closest Dataverse type is applied. Pick-list fields require a separate value-mapping step for each option.

Jubilee N:N contact-company associations map to Dataverse AccountContactRelation. We create one primary relation (IsPrimary: true) per contact and surface secondary associations in the same table. If Jubilee supports multiple association roles (e.g., Decision Maker, Influencer), those roles are stored in a custom column on AccountContactRelation since the built-in Dynamics roles table has a limited schema.

Jubilee email activities map to Dataverse Email records with Regarding lookup pointing to the source contact or deal. Email body, subject, from/to addresses, and sent/received timestamps are preserved. Attachments are extracted and re-uploaded to Dataverse notes or SharePoint document management based on your Dynamics configuration.

Jubilee call, meeting, and note records map to their Dataverse equivalents. Call duration and outcome are stored in custom columns on PhoneCall. Meeting start/end times and location map to Appointment fields. Free-form notes map to Dataverse Annotation (Notes) with the Regarding lookup set to the parent contact or deal.

If Jubilee stores product line items directly on deal records, we split them into separate OpportunityProduct records in Dataverse. Product lookup requires an existing Product (or msdyn_product) record — we create placeholder products during migration if the source product catalog is not separately exported, then link OpportunityProducts to those placeholders.

Jubilee owner IDs are resolved by email against Dynamics 365 SystemUser records. Matches are written as OwnerId on migrated records. Owners with no matching email are flagged in the pre-flight report — your Dynamics admin either invites them to the tenant or assigns their records to a fallback owner before the migration runs.

Jubilee file attachments on contacts, companies, and deals are downloaded and re-uploaded to Dynamics 365. By default, files are stored as Dataverse Notes attachments. If your Dynamics environment uses SharePoint document management, we create SharePoint Document Location records and store files in the configured document library.

Jubilee workflows execute in Jubilee's own automation engine and are not exposed as exportable configuration. We cannot migrate them. We export a JSON manifest of your active workflows (trigger events, conditions, actions) as a rebuild reference. Your Dynamics admin uses that manifest to recreate equivalent logic in Power Automate or Dynamics workflows.

Jubilee reports built on Jubilee data are not portable. The underlying data migrates — your reports in Dynamics will reference the same fields with different names. We provide a field-mapping cross-reference document so your analytics team can rebuild reports against the new Dynamics schema. Custom charts or visualizations built in Jubilee's report builder must be recreated in Power BI or Dynamics.