How to Export Data from AdvisorEngine CRM: Methods & Limits

There is no single "Export Everything" button in AdvisorEngine CRM. The native Database Export tool delivers your database content as CSV files inside a password-protected zip archive — but it explicitly excludes documents and flattens the Record → Person → Action hierarchy that makes wealth management data meaningful.

For wealth management firms, a complete data export requires capturing the complex relational links between households, individual clients, financial plans, and compliance-mandated communication logs (Actions). If you're planning a migration to Wealthbox, Redtail, Salesforce Financial Services Cloud, or HubSpot, relying solely on native CSV exports will break these relationships.

Here is what each export method actually gives you:

Method	Format	Records & Persons	Actions/Notes	Documents	Revenue Data	Household Hierarchies	Custom Fields
Database Export	CSV (zip)	✅	✅ (flat)	❌	✅ (flat)	❌ (flattened)	✅
Outlook Add-in Export	Outlook Contacts	Partial (Person 1 only)	❌	❌	❌	❌	❌
Microsoft 365 Contact Sync	Outlook Contacts	Partial (Person 1 only)	❌	❌	❌	❌	❌
Grid / Report Export	Excel/CSV	Varies	Varies	❌	Partial	❌	Varies
Constant Contact Sync	CC Contacts	Partial (email required)	❌	❌	❌	❌	❌
Dedicated Migration Service	Target System	✅	✅	✅	✅	✅	✅

Migration-ready extract means more than a folder of CSVs. You need source IDs, Record ownership, Person-to-Record relationships, chronological Action history, documents, and custom field data preserved in a structure the target system can actually ingest.

For context on why flat CSV files struggle with relational CRM data, see our breakdown of Using CSVs for SaaS Data Migrations.

How to Export Your AdvisorEngine CRM Database (Step-by-Step)

The native export process is straightforward: navigate to Settings, click the Database Export tile, create a password that is at least seven characters long, then click Export. Click Get Link To Database Export to begin downloading. To open the zip file, enter the password you created. The output is your current database contents in CSV files.

Those CSVs will include Records, Persons, Actions, opportunities, custom field values, and revenue entries — all as flat, denormalized tables. Each CSV represents a single data table with internal IDs that reference other tables. Reassembling this data into a new CRM requires mapping relational IDs across dozens of spreadsheets.

If these instructions don't work for you, contact AdvisorEngine directly to request a backup of your CRM data. This fallback is worth knowing about — some firms report that the self-service export can time out on large databases, and AdvisorEngine support can generate the archive on their side.

The Big Catch: Documents Are Not Included in Native Exports

This is the limitation that catches most firms off guard. AdvisorEngine promotes "easy-to-use data and database exporting capabilities", but the native Database Export explicitly omits all uploaded documents.

For an RIA that has stored years of client agreements, financial plans, compliance correspondence, KYC documentation, signed investment policy statements, and historical tax forms in the CRM, this means the export captures your structured data but leaves behind the unstructured data that auditors and compliance officers care about most.

There is no bulk document download feature in AdvisorEngine CRM. Documents must be downloaded individually from each Record's document storage area. For firms with thousands of stored files across hundreds of client Records, this is a manual, time-intensive process.

If your firm uses the Docupace integration to store documents, the Docupace integration allows files stored in Docupace to be visible within the CRM navigation in the Record Document storage area — but those files live in Docupace, not in AdvisorEngine's own storage. You would need to extract them from Docupace separately.

If you are planning an AdvisorEngine CRM data migration, document extraction must be treated as a separate, highly technical workstream. Documents must be retrieved, matched to their parent Record or Household ID, and securely transported to the new system. Failing to extract these files correctly can result in compliance violations, broken audit trails, and lost client history.

Exporting Specific Data Types: Contacts, Revenue, Actions, and More

Not all data in AdvisorEngine behaves the same way during export. Certain records require highly specific extraction methods, and some cannot be extracted in bulk at all.

Informational Contacts: Record-by-Record Only

AdvisorEngine CRM distinguishes between Persons (primary contacts on a Record) and Informational Contacts (secondary contacts stored at the Record level — typically CPAs, attorneys, or extended family members linked to a household). This distinction matters because Informational Contacts do not appear in the standard database export or global reports.

It is not possible to report globally on Informational Contacts. To export them, you must navigate to each individual Record, use the Export to Excel feature on the Informational Contacts grid, and repeat for every Record that has them. For a firm with 500+ client households, this is extremely tedious.

Revenue Reports

AdvisorEngine CRM allows you to track revenue at the Record level, but revenue reporting requires that the Tracking Revenue feature is enabled for your Records first. Once enabled, you can generate revenue reports from the Record Workspace by selecting specific records, specifying a date range, and filtering by revenue type. Use the Save As command to export the report to a document format.

The key limitation: revenue data in the database export appears as flat rows without the Record context that makes it meaningful. If you need revenue figures tied to specific households for import into another system, you'll need to export reports manually or reconstruct the relationships from the raw CSV IDs. This output is useful for point-in-time financial analysis but does not yield raw relational data suitable for a database migration.

Outlook Add-in Contact Export (One-Way Sync)

The Local Outlook Add-in enables users to export contact data from AdvisorEngine CRM to Microsoft Outlook. This is a one-way synchronization. Due to limitations of Microsoft Outlook Contacts, primarily only Person 1's contact info on a Record is exported.

To set it up:

1. Create a folder in your Outlook contacts specifically for the CRM export/sync (recommended to avoid interfering with your regular contact list).
2. From the Add-in Email Toolbar, click the blue question mark, then click Options. Under Auto Contact Export, select On. Click the Refresh button to load your contact folders, select the target Contact Folder, and click Initialize.

Changes made in AE CRM will automatically synchronize to these contacts. Do not edit these contacts in Outlook directly. Edit the information stored in your CRM so changes show in both locations.

This method is useful for getting a quick contact list into Outlook, but it is not a migration path. It only moves Person 1 data, omits Person 2, and carries no Action history, notes, or custom fields.

Microsoft 365 Contact Sync (Two-Way)

Once the Microsoft 365 integration is set up for your User, you can sync contacts between AdvisorEngine CRM and a Contact folder within Microsoft 365. This is a per-user setting and must be enabled and configured individually for each User.

Unlike the legacy Outlook Add-in, the M365 sync is bidirectional — the sync function will regularly scan both the selected Outlook folder and CRM Records and make updates to either system as needed.

This is a contact sync tool, not a data migration tool. It handles Person 1 contact fields and nothing else.

Actions and Activity History

Actions are the backbone of AdvisorEngine CRM's activity tracking. They capture calls, meetings, emails, tasks, and notes tied to specific Records. Actions appear in the database export as flat CSV rows with Record ID references — but the chronological, contextual nature of the Action log is lost when it's reduced to a spreadsheet.

When migrating to another CRM, Actions typically need to be mapped to the target system's activity timeline (e.g., HubSpot Engagements, Salesforce Activities, or Wealthbox Events). This mapping requires scripting — you cannot simply import the Action CSV into another system and expect it to retain context. An Action that was originally tied to a specific financial plan might default to a generic account note, losing vital compliance detail.

Classifications and Keywords

In AdvisorEngine, Classifications and Keywords are heavily used to segment clients by service tier, AUM, or communication preferences. While the Database Export includes these fields, they are often exported as comma-separated strings within a single cell. During a migration, these strings must be parsed and mapped to multi-select picklists or custom tags in the target CRM. Failing to split these values correctly will corrupt your segmentation and break automated marketing workflows.

Why AdvisorEngine CRM Data Is Uniquely Hard to Migrate

AdvisorEngine CRM is built for advisors, by advisors. Trusted by wealth managers since 2000, it inherently understands the business, offering specific workflow automation and exceptional client service. That advisor-specific architecture is exactly what makes export complicated.

The core data model uses a Record → Person hierarchy that differs from standard CRM conventions:

• A Record represents a household, company, or entity (not an individual contact)
• Person 1 and Person 2 live inside a Record (typically spouses)
• Informational Contacts are additional contacts nested under a Record
• Actions are logged against Records, not individual Persons
• Workflows are process templates that trigger Actions and tasks

This householding model is powerful for advisory firms but creates problems during export because most target CRMs (Salesforce, HubSpot, Redtail, Wealthbox) use a flat Contact or Account → Contact model. Users love "the workflow build out & householding spouses", but that same structure breaks when dumped into CSV.

Specific things that break during a manual CSV migration:

• Household relationships — Person 1 and Person 2 become separate contact rows with no obvious link to their shared Record (household). A husband and wife grouped under a single Household in AdvisorEngine will import as two isolated contacts with no shared financial history. The target system will not inherently know that "Record ID 1042" and "Record ID 1043" belong to "Household ID 500" unless you explicitly script that relationship during the import.
• Action ownership — Actions reference Record IDs that don't exist in the target system. Without proper mapping, an Action originally tied to a specific financial plan might default to a generic account note, losing vital context.
• Custom field context — User-defined fields export as columns, but without the field type metadata (dropdown values, date formats) the target system needs.
• Document links — Any references to stored documents become dead pointers.
• Classifications and Keywords — Comma-separated values in single cells need to be parsed and mapped to the target system's picklist or tag structure.
• Workflow state — Active workflow instances and their completion status are not meaningful outside AdvisorEngine.

For a deeper look at the common pitfalls, see 7 Costly Mistakes to Avoid When Migrating Financial Data.

Comparison of AdvisorEngine Export and Migration Methods

Criteria	Native Database Export	Manual Grid Exports	Outlook / M365 Sync	Third-Party Sync Tools	Dedicated Migration Service
Data completeness	Partial (no docs)	Very partial	Contacts only	Varies by tool	Full
Relationship preservation	❌ Flat CSVs	❌	❌	Not designed for this	✅
Document extraction	❌	❌	❌	Varies	✅
Action/note history	Flat rows only	❌	❌	Not designed for historical bulk	✅ (mapped to target)
Custom field mapping	Raw columns	Partial	❌	Varies	✅
Effort required	Low (self-service)	Very high (manual)	Medium (per-user)	Medium	Low (handled for you)
Compliance audit trail	❌	❌	❌	Varies	✅
Cost	Free	Free	Free	Varies	Paid

Firms typically choose one of three paths:

1. Native CSV Export (DIY): Best for simple, point-in-time text backups. Requires zero budget and is accessible directly from the settings menu. But it costs significant hours in manual data manipulation, fails entirely for document extraction, and breaks household hierarchies.

2. Third-Party Sync Tools (e.g., PreciseFP, Constant Contact): Best for bi-directional data gathering and keeping client/prospect info updated between systems. The PreciseFP integration with AdvisorEngine is bi-directional, meaning you can export and import client/prospect information with a single click. It currently integrates contact and employment information along with family members information. These tools are not designed for bulk historical data migrations involving years of compliance logs, complex Actions, and large document vaults.

3. Dedicated Migration Services: Best for full-scale system replacements (e.g., AdvisorEngine to HubSpot, Salesforce, or Wealthbox). Uses direct API access to extract all data — including documents, custom financial fields, and Actions — and maps them accurately into the target system's architecture. Preserves relational integrity. Requires an upfront investment.

When the Native Export Is Enough

If you need a backup for disaster recovery or a quick reference dataset, the native Database Export is fine. It gives you a snapshot of your structured data. Keep the encrypted zip in secure storage and you have a reasonable safety net.

When You Need More

If you are migrating to a new CRM, the native export is a starting point but not a solution. You'll need to:

1. Reconstruct Record → Person relationships from ID references
2. Map Actions chronologically into the target system's activity model
3. Extract documents manually (or via automation against the CRM's interface)
4. Handle Informational Contacts with per-Record manual exports
5. Validate custom field types and picklist values against the target schema
6. Parse Classifications and Keywords from comma-separated strings into proper multi-select fields
7. Verify revenue data is correctly attributed to the right households

This is 40–80 hours of engineering work for a mid-sized RIA firm, before you account for QA and data validation.

AdvisorEngine CRM's Integration Ecosystem: What Can Push Data Out?

AdvisorEngine CRM features deep integrations with many custodians and major portfolio management, reporting, and back-office solutions. Some of these integrations can be used as indirect export paths:

• Orion Advisor Services — The Orion Contact Push integration allows you to send Record Contact Info changes from AdvisorEngine CRM to your Orion Contacts. This is a one-way sync that only pushes info from AE CRM to Orion.
• Constant Contact — A modern API framework powers the Constant Contact integrations, which will allow advisors to both export and import contact data to and from Junxure. Useful for email marketing list management but not a full data export.
• PreciseFP — Bi-directional contact and employment sync, as noted above. Covers a narrow slice of contact data for specific operational purposes.
• Docupace — Connects document storage but doesn't export data out of AE CRM.
• Zocks / Jump — AI meeting note tools that push into AE CRM, not out of it.

None of these integrations constitute a full data export. They each move narrow slices of data for specific operational workflows.

A Note on the Junxure Legacy

In 2018, the AdvisorEngine team embarked on a multi-year strategic initiative to modernize Junxure CRM. The first stage focused on infrastructure upgrades. The second stage brought deeper integrations. The third stage brought the CRM in line with the company's product ideals. The product is now called AdvisorEngine CRM.

If your firm is still running the legacy desktop version of Junxure, the desktop legacy version is still being maintained from a security and operational standpoint, but users wanting the latest integrations or the speed of cloud-based improvements will need to switch systems.

Legacy Junxure Desktop databases use a different storage format than the cloud version. Exporting from the desktop version may require direct database access (SQL Server) or coordination with AdvisorEngine support. The steps outlined in this guide apply to the cloud-based AdvisorEngine CRM.

What to Do Before You Export

Before running any export, take these prep steps:

• Run a data quality audit — Identify duplicate Records, incomplete Persons, and orphaned Actions. Cleaning up before export saves significant time during import.
• Document your custom fields — List every user-defined field, its data type, and its picklist values. The export CSVs will have column headers, but they won't tell you what field type they are.
• Inventory your documents — Count how many files are stored per Record. This tells you how large the manual document extraction effort will be.
• Check Informational Contacts — Determine which Records have Informational Contacts that won't appear in the standard export.
• Confirm your Tracking Revenue status — If revenue data matters for your migration, verify that revenue tracking is enabled for all relevant Records before you export.
• Notify AdvisorEngine support — If you're planning a full migration, let their support team know. They may be able to provide a more complete data package than the self-service tool delivers.

How ClonePartner Handles AdvisorEngine CRM Migrations

We've run enough financial CRM migrations to know where AdvisorEngine exports break down in practice. The three biggest gaps — documents excluded from native export, household hierarchies flattened to CSV, and Action history disconnected from Records — are exactly the problems we solve.

Here's what a ClonePartner-led AdvisorEngine migration typically looks like:

1. Full data inventory — We map every Record, Person, Action, custom field, document, and workflow in your database before touching anything.
2. Document extraction — We extract documents that the native export omits, preserving file names, folder structures, and Record associations.
3. Relationship reconstruction — We rebuild Record → Person 1 / Person 2 / Informational Contact hierarchies in the target CRM's native data model (Households, Contacts, Companies — whatever the target supports).
4. Action timeline mapping — We map historical Actions into the target system's activity timeline chronologically, so your compliance history and communication logs survive intact.
5. Custom field and picklist translation — We handle data type mismatches between AdvisorEngine's user-defined fields and the target CRM's property types. Classifications and Keywords are parsed and mapped to proper multi-select fields.
6. Zero-downtime execution — Your team keeps working in AdvisorEngine during the migration. We run delta syncs to capture any changes made between the initial extraction and go-live. Your advisors never lose access to critical client data during the transition.

For more on our zero-downtime approach, see Zero Downtime Guaranteed.

For a broader look at CRM migration options, check out our Top 5 Best CRM Migration Solutions.