Confirm what needs to move and what should stay
Jungo runs on Salesforce, but the configuration in your org determines the migration scope. Inventory the actual objects, fields, relationships, files, activities, integrations and automations. Do not build a mapping from guessed package field names.
This is a migration-planning guide. Before a move, validate the target design with your actual record structure and agree the acceptance checks. The right scope depends on what that review finds.
Demonstrate the target relationship model
HighLevel documents custom objects and record associations. It should not be evaluated as though it only supports a flat contact list. Check the current account capabilities, limits, workflow support and reporting behaviour against a representative mortgage process.
HighLevel: create and edit custom objects
HighLevel: associations between opportunities, companies and custom objects
Show one person with more than one loan-related record, a co-borrower relationship and a referral partner. Establish which system owns the actual loan process and sensitive documents. Moving marketing and relationship management does not automatically replace origination, underwriting or servicing systems.
| Area | What to verify |
|---|---|
| People and organisations | Stable identifiers, shared addresses and relationship roles. |
| Loan-related records | How repeated applications and co-borrowers remain distinguishable. |
| Activity and files | Which history is imported, retained elsewhere or made available by reference. |
| Calculated values | Whether the destination recalculates the value or receives a dated snapshot. |
| Contact preferences | How consent evidence, opt-outs and suppression are preserved. |
| Automation | What triggers a message, assignment or stage change in the destination. |
Prevent migration from starting unintended outreach
An imported record can satisfy a workflow trigger even when nobody intends to send a message. Keep sending automations disabled during the rehearsal. Test the exact import and subsequent update behaviour with synthetic records before enabling any customer-facing action.
Preserve opt-outs and their source evidence. A contact’s presence in the old CRM is not a reason to treat every channel as available for outreach. Have the accountable owner approve the contact rules before the new sending process starts.
Reconcile a sample before the full load
Retain source identifiers in the mapping and destination where appropriate. Match carefully; two people sharing an email address should not be merged merely to satisfy a convenient import key. Hold ambiguous records for review.
Compare record counts, selected field values, relationships, activity and attachment access. Ask a broker and an administrator to complete their actual tasks in the target system. Record the gaps rather than assuming a successful CSV import establishes a working migration.
Keep the website and CRM decisions separate
A CRM move does not require an immediate website replacement. If forms, booking or landing pages change, document every affected URL, destination and follow-up trigger. Keep a working route for new enquiries during the transition.
Retire an existing tool only after its required functions have a tested replacement or an explicitly accepted alternative. Include integrations, reporting, retention and export access in that decision, not just visible screens.
Agree the cutover and rollback
- Name the system of record during each part of the move.
- Set the initial load, change capture and final reconciliation process.
- Identify who can authorise the switch and the conditions that would stop it.
- Prepare a rollback that avoids duplicate messages, records or competing updates.
- Monitor the first live journeys and route exceptions to an owner.
Estimate the work after the mapping, target demonstration and rehearsal identify the real dependencies. Licence prices, migration hours and a generic contact count cannot substitute for that scope.
Explore lending and finance workflows
Discuss a similar workflow
Bring a description of the process, the systems involved and one example of where work gets stuck. We can use discovery to establish the requirements, dependencies and next step before preparing a solution and estimate. Please leave private customer, applicant and patient records out of the website enquiry.