Kerdora supports a mix of ongoing connections and one-time imports: linked financial accounts, Altruist holdings imports, tax-return imports, document extraction, Spending statement imports, and an advisor scheduling link. These workflows do not all behave like live integrations, so confirm whether data continues syncing or was imported once.
How do I move a client from RightCapital?
Kerdora does not currently provide a direct RightCapital import or an ongoing RightCapital sync. Do not upload a RightCapital backup or export and expect Kerdora to recreate the plan automatically.
Before leaving RightCapital, gather the current source information you need to rebuild and verify the household:
household members, birth dates, relationships, and entities;
assets, liabilities, ownership, tax treatment, balances, holdings, and savings;
income, Social Security, Giving, spending, and payment frequencies;
Goals, dates, target amounts, retirement assumptions, and account assignments;
insurance policies and estate information; and
the latest statements, tax returns, and other documents that support those values.
Use the Kerdora workflow that matches each source:
Have the client link supported institutions when you want an ongoing account connection.
Use Upload & Extract for supported source documents that can propose client-data records.
Use the tax-return workflow for supported returns and tax-scenario inputs.
Use the Altruist importer only for an applicable Altruist CSV.
Use a Spending statement import for supported transaction statements.
Enter or correct information manually when no supported import supplies it.
After migration, compare each created record with its source. Confirm owner, subtype, tax treatment, amount, frequency, Goal assignment, and source date. Search for an existing linked, extracted, or manual record before creating another one. A statement and a linked feed can describe the same account; they are not automatically two assets.
Account aggregation: ongoing linked-account data
Account aggregation lets a client connect supported institutions from the portal. Depending on the institution and account type, the connection can provide account metadata, balances, investment holdings, and transactions.
The client completes institution authentication and account review. An advisor can refresh a healthy or stale link. The client reconnects an errored link and controls disconnecting or unlinking.
Institution coverage and available data vary. A connected account does not guarantee complete holdings, transactions, or history.
Altruist: one-time holdings import
Use the Altruist import when an advisor has an Altruist data file and needs to create or update client accounts and holdings. This is an import workflow, not a live custodian sync.
Review household and account matching before confirming. The result screen reports import counts; it does not create an ongoing Altruist connection or automatically keep future holdings current.
Tax returns: source import and extraction
Taxes can store and extract supported client tax returns, then use the reviewed values in tax analysis. The advisor must review entity matches, tax year, extracted forms, and scenario values.
A tax-return import does not file a return, connect to tax-preparation software, or automatically update when a later return is filed.
Documents and Upload & Extract: one-time client-data proposals
An advisor can upload supported files and use Upload & Extract to produce proposed client-data additions or updates. The advisor reviews and applies each proposal.
Document extraction does not create a live connection to a document provider, CRM, custodian, or tax system. Later source changes require another upload or a manual update.
Spending statements: one-time transaction imports
Spending supports importing transactions from supported bank or card statements. Record the account and date range so an imported period does not overlap a linked transaction feed or another statement import.
Statement imports do not refresh. Account aggregation is the ongoing source when a supported institution supplies transaction data.
Calendar and scheduling link
Under advisor Settings, an advisor can save a calendar or scheduling link used for client scheduling. This exposes the approved booking destination where Kerdora uses it.
It is not a two-way calendar sync. Kerdora does not currently read calendar availability, create planning events from a calendar, or synchronize Office planning dates with Google or Outlook.
What common integrations are not currently supported?
Unless a current Kerdora screen shows otherwise, do not assume support for:
continuous CRM synchronization;
a direct RightCapital import or synchronization;
broad custodian feeds outside the available linked-account connection and Altruist import;
tax-software synchronization or electronic filing;
Google Calendar or Outlook calendar synchronization;
automatic document-provider synchronization;
automatic export to a portfolio-management or rebalancing platform; or
a public workflow that keeps every imported file synchronized.
Use document upload, manual entry, or an available purpose-built import when one fits the task. Keep one authoritative source for each record and review ownership, type, tax treatment, Goal assignment, and timing after import.
How do I confirm whether a connection is live?
A live linked-account connection has an institution card with status and last-sync information. A one-time import has an import or extraction result but no continuing institution refresh.
Before promising an integration to a client or firm:
Check the current Kerdora menu and import screen.
Identify whether the workflow is live or one-time.
Confirm which fields are supplied.
Confirm who must authenticate or review.
Define how future updates will be handled.
Contact Kerdora Support when a firm needs a connection not listed here. Describe the provider, data required, direction of sync, update frequency, and planning workflow. Do not share credentials.