The loan file stays in origination; what moves is the relationship layer of borrowers, partners, consent and pipeline references that loan officers work from.
Mortgage and lending migrations usually pull borrower and prospect data from an older CRM, loan officer spreadsheets, a marketing tool and referral partner lists, while the loan origination system continues to own applications and loan files. We load borrowers, co-borrowers, real estate agents, builders and other referral partners, reference loans by number and milestone, and carry forward lead source, communication history and consent. For business lenders, companies, guarantors and brokers join the model. Past-closed borrowers are brought in with enough detail to support refinance, renewal and cross-sell outreach, subject to the privacy rules that govern it.
Lending data is shaped by the loan file, which lives elsewhere and changes status rapidly. A migration must reference the loan origination system accurately without turning Salesforce into a second, stale copy of the file. Relationships are also layered: co-borrowers, referral partners and loan officers all have claims on the same record, and loan officers are protective of their borrower lists. Consent is strictly regulated, with telemarketing and privacy rules affecting whether a past borrower can be contacted and how. Loan officer turnover adds another wrinkle, because leads and past clients assigned to departed officers need clear reassignment rules before data is loaded.
Active loans come across as references to the origination system with loan number, purpose, stage and key milestone dates. Loan officers and processors see where each deal stands in Salesforce, while the origination system stays authoritative, and reconciliation confirms every active loan is represented once. Withdrawn and denied applications are loaded with their status so follow-up can be planned appropriately.
Closed borrowers are loaded with property, loan type and closing date so marketing and loan officers can plan rate-change, renewal and anniversary outreach. We keep only the fields that support permissible marketing and service, avoiding full loan files that would widen privacy exposure. Loans sold or transferred for servicing are flagged so outreach reflects who services them now and avoids confusing borrowers.
Real estate agents, builders, financial planners and other partners are consolidated from loan officer lists into one contact per partner, with links to the loans they referred. Loan officers keep ownership of their relationships, and managers finally see which partners generate closed business across the team instead of only within individual books. Partner contacts who left the industry or changed brokerages are updated or retired during cleanup, and co-marketing agreements are noted where compliance requires review.
Leads from purchased lists, websites and referral forms keep their source, capture date and consent flags. Do-not-call and do-not-email status are consolidated with a strict rule that the most restrictive preference wins when sources disagree, and that consolidation happens before any campaign or dialer is switched on in Salesforce. Lead records that never engaged and carry no valid consent are usually left behind, which shrinks the database and the exposure that comes with it. Purchased-list leads keep their vendor category for later review.
We begin with lending operations, compliance and a group of loan officers representing different production styles. Identifiers from the origination system are agreed first, then borrowers and partners are matched and loaded, followed by loan references and activity history. Compliance reviews consent mapping and the handling of nonpublic personal information before production loads. Test data is reconciled against pipeline reports, and loan officers confirm their own books in a sandbox. Cutover avoids month-end closing periods, when processors and closers are busiest, and the legacy CRM remains read-only through the next closing cycle.
Loan numbers, status, milestones and assigned staff are extracted for matching and then kept current by integration, while the loan file itself remains in the origination system.
Product and rate lock references on active loans are carried where loan officers need context, without copying pricing data that changes constantly and belongs in the pricing engine.
Serviced loan status and payoff indicators help target retention outreach, and identifiers are mapped so past clients link to the loans they hold today.
Permission collected for one purpose or by one entity may not cover new outreach. Review TCPA, CAN-SPAM and privacy notices with compliance before migrating preferences, and never let a merge replace a restrictive status with a permissive one from a less reliable source.
Borrower details fall under GLBA privacy and safeguards requirements. Limit migrated fields to what sales and service need, secure every extract, and involve compliance in approving environments. Fewer sensitive fields also mean simpler access rules for loan officers and partners.
Borrowers and partners owned by former loan officers need a clear rule: reassign to a branch manager, a house account or a retention team. Decide before loading, or orphaned records will sit unworked and past clients will hear from nobody.
Client names are anonymized.
The data becomes the company's record in Salesforce, with the loan officer shown as owner. That usually improves follow-up, because nothing is lost when a spreadsheet goes missing or a laptop is replaced. Ownership and visibility rules are agreed with sales leadership in advance, so officers know exactly which relationships remain theirs and what managers can see.
In most cases they stay put. Applications, disclosures and underwriting documents belong in the loan origination system or document repository with their own controls and retention rules. Salesforce holds the relationship, communication history and references to the loan, which is what sales and service teams need without duplicating regulated documents in another place that would need its own retention schedule.
Borrowers often appear once per loan, with name variations, maiden names or co-borrower roles. We match on origination system identifiers, property and contact details, then merge into single person records linked to each loan with the right role. Merges affecting consent or ownership go to a review queue instead of being automated, and loan officers help resolve them.
The model expands to businesses, owners, guarantors, brokers and multiple credit facilities per relationship. Matching relies on tax IDs and entity names, and ownership chains need review because the same person may personally back several loans. Financial Services Cloud's relationship features help represent those connections without heavy custom development. Guarantor and owner relationships are verified with credit administration before loading, since errors there affect risk reporting.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.