Skip to content

Migration guide · Wealth & Advisor CRM

Junxure (AdvisorEngine) to Salesforce migration

Junxure / AdvisorEngine CRMSalesforce Financial Services Cloud

Short answer

Migrating from Junxure or AdvisorEngine CRM to Salesforce Financial Services Cloud moves contacts, households, notes, activities and workflows into FSC, so firms on a retired or legacy advisor CRM get a platform with stronger automation, reporting and integrations.

Why firms make this move

AdvisorEngine retired the Junxure brand, and many firms still run on it or its successor CRM. Moving to FSC is a chance to clean up years of history and connect custodians and portfolio systems properly. Vantage Point has migrated Junxure data for wealth firms, including programs that combined several acquired firms' CRMs into one Salesforce org.

What moves

  • Contacts and households
  • Notes and activities with original dates
  • Workflows and service history
  • Custom fields and categories
  • Documents where available

How the data maps

FromTo
ContactPerson account or contact
HouseholdHousehold account
Action / activityTask or event
NoteNote
WorkflowAction plan, case or flow

See the field-by-field map ↓

What to watch out for

  • Export formats and access to the legacy database
  • Inconsistent household data
  • Duplicate records from acquisitions
  • Legacy history that is not worth moving

How Vantage Point runs the migration

  1. Discovery and data inventory: what exists, what is clean, what is worth moving
  2. Target design: objects, record types, households or companies, ownership and security
  3. Field-by-field data mapping document, signed off by business owners
  4. Cleanup and deduplication before the move, not after
  5. Test loads into a sandbox with reconciliation reports
  6. User acceptance testing with real scenarios
  7. Cutover: final delta load, integrations switched, old system set to read-only
  8. Hypercare and adoption support

Typical timeline

Typically 6 to 12 weeks, longer when several acquired firms' data is combined.

Frequently asked questions

Can we bring over history from acquired firms too?

Yes. Multi-source migrations are run in waves with a shared mapping and deduplication rules.

What if our Junxure data is messy?

That is common. Cleanup and deduplication happen before the load, guided by rules you approve.

Last reviewed October 2, 2026 by the Vantage Point team. Browse all migration paths →

Field-level map

Junxure (AdvisorEngine) to Salesforce: field by field

10 mappings we start from on this migration, 7 of which need a transform, a lookup or a decision. Every project gets its own signed-off version; this is the baseline.

FromToHowNotes
Junxure contact (individual)Name, birth date, contact details Person AccountFirstName / LastName / PersonBirthdate req direct
Junxure contactExtra emails, phones, addresses Person AccountPrimary fields + Contact Point records split
Junxure householdHousehold Account (Household record type)Name req direct
Junxure household memberRelationship / role Account Contact RelationshipRoles req association
Junxure contactType / status / category Person AccountClient category and status fields picklist map
Junxure contactAdvisor / owner Person AccountOwnerId req lookup
Junxure activitiesTasks, meetings, notes Task / Event / ContentNoteSubject, dates, associations association
Junxure accountsFinancial accounts Financial AccountAccount number, type, balance manual review Usually replaced by a custodian or portfolio-system feed.
Junxure custom fieldsCustom fields Custom fields— manual review Keep only fields someone still uses.
Junxure recordSource ID Person Account / AccountLegacy_ID__c (external ID) req direct

Field names are the platforms' standard API names; your org's custom fields are mapped during discovery. What the "How" labels mean

How labels
direct
Value copies across unchanged.
picklist map
Each source value is mapped to a target value.
lookup
Matched to an existing record, such as a user by email.
association
Becomes a relationship between records, loaded in a later pass.
derive
Calculated or cleaned during the load.
split / concat
One field becomes several, or several become one.
rebuild
Configuration or automation that is rebuilt rather than moved.
drop
Not migrated, deliberately.
manual review
Needs a decision with your team before the load.