The hard part of this move is not the export. It is the difference in how the two systems think. Envestnet Tamarac CRM works in contact records; Redtail CRM works in contact records. Get that mapping wrong and every report built on it afterwards is wrong too. This page covers the field map, what does not survive, what it costs, and the reconciliation step that decides whether anyone trusts Redtail CRM in month two.
The two systems, side by side
| Envestnet Tamarac CRM | Redtail CRM | |
|---|---|---|
| Primary record | Contact | Contact |
| Grouping | Household, aligned to Tamarac reporting groups | Family or account grouping on the contact |
| Activity history | Dynamics activities plus Tamarac workflow | Notes, activities and a separate workflow object |
| Documents | Dynamics notes and attachments, or a connected DMS | Attached to the contact, or in Redtail Imaging |
| Getting data out | Dynamics export tooling and the platform API. | CSV export per module, or a vendor-assisted extract for full history. |
| Who administers it | A named Dynamics administrator. | None. An operations associate can run it. |
| Pricing | Bundled with the Tamarac suite; custom quoted. | $39 to $59 per user per month billed annually. |
What breaks
- Grouping changes: Household, aligned to Tamarac reporting groups becomes Family or account grouping on the contact. Somebody has to define what a group means in the target before load.
- Activity history moves with partial fidelity. Envestnet Tamarac CRM stores it as dynamics activities plus tamarac workflow; Redtail CRM expects notes, activities and a separate workflow object.
- Plugins and Power Automate flows carry logic that no Dataverse export represents.
- Automations, reports, dashboards and permissions never transfer. Budget them as build work.
- Every connected system has to be repointed and retested: the DMS, billing, e-signature and the shared inbox.
Known hazards on each side
Leaving Envestnet Tamarac CRM:
- Household grouping is aligned to Tamarac reporting, so it may not match how the firm wants to see clients elsewhere.
- Dynamics option sets and lookups need translating rather than copying.
- Leaving Tamarac CRM while keeping Tamarac reporting means the two stop agreeing unless something reconciles them.
Arriving in Redtail CRM:
- Status, Servicing Advisor and Writing Advisor are used inconsistently between firms, so they get remapped rather than copied.
- Recurring activity criteria do not translate cleanly to other systems, and future occurrences generally cannot be recreated.
- Imaging attachments are a separate extract from the contact data.
The field map
| Concept | In Envestnet Tamarac CRM | In Redtail CRM | What to watch |
|---|---|---|---|
| Primary record | Contact | Contact | Same shape. Mostly a mechanical load. |
| Grouping | Household, aligned to Tamarac reporting groups | Family or account grouping on the contact | The target groups records differently, so grouping is created rather than copied. |
| Activity history | Dynamics activities plus Tamarac workflow | Notes, activities and a separate workflow object | Expect partial fidelity. Types, timestamps and authorship survive; structure often does not. |
| Documents | Dynamics notes and attachments, or a connected DMS | Attached to the contact, or in Redtail Imaging | Usually a separate extract and load from the record data. |
| Owner and assignment | Assigned user or advisor fields | Assigned user or team fields | Map departed staff explicitly. Records assigned to nobody disappear from every view. |
| Custom fields | Firm-specific fields added over time | Created to match, or consciously dropped | The audit here is the work. Undocumented fields that reports depend on are the usual surprise. |
Cost and timeline
| Phase | Typical range |
|---|---|
| Data audit and cleanup | $3,000 to $25,000 |
| Migration execution | $5,000 to $50,000 |
| Target configuration | Two to six weeks |
| Ongoing administration | Absorbed by existing operations staff |
The upside of this direction is administrative. Envestnet Tamarac CRM assumes a named platform administrator and Redtail CRM does not, so the ongoing cost drops as well as the license. The trade is expressiveness: any workflow encoded in the platform has to be rebuilt or given up.
The five phases
- Audit Envestnet Tamarac CRM. Count records per object, find duplicates and orphans, and decide what does not come with you. Get that decision signed off before mapping.
- Map against real records. Use the table above as the starting point, then walk fifty live records field by field.
- Dry run into a Redtail CRM sandbox. Load the full set, not a sample. Sample loads hide the failures that only appear at volume.
- Cut over on a quiet window. Freeze writes in Envestnet Tamarac CRM, load, repoint every integration, unfreeze. Keep Envestnet Tamarac CRM read-only for at least a quarter.
- Reconcile. Compare Redtail CRM to Envestnet Tamarac CRM record by record and field by field, and produce a variance report.
The full version of this plan, with the failure evidence behind it, is in the CRM migration playbook.
The compliance clause
The Advisers Act books-and-records rule (17 CFR 275.204-2) survives the migration. A household that lands without its history is a records gap, not a cosmetic issue. Keep the field map, the variance report and the mapping sign-offs with the records, because the decisions you made in phase two are part of the record too.
Where Caddi fits
Caddi does the mechanical half and then keeps doing it. Show it the task once and it reads Envestnet Tamarac CRM, applies your field map, loads Redtail CRM, and then compares both sides record by record and hands back a variance report you can act on. Because it runs over APIs across your stack, the same agent covers the parts a migration tool ignores: documents filed to the right contact with the right metadata, and the post-cutover hygiene that otherwise becomes someone's Monday.
Caddi automation for these systems: Envestnet Tamarac CRM and Redtail CRM.
Related migrations
- Redtail CRM to Salesforce
- Redtail CRM to Salesforce Financial Services Cloud
- Redtail CRM to Wealthbox
- Salesforce Financial Services Cloud to Redtail CRM
- Salesforce to Redtail CRM
- Wealthbox to Redtail CRM
Migration without the manual pass
Move and reconcile Envestnet Tamarac CRM into Redtail CRM
Caddi reads Envestnet Tamarac CRM, applies your field map, loads Redtail CRM, then compares both sides record by record and reports the variances.
Frequently asked questions
How do you migrate from Envestnet Tamarac CRM to Redtail CRM?
Audit the Envestnet Tamarac CRM data first, then map fields against fifty real records rather than against the schema, dry run the full set into a Redtail CRM sandbox, cut over on a quiet window with writes frozen, and reconcile record by record afterwards. Dynamics export tooling and the platform API. Redtail CRM then needs the records loaded in dependency order, with documents as a separate pass.
What does not transfer from Envestnet Tamarac CRM to Redtail CRM?
Grouping changes: Household, aligned to Tamarac reporting groups becomes Family or account grouping on the contact. Somebody has to define what a group means in the target before load. Activity history moves with partial fidelity. Envestnet Tamarac CRM stores it as dynamics activities plus tamarac workflow; Redtail CRM expects notes, activities and a separate workflow object. Plugins and Power Automate flows carry logic that no Dataverse export represents.
How long does a Envestnet Tamarac CRM to Redtail CRM migration take?
Six to twelve weeks is realistic for a clean mid-size move, and three to six months where Redtail CRM is being implemented at the same time. Firms with years of history in Envestnet Tamarac CRM should budget several weeks of cleanup before any data moves.
Who administers Redtail CRM afterwards?
None. An operations associate can run it. That is one of the reasons this move is lighter than a platform migration.
What are the compliance implications for advisory firms?
The Advisers Act books-and-records rule (17 CFR 275.204-2) survives the migration. A gap in client history is a finding, so keep the field map, the variance report and the sign-offs where an examiner can find them.