Quick Answer: Salentica Elements is built on the Salesforce Lightning Platform — not Microsoft Dynamics 365 (that's Salentica Engage). Migrating from Elements to Salesforce Financial Services Cloud (FSC) is therefore a same-platform transition from a managed package to FSC Core, not a platform switch. Your data already lives in Salesforce, so the project focuses on remapping Elements objects (Relationships, Families, Financial Accounts, Requests) to FSC Core objects (Person Accounts, Households, Financial Accounts, Action Plans), typically over a 3–6 month phased project.
Salentica Elements is a capable, wealth-specific CRM. According to SS&C's own product page, Elements is "highly configurable with a vast integration network," designed for wealth, investment management, and trust fiduciaries — and its foundation is the Salesforce Lightning Platform. Its sibling product, Salentica Engage, is the one built on Microsoft Dynamics 365. Elements is even listed on the Salesforce AppExchange as a Salesforce app requiring Sales Cloud.
So if Elements already runs on Salesforce, why do firms move to Financial Services Cloud? The drivers we hear most often:
None of this is a knock on Elements — it's a question of which foundation fits your firm's next decade. For a broader comparison, see our complete CRM showdown: Salesforce FSC vs. Wealthbox vs. Redtail vs. Orion vs. Practifi.
No — and this is the single most important fact to get right. Because Elements is built on the Salesforce Lightning Platform, an Elements-to-FSC migration is a managed-package-to-core transition inside the Salesforce ecosystem, not a Dynamics-to-Salesforce platform switch.
That distinction changes everything about the project:
By contrast, firms on Salentica Engage (the Dynamics 365 product) face a true platform switch — cross-platform data extraction, process re-mapping, and full user retraining. The phases below still apply, but expect longer timelines and heavier change management.
Elements organizes wealth management data around a specific object hierarchy — documented in Salentica's own knowledge base — and most of it maps cleanly to FSC Core equivalents. FSC models people as Person Accounts and groups them into households using party relationship groups, with a dedicated financial account data model on top.
Here's a practical mapping guide:
| Salentica Elements Object | Salesforce FSC Core Equivalent | Migration Notes |
|---|---|---|
| Relationship (Account) | Business Account / Household | The "main hub" record in Elements becomes the household or business account anchor in FSC. |
| Family | Household (Party Relationship Group) | Elements Families linking multiple Relationships map to FSC household groups and relationship group memberships. |
| Contacts | Person Accounts | Individuals — clients, spouses, professional contacts — become person accounts with account-contact relationships defining their household roles. |
| Financial Accounts | Financial Accounts | Custody and non-custody shell accounts map directly to FSC's Financial Account object. |
| Financial Assets & Liabilities | Assets / Liabilities (Financial Account children) | Holdings, real estate, and debt instruments map to FSC's asset and liability records. |
| Legal Entities | Business Accounts with relationship roles | Trusts, LLCs, and entities with tax IDs become business accounts connected via relationship roles. |
| Portfolios | Financial Account groupings | Portfolio groupings by risk tolerance or reporting need are rebuilt using FSC account hierarchies or custom groupings. |
| Requests (multi-step processes) | Action Plans | Elements' repeatable task/checklist processes map naturally to FSC Action Plans and templates. |
| Activities (calls, tasks, events, emails) | Salesforce Activities | Standard activity objects migrate with dates, owners, and record associations intact. |
| InTouch service levels | Action Plans + Flow automation | Touchpoint frequency tracking is rebuilt with FSC action plans and scheduled flows. |
| Documents & attachments | Salesforce Files | Files attached to Elements records migrate to Salesforce Files with parent record links preserved. |
Two areas deserve extra attention: custodian and portfolio management integrations (Elements' pre-built connections to Schwab, Fidelity, Black Diamond, and others must be re-established or replaced on the FSC side) and historical activity data, which often carries compliance value and should be migrated completely rather than archived.
A well-run migration follows a predictable sequence. Here's the phased approach we use:
Timelines vary with data volume, customization depth, and integration count, but typical ranges look like this:
| Firm Profile | Typical Timeline |
|---|---|
| Small RIA, light customization, few integrations | 8–12 weeks |
| Mid-size wealth firm, moderate customization, several integrations | 3–5 months |
| Large or multi-entity firm, heavy customization, complex integration landscape | 5–8+ months |
The assessment phase alone usually runs 2–4 weeks and is the best investment in the entire project — it's what turns these ranges into a committed plan.
Vantage Point is a boutique Salesforce consulting firm with deep Financial Services Cloud experience across wealth management, RIAs, and family offices. For Elements-to-FSC migrations, our Salesforce implementation and advisory team leads the assessment, data model design, and cutover, while our system integration and data migration practice rebuilds custodian and portfolio management connections on FSC.
Senior consultants only — no junior handoffs; the experts you meet are the experts who deliver. If you're weighing the move, our FSC Core vs. Managed Package migration guide is a useful companion read, and we're happy to walk through your specific Elements configuration in a working session.
Salentica Elements is built on the Salesforce Lightning Platform — it's listed on the Salesforce AppExchange and requires Sales Cloud. Salentica Engage is the separate product built on Microsoft Dynamics 365. SS&C confirms both foundations on its CRM solutions page.
No. Because Elements already runs on Salesforce, migrating to FSC is a managed-package-to-core transition within the Salesforce ecosystem. Your data is extracted with standard Salesforce tools, and users stay in the familiar Lightning interface.
Pre-built integrations — such as Schwab OpenView Gateway and Fidelity Wealthscape connections — are tied to your Elements configuration and must be re-established or replaced on the FSC side. Integration re-planning should be part of the assessment phase, not an afterthought.
Often, yes. Because Elements is a managed package inside your Salesforce org, some firms install FSC in the same org, remap data to FSC Core objects, and retire the package; others prefer a fresh FSC org. Decide during assessment based on your customization footprint and licensing.
Most projects run 3–6 months. Small firms with light customization can finish in 8–12 weeks; large or heavily customized firms with complex integrations should plan for 5–8 months or more.
Yes. Calls, tasks, events, and emails stored in Elements are standard Salesforce activity records and migrate with dates, owners, and record associations intact. Given their compliance value, historical activities should be migrated completely rather than archived.
Elements migrations stay within Salesforce — no platform switch. Engage is built on Microsoft Dynamics 365, so moving from Engage to FSC is a true cross-platform migration with separate data extraction, process re-mapping, and fuller retraining.
Migrating from Salentica Elements to Salesforce Financial Services Cloud is one of the more approachable CRM transitions a wealth management firm can take on — you're modernizing within a platform your team already knows. The firms that succeed treat it as a data model and adoption project, not just a data move.
If you're evaluating the switch, start a conversation with Vantage Point. We'll review your Elements configuration, outline a phased plan, and give you an honest read on scope and timeline.
Vantage Point is a boutique CRM consulting firm helping businesses transform with Salesforce, HubSpot, and AI. With 150+ clients across 400+ engagements and an average engagement rating of 4.71/5.0, our senior-only, employee-owned team delivers Salesforce Financial Services Cloud implementations, integrations, data migrations, and managed services. Learn more at vantagepoint.io.