A 360view-to-FSC migration is a schema translation project: freeze the FSC household and person model first, migrate only 360view-native data, and re-sync core data separately.
A technical guide to migrating from 360view CRM to Salesforce FSC — covering object mapping, household transformation, load order, and compliance checks.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
Do not migrate every visible balance, product field, and transaction shadow out of
Do not migrate every visible balance, product field, and transaction shadow out of 360view just because users can see it there. If the authoritative source is the core, move the relationship context and historical CRM interaction data, then let the new core-to-Salesforce integration repopulate current balances and product facts. That reduces stale-data risk and makes reconciliation simpler.
Enabling Person Accounts in Salesforce FSC is an irreversible decision that fundamentally
Enabling Person Accounts in Salesforce FSC is an irreversible decision that fundamentally alters the org's data model. Validate this against your full B2B and B2C scope before raising a Salesforce support case to enable it.
If you are torn between migrating a field and re-sourcing it from core, default to
If you are torn between migrating a field and re-sourcing it from core, default to re-sourcing from core unless there is a hard business reason not to. CRM migrations fail when teams move too much duplicated operational data and then spend weeks reconciling copies instead of mastering one authoritative feed.
Do not skip the pilot load
A single branch validates your entire transformation pipeline — field mappings, relationship linking, and load order — before you risk production data for the whole institution.
Salesforce can preserve audit fields such as CreatedDate during insert when you enable
Salesforce can preserve audit fields such as CreatedDate during insert when you enable the right permissions, but Salesforce does not allow importing Field History Tracking records. If you need pre-Salesforce change history for audit or regulator response, archive it outside standard field history or store it in a separate immutable structure.
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Agree scope, pipeline design and success criteria before touching data.
Objective A scope covering every object in the revenue model, with sales leadership signed up to the pipeline design.
Keep these open
-
Inventory every object in 360 View CRM
Count accounts, contacts, leads, deals or opportunities, activities, notes, emails, files, products and quotes. Activity and email history is usually the largest object by an order of magnitude and the one people forget to size.
Data Profiler Get real record counts instead of estimating from memory -
Map the current pipeline and agree the target model
Document every pipeline, stage, probability and required field, then agree the Salesforce model with sales leadership. Migrating a broken pipeline faithfully is a wasted opportunity; redesigning it mid-migration is a wasted migration.
Stage changes alter historical conversion rates. Agree how you will restate reporting before you change the model.
-
Catalogue integrations and automation
List every system touching 360 View CRM: marketing automation, quoting, billing, ERP, data enrichment, dialler, BI. Each is a separate cutover task with its own owner, and each can silently write bad data into your new CRM.
-
Capture the reporting that must survive
Interview the people who actually live in the dashboards — forecast, pipeline coverage, rep activity, cohort conversion. Every one of these needs the underlying fields to migrate, which frequently expands the scope.
-
Build the business case and pick the go-live date
Model licence delta, implementation effort and productivity dip. Then choose the date deliberately: mid-quarter is disruptive, quarter-end is worse. Most teams land on the first week of a new quarter.
COI & ROI Calculator Build the 36-month business case you will need for sign-off
360 View CRM → Salesforce specifics
- Which FSC household model are you using?
- Managed-package Household Account or standard Groups and Households?
Don't move on until
- Object counts confirmed for accounts, contacts, deals and activities
- Target pipeline and stage model agreed with sales leadership
- Reporting requirements captured from the people who use the reports
02 Data Audit CRM data is usually dirtier than anyone expects. Find out how dirty.
Objective A profiled export with duplicates, ownership gaps and relationship integrity all quantified and triaged.
Keep these open
-
Export and profile every object
Profile null rates, distinct values and type consistency across all objects. Pay attention to fields sales reps were supposed to fill in: an 80% null rate on a field your forecast depends on is a business finding, not a data one.
Data Profiler Profile the 360 View CRM export for nulls, outliers and type drift -
Quantify duplicates and agree the merge policy
Measure duplicate accounts (same company, different spellings and suffixes) and contacts (same email, or same person at a renamed company). Agree survivorship rules before merging: which record wins, which fields, and what happens to the activity history on the loser.
Merging before you have agreed survivorship rules destroys history irreversibly. Decide first, merge second.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Verify relationship integrity
Check every deal has a valid account, every contact a valid account, every activity a valid parent. Referential breaks are the defect that turns a clean-looking load into a CRM where the pipeline report does not tie to the account list.
-
Resolve ownership and the user map
Build the 360 View CRM user → Salesforce user map, including leavers. Every record needs a valid owner: records assigned to deactivated users either fail to load or land unassigned, and unassigned pipeline is pipeline nobody works.
Records owned by deactivated users are a top cause of load failures. Decide the reassignment target before you start.
-
Scan for PII and regional compliance
CRMs hold marketing consent, lawful basis and unsubscribe state. Confirm these fields migrate intact and that consent provenance survives — losing consent records is a regulatory problem, not a data-quality one.
PII & Compliance Scanner Find regulated fields before they land in a new system -
Clean, normalise and archive the pre-state
Normalise country and state values, phone formats, currencies and casing, and standardise all timestamps to UTC. Keep an untouched copy of the raw export — it is your only reference if a mapping decision turns out wrong.
Don't move on until
- Duplicate rate quantified per object with a merge policy agreed
- Every record has a valid owner mapped to a target user
- Relationship integrity verified — no orphaned deals or contacts
03 Field Mapping Map objects, relationships and picklists — in that order.
Objective A signed mapping spec that covers objects, relationships, picklist values and currency handling.
Keep these open
-
Map objects and their relationships first
Establish how 360 View CRM objects correspond to Salesforce objects before any field work. Leads-versus-contacts, accounts-versus-organisations and deal hierarchies differ structurally between CRMs, and a field map built on the wrong object model has to be redone.
Schema Mapper Opens pre-loaded with the 360 View CRM → Salesforce field pair -
Generate and then hand-review the field map
Auto-match both schemas, then review every row. Look hardest at anything named "type", "source", "stage" or "status", where names match and meanings do not.
-
Map every picklist value, including retired ones
Enumerate all values on both sides — deal stages, lead sources, industries, statuses — and map each explicitly, including values no longer offered but still present on old records. Unmapped values either fail the row or land as blanks that quietly break segmentation.
Historical records often carry picklist values that were retired years ago and no longer appear in the UI.
-
Decide currency, amount and date handling
If you sell in multiple currencies, confirm how Salesforce stores amounts, exchange rates and dated conversion rates. Recalculating historical deal values at today's rate silently rewrites your revenue history.
Multi-currency deals re-converted at current rates will not tie to your historical reporting or your finance system.
-
Determine the load order
Sequence the load so parents exist before children: users, then accounts, then contacts, then deals, then activities and notes. Keep source IDs in custom fields so relationships can be rebuilt by lookup rather than guesswork.
-
Freeze the spec and sign off
Version-control the mapping, walk RevOps and sales leadership through the decisions that change reporting, and get written sign-off before the pilot.
Don't move on until
- Object and relationship model mapped and reviewed
- Every picklist value explicitly mapped, including dead values
- Load order determined so parents always exist before children
04 Test Migration Pilot with related records, not a flat sample.
Objective A pilot load whose relationships, ownership and roll-up reporting all verify against source.
Keep these open
-
Configure the Salesforce sandbox to match the agreed model
Build the pipelines, stages, custom fields, record types and user roles first. Load into a default configuration and you will only discover the configuration defects at full scale.
-
Select a connected pilot slice
Take complete account trees — 50-100 accounts with all their contacts, deals, activities and files — rather than a flat random sample. Relationship defects are the whole point of a CRM pilot and a flat sample cannot expose them.
-
Run the load in dependency order with full logging
Load users, accounts, contacts, deals, then activities, logging every request against its source ID. Note which failures are transient (rate limits, timeouts) and which are structural (validation, missing parent).
-
Verify relationships and roll-ups
Confirm every deal sits on the right account with the right owner and stage, and that pipeline totals per account and per rep match 360 View CRM exactly. Roll-up mismatches almost always mean a relationship or currency defect upstream.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Measure throughput and project the full load
Record actual records-per-hour under Salesforce's API limits and extrapolate, remembering activity history usually dominates volume. If the projection exceeds your window, split the load or trim activity scope now.
-
Let reps work the pilot data
Put two or three reps in the sandbox against their own accounts. They spot missing context, wrong owners and unusable notes far faster than any reconciliation script, and their buy-in is what makes adoption work.
Don't move on until
- Relationships intact across the whole pilot slice
- Pipeline roll-ups match source for the pilot accounts
- Reps have worked pilot records and confirmed they are usable
05 Cutover Switch the revenue system with the pipeline intact.
Objective All in-scope CRM data live in Salesforce, integrations repointed, and reps selling on day one.
Keep these open
-
Pre-load history ahead of the freeze
Load closed deals, historical activities and inactive accounts while 360 View CRM stays live. Only open pipeline and the final delta need to move inside the window.
-
Publish the cutover runbook
A timed sequence with owners and abort criteria: freeze, final export, delta load, integration switch, smoke test, go/no-go, rep enablement. Pick a window that avoids quarter-end and month-end close.
-
Freeze 360 View CRM and take the final delta
Set 360 View CRM read-only and export everything changed since the pre-load. Reps updating deals during an unenforced freeze is the classic way to lose the most recent — and most valuable — pipeline changes.
A rep who updates a deal in the old CRM during the freeze will lose that update permanently.
-
Load the delta and reconcile the pipeline
Run the delta, then verify open pipeline value and count per rep against 360 View CRM before anything else. If the pipeline number is wrong on day one, reps stop trusting the system and never fully come back.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint every integration and verify with real records
Switch marketing automation, quoting, billing, enrichment, dialler and BI connections, then push a live record through each path. An unrepointed integration writing into the old CRM causes divergence that gets harder to reconcile every day.
Two-way integrations left pointing at the old CRM will keep writing there. Disable them before you switch, not after.
Cron Expression Builder Schedule the delta syncs that run through the freeze -
Go/no-go, then enable the reps
Call the decision explicitly against the exit criteria. Run enablement on real data with their own accounts on screen, and keep 360 View CRM read-only rather than cancelled until validation closes.
Don't move on until
- Historical load complete and reconciled before the freeze
- All integrations repointed and verified end to end
- Reps logged in with pipeline visible and correct
06 Validation Prove the revenue numbers tie out, then close the project.
Objective Reconciled data, forecast parity with pre-migration reporting, and signed acceptance.
Keep these open
-
Reconcile every object
Compare counts and values across accounts, contacts, deals, activities and files, plus field-level spot checks on a random sample. Produce a single report suitable for audit and for finance.
Migration Validation Tool Reconcile 360 View CRM and Salesforce record-for-record -
Tie the pipeline and forecast to baseline
Rebuild forecast, pipeline coverage and win-rate reporting and compare to pre-migration figures. Every variance needs an explanation — most trace back to stage or currency mapping decisions made in Field Mapping.
Stage-model changes will legitimately shift historical conversion rates. Restate the baseline rather than chasing the difference as a defect.
-
Verify ownership, visibility and permissions
Confirm every record has the right owner and that sharing rules, territories and role hierarchy give each rep exactly the visibility intended. Over-broad visibility in a CRM is a data-protection issue as much as a config one.
-
Re-profile for field completeness
Compare loaded null rates against the source profile per field. A field that arrived empty while counts matched is the failure counts alone cannot detect.
Data Profiler Prove field completeness held up through the load -
Test automation and integration write-back
Fire every workflow, assignment rule, sequence and notification, and confirm each integration writes correctly in both directions. Automation is rebuilt rather than migrated, so it is unproven until observed.
-
Sign off and schedule decommission
Get written acceptance against the Discovery criteria, keep 360 View CRM read-only for 30-90 days with a final archive export taken, then diarise cancellation so the contract does not auto-renew.
-
Record count reconciliation
by object type and by branch — totals must match between 360view source and Salesforce target
-
Document verification
spot check that files are linked to correct records and are accessible
360 View CRM → Salesforce specifics
- Household completeness
- every migrated household has all expected Person Accounts, Financial Accounts, and activities
- ACR role accuracy
- Primary, Joint, Authorized Signer roles match source assignments
- Financial Account data
- product types, open dates, masked account numbers, and balance strategy match source
- Activity history
- no missing notes, calls, or meeting records
- CRA data validation
- if 360view was used for CRA reporting, run parallel reports in both systems to confirm all reportable data is present and correctly categorized
Don't move on until
- Full reconciliation report complete across all objects
- Forecast and pipeline reports tie to pre-migration baselines
- Acceptance signed and 360 View CRM decommission scheduled
Field mapping reference
The field-by-field mapping for each object. Use this as the starting point for your mapping spec.
view Salesforce FSC
| 360 View CRM field | Salesforce field | Notes |
|---|---|---|
| Households | Account (Household RT) or Account + Party Relationship Group | 360view households are the primary entity. In FSC, the Household is a container, not the root entity. |
| People / Contacts | Person Accounts (or Contacts in individual model) | Each 360view contact becomes a Person Account record in most new builds. |
| Organizations | Business Accounts | Standard Account object with Business record type. |
| Household–Contact Links | Account-Contact Relationship (ACR) | Junction object carrying role, start date, end date, and primary-group semantics. |
| Product Holdings | Financial Accounts | Out of the box, FSC comes with several standard record types to track information on checking, savings, loan, credit card, investment, and insurance accounts. Map each 360view product type to the appropriate FSC record type. |
| Multi-party product ownership | Financial Account Role (managed-package) or Financial Account Party (standard) | One row per owner, signer, beneficiary, or guarantor. Each Financial Account must have at least one active Primary Owner. |
| Product Balances / Details | Financial Account fields or Financial Account Balance | Current balances map to Financial Account fields. Investment-level detail maps to Financial Holdings. Consider whether to migrate or re-sync from core. |
| Profitability Data | Custom fields on Account or Financial Account | FSC has no native profitability scoring. 360view calculates profitability at the household level using core data — the calculation logic does not migrate. |
| Activities | Tasks, Events, Activity records | Standard Salesforce activity model. Map 360view activity types to Task/Event record types. |
| Referrals | Lead (Referral record type) or custom Referral object | The Lead/Referrals tab has been sort of "repurposed" in FSC to handle referrals and expressed interest in a product for an existing client. Multi-hop referral chains may require custom fields or a custom referral object. |
| Pipelines / Opportunities | Opportunities with Products | Map 360view pipeline stages to Salesforce Opportunity stages. |
| Documents / Attachments | Salesforce Files (ContentVersion / ContentDocument / ContentDocumentLink) | Each file must be linked to the correct Person Account, Household, or Financial Account. |
| Alerts / SmartPops | No equivalent | Must be rebuilt as Salesforce Flows, scheduled flows, or Apex. |
| Users and Branch Data | Users, Roles, Territories | Branch hierarchy maps to Salesforce Territory Management. Role-based access maps to Permission Sets and Sharing Rules. |
| Incidents | Case | If your 360view institution uses Incident Tracking, map it to Case rather than hiding it inside notes. |
| Custom Fields | Custom fields on corresponding FSC objects | Data type mapping required (picklists, multi-selects, date formats). |
360view FSC
| 360 View CRM field | Salesforce field | Notes |
|---|---|---|
| Household_ID | LegacyHouseholdKey__c (External ID) | No |
| Household_Name | Name | Yes |
| Household_Status | Status__c | Yes |
| Primary_Branch_Code | Branch__c (Lookup) | Yes |
| Household_Segment | Segment__c | Yes |
| Profitability_Score | ProfitabilityScore__c | Yes |
| Profitability_Rank | ProfitabilityRank__c | Yes |
| Created_Date | CreatedDate | Yes |
| Owner / RM | OwnerId (Lookup: User) | Yes |
| Customer_ID | LegacyPersonKey__c (External ID) | No |
| First_Name | FirstName | No |
| Last_Name | LastName | No |
| Date_of_Birth | Birthdate | No |
| Yes | ||
| Mobile_Phone | MobilePhone | Yes |
| Home_Phone | Phone | Yes |
| Tax_ID | TaxIdLast4__c | Yes |
| Preferred_Contact_Method | PreferredContactMethod__c | Yes |
| Street | PersonMailingStreet | No |
| City | PersonMailingCity | No |
| State | PersonMailingState | Yes |
| Postal_Code | PersonMailingPostalCode | Yes |
| Country | PersonMailingCountry | Yes |
| Customer_Status | Status__c | Yes |
| Do_Not_Call | DoNotCall | No |
| Email_Opt_Out | HasOptedOutOfEmail | Yes |
| Assigned_Banker | PrimaryBanker__c (Lookup: User) | Yes |
| Business_ID | LegacyBusinessKey__c (External ID) | No |
| Legal_Name | Name | No |
| DBA_Name | DBA__c | Yes |
| Industry | Industry | Yes |
| Tax_EIN | EINLast4__c | Yes |
| Business_Status | Status__c | Yes |
| Role_Type | Roles | Yes |
| Start_Date | StartDate | No |
| End_Date | EndDate | No |
| Is_Primary | IsPrimary / Primary Group flag | Yes |
| Household_Key | AccountId (Lookup) | Yes |
| Person_Key | ContactId (Lookup) | Yes |
| Product_ID | LegacyFinancialAccountKey__c (External ID) | No |
| Product_Type | RecordTypeId | Yes |
| Product_Name | Name | Yes |
| Account_Number | MaskedAccountNumber__c | Yes |
| Core_Account_ID | CoreAccountId__c | No |
| Open_Date | OpenDate__c | No |
| Close_Date | CloseDate__c | No |
| Current_Balance | CurrentBalance__c | Yes |
| Available_Balance | AvailableBalance__c | Yes |
| Loan_Amount | LoanAmount__c | No |
| Credit_Limit | CreditLimit__c | No |
| Interest_Rate | InterestRate__c | No |
| Maturity_Date | MaturityDate__c | No |
| Product_Status | Status__c | Yes |
| Owner_Role | Role | Yes |
| Person_Key | Party/Owner Lookup | Yes |
| Referral_ID | LegacyReferralKey__c (External ID) | No |
| Referral_Status | Status | Yes |
| Product_Interest | InterestedProduct__c | Yes |
| Assignee | Assignee__c (Lookup: User/Queue) | Yes |
| Pipeline_ID | LegacyOpportunityKey__c (External ID) | No |
| Stage | StageName | Yes |
| Activity_ID | LegacyActivityKey__c (External ID) | No |
| Activity_Type | Type | Yes |
| Subject / Description | Subject / Description | Yes |
| Related_Record_Key | WhatId or WhoId | Yes |
| Document_ID | LegacyFileKey__c (External ID) | No |
| File_Name | Title | Yes |
| Parent_Record_Key | LinkedEntityId | Yes |
| Owner_User_Key | FederationIdentifier or LegacyUserKey__c | Yes |
| Branch_Code | BranchCode__c or Territory key | Yes |
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Does 360view CRM have an API for data extraction?
Yes. 360view offers a REST API (OAuth 2.0) that covers customers, accounts, referrals, incidents, pipelines, and activities. It requires a paid API license ('focus plan'), has throttling limits, and uses pagination. It is not as open as Salesforce or HubSpot APIs, so many institutions opt for a database-level export instead.
How do 360view households map to Salesforce Financial Services Cloud?
360view treats households as the primary entity. In Salesforce FSC, you create an Account with the Household record type (or use the newer Groups and Households model), then link Person Accounts to it via the Account-Contact Relationship (ACR) junction object. The ACR carries roles (Primary, Joint, etc.), start and end dates, and controls how financial data rolls up to the household level.
Should I migrate core banking data from 360view to Salesforce?
Generally, no. Data that is synced from your core processor (Fiserv, Jack Henry, FIS) into 360view — such as balances, product details, and transaction history — should be re-synced directly from core into Salesforce FSC via a new integration. Only migrate 360view-native data: activities, notes, referrals, relationship assignments, custom fields, and profitability scores.
Is enabling Person Accounts in Salesforce FSC reversible?
No. Once Person Accounts are enabled, they cannot be disabled. This is an org-level architectural decision that affects how all contacts, households, and financial accounts relate to each other. It also changes available organization-wide default sharing options. Validate against your full B2B and B2C scope before enabling.
How long does a 360view to Salesforce FSC migration take?
For a small community bank with under 5,000 households, expect 4–10 weeks with a managed service. For larger credit unions with 50,000+ households, complex data, and custom objects, expect 8–16 weeks. FSC configuration alone (before any data is loaded) typically takes 4–8 weeks.