Enabling the Orion Integration

Learning Team

Please note: This content is intended for Practifi System Administrators and is technical in nature. The steps described in this article may not be able to be completed without System Administrator permissions. Please discuss your integration installation plans with your Practifi Customer Support Team for their assistance.

Overview

Orion Advisor Solutions is a leading portfolio accounting, billing, and performance reporting platform for independent Registered Investment Advisors. The Orion integration with Practifi connects portfolio and account data directly to the CRM via Orion Connect, Orion’s Salesforce-based managed package installed within Practifi. Once enabled, the integration syncs Household, Contact, Account, Holding, and Receivable records on a configurable schedule, eliminating manual data entry and reconciliation between systems.

The Orion integration is a coordinated installation: it is initiated by the client with their Orion representative, installed and partly configured by the Orion Salesforce Support team, and completed by the Practifi Support team, with your System Administrator taking ownership of permission sets, data mapping, and ongoing sync configuration. Most data flows from Orion into Practifi, with two-way sync available for Household and Household Member records, ensuring demographic updates made in either system stay aligned.

This article guides you through enabling the Orion integration: confirming prerequisites, installing the OrionConnect managed package, assigning permission sets, connec, and confirm that your user has the System Administrator profile or an |ting the Orion Sync, configuring data mappings, deploying Practifi Orion metadata, preparing your existing households for sync, testing with sample data, scheduling the sync, authorizing Orion Connect views, and understanding the data model. For guidance on how advisors and operations staff will work with Orion data day-to-day, see the companion article, Using the Orion Integration.

Prerequisites
Understanding the Integration Architecture
Installing the OrionConnect Package
Provisioning the Practifi License for the Orion User
Assigning Permission Sets
Setting Up the Orion Sync Connection
Configuring Data Mappings
Running the Initial Test Sync
Deploying Practifi Orion Metadata
Populating Orion IDs on Existing Households
Testing Sync With Sample Data
Configuring Page Layouts
Authorizing Orion Connect Views
Configuring the Sync Schedule
Running an Ad-Hoc Sync
Understanding Data Mappings
New Households Going Forward
Testing and Verification
Monitoring and Troubleshooting
Security and Data Privacy
Known Limitations

Prerequisites

Before you begin enabling the Orion integration, ensure your organization and Practifi environment meet the following requirements. Missing any of these will delay the install or cause sync errors after go-live.

Requirement	Details	How to Verify
System Administrator Access	The person managing the integration setup must have Salesforce System Administrator permissions in your Practifi instance.	In Practifi, navigate to Setup > User, and confirm that your user has the System Administrator profile or an equivalent role.
Practifi License for the Orion User	A Practifi license must be available for the Orion integration user account. Ops will provision this license through the Orion Integration License process on your client project.	In Setup > Users, confirm you have available Practifi user licenses. If you are near your limit, contact your Practifi Account Manager.
Orion Licenses for Connect Users	Each user who needs to view Orion data through Orion Connect must have an Orion license. Users without an Orion license can still benefit from synced data, but cannot use the Orion Connect Visualforce views or links.	Confirm Orion license counts with your Orion account manager. If you plan to use a Default User configuration, only that user requires an Orion license for outbound sync.
Coordination With Orion Support	Enablement begins with the Orion Salesforce Support team. They handle initial package installation and basic configuration before handing off to Practifi Support for additional setup.	Reach out to your Orion representative to initiate the integration. They will coordinate with the Orion Salesforce Support team to start the install process.
Coordination With Practifi Support	Practifi Support coordinates the metadata deployment, mapping configuration, and final cutover steps once Orion has installed the package.	Open a case with Practifi Support to confirm your enablement timeline, request the Practifi Orion metadata package, and align on data mapping assistance.
Orion Household IDs Available	Before testing or running a full sync, you must have Orion Household IDs for every existing Client in Practifi to prevent duplicate Household creation.	Ask your Orion representative to run a query in Orion that returns Household IDs and drop the export into your Practifi client SharePoint site.

Understanding the Integration Architecture

The Orion integration uses the OrionConnect managed package to create a secure, authenticated bridge between Orion and your Practifi instance. Once installed and authorized, the package exposes a set of Visualforce pages, including the OrionSync configuration page, which lets your System Administrator manage the connection, mappings, sync schedule, and history. Data flows are governed by per-object mapping rules, with most objects synced one-way (from Orion to Practifi) and a small set of objects configured for two-way sync.

Integration Flow

The Orion sync runs on a schedule that you configure in the OrionSync Visualforce page, typically once per day after Orion’s internal data refresh completes. Each run executes the following steps:

A scheduled Apex job initiates the sync at the configured time.
OrionConnect authenticates to Orion using the connection established on the Connection tab of the Orion Data Sync page.
For every Household in Orion that has its Sync to Force.com flag set, the sync pulls Household, Household Member, Account, Asset, and Receivable records and maps them to the corresponding Practifi objects.
Where two-way sync is enabled (Households and Contacts), changes made in Practifi are pushed back to Orion using the Sync Regulator field on each record.
Sync results, including any per-record errors, are written to the History and Errors tabs on the OrionSync page for review.

Data Flow Diagram

The following diagram illustrates how data flows between Orion and Practifi:

Orion (Portfolio Accounting and Billing)	OrionConnect Managed Package (Households, Contacts, Accounts, Assets, Receivables)	Practifi (Client Relationship Management)

Inbound (Orion to Practifi): Households, Contacts, Financial Accounts, Holdings, and Installments sync on the configured schedule.
Outbound (Practifi to Orion): Household and Contact demographic updates push back when two-way sync is enabled, and the Sync Regulator field is configured.

Key Technical Details

Integration Type: Managed package (OrionConnect App), installed directly into Practifi via a Salesforce package URL.
Authentication: Bi-directional OAuth that links a Salesforce identity to an Orion identity, established once from the Connection tab on the Orion Data Sync page. A Legacy Authorization (username/password) option is available under Show Advanced for service accounts that need to run scheduled syncs while not logged in to Salesforce.
Data Flow Direction: Inbound for Financial Accounts (Asset/Liability), Holdings, and Installments. Two-way for Households (Account) and Contacts (Household Members).
Sync Schedule: Configurable from the Schedule tab on the Orion Data Sync page, with multiple sync configurations supported. Daily runs are recommended after Orion’s end-of-day data is available.
Default User Option: A Default User can be configured in OrionSync so that all API calls operate under that identity. This means not every Salesforce user needs an Orion license to support the outbound sync.
Object Coverage: Five primary object mappings, covering Households, Household Members, Accounts, Assets, and Receivables.

Installing the OrionConnect Package

The OrionConnect managed package is installed directly into your Practifi org. Orion no longer requires a dedicated user account for installation; the package is installed by your System Administrator and then granted access by the Orion Salesforce Support team.

Please note: Throughout this article, the configuration page is referred to as Orion Data Sync, the page header shown in the UI. The underlying Visualforce API name is OrionSync, which appears in URLs and in Salesforce Setup.

Steps to Install the Package

Open the OrionConnect installation link in a browser where you are logged in as a Salesforce System Administrator: https://login.salesforce.com/packaging/installPackage.apexp?p0=04t6T000001piuvQAA.
On the install page, select Install for All Users and click Install.
When prompted, approve any third-party site access requests required by the package.
Wait for the install to complete. You will receive an email confirmation once the package is fully installed.

After the installation completes, grant the Orion Salesforce Support team temporary login access so they can complete the basic configuration on their side.

In Practifi, navigate to your personal settings by clicking your avatar and selecting Settings.
In the left navigation, click Grant Account Login Access.
Set the access duration to 30 days for the Orion Salesforce Support administrator.
Click Save.

Practifi Support will notify Orion via email to sme-salesforcesupport@orion.com once package installation is complete.

Provisioning the Practifi License for the Orion User

After the OrionConnect package is installed, the Orion integration user requires a Practifi license. Practifi provisions this license through an internal process tied to your client project.

Open a case with Practifi Support and request the Orion Integration License process to be kicked off on your client project.
Provide the username of the Orion integration user.
Wait for confirmation that the license has been applied.
Once confirmed, validate that the user has a Practifi license assigned by navigating to Setup > Users and reviewing the user’s record.

Please note: The Orion integration user must remain active and licensed for the duration of the integration’s use. Deactivating or removing the license will cause sync runs to fail until the license is restored.

Assigning Permission Sets

The OrionConnect package includes an Orion Integration permission set that grants access to the package’s objects, fields, Visualforce pages, and Apex jobs. Assign this permission set to every user who needs to interact with Orion data inside Practifi.

Assigning the Orion Integration Permission Set

In Practifi, navigate to Setup > Users.
Click the username of a user who needs Orion access.
In the Permission Set Assignments section, click Edit Assignments.
Locate the Orion Integration permission set in the Available Permission Sets list.
Click the permission set to move it to the Enabled Permission Sets column.
Click Save.

Assigning the Practifi Administrator Permission Set Group to the Integration User

If you are using a dedicated Orion integration user account for the connection, assign that user the Practifi—Administrator permission set group so the sync has the access it needs across Practifi objects.

Navigate to the integration user’s record in Setup > Users.
In the Permission Set Group Assignments section, click Edit Assignments.
Add Practifi—Administrator to the Enabled Permission Set Groups column.
Click Save.

Assigning the Orion License

The OrionConnect package is licensed at the user level. Each user who needs access to Orion-package objects, fields, and Visualforce pages must be assigned the Orion Connect license.

Navigate to Setup > Installed Packages.
Click Manage Licenses next to Orion Connect.
Click Add Users.
Select the users who need access and click Add.

Please note: Without an Orion license, a user cannot view Orion-package objects, fields, the Single Sign-On app, links, or dashboards. If a Default User is configured later in the Orion Data Sync page, only that user requires a license for the outbound API calls; other users still need their own license to view Orion Connect content directly.

Setting Up the Orion Sync Connection

After permission sets are assigned, the Orion integration user authenticates the connection between Orion and Salesforce using the Orion Data Sync page (Visualforce API name OrionSync). All steps in this section must be completed by the Orion integration user, since the linked identity is bound to the connection.

Opening the Orion Data Sync Page

Log in to Practifi as the Orion integration user.
Navigate to Setup > Visualforce Pages.
Locate OrionSync in the list and click the page name.
Click the Preview icon to open the Orion Data Sync interface in a new tab. The page header reads Orion Data Sync.

Tab Overview

The Orion Data Sync page exposes a vertical tab list on the left:

Connection: Authentication and Default User configuration.
Schedule: Sync schedules, Run Now, and recurring sync jobs.
Mapping: Field-by-field mapping for the five object pairs. The Mapping tab is hidden by default and only appears after you click Show Advanced on the Connection tab.
Permissions: Confirms the Orion Integration permission set and shows assigned users.
History: Per-run sync status and timing.
Errors: Per-record sync errors.

Screenshot 2026-05-08 at 10.24.04 AM.png

Linking Salesforce and Orion (Bi-directional OAuth)

The current OrionConnect package uses bi-directional OAuth as the primary authentication path. The OAuth flow links the user’s Salesforce identity and Orion identity together so data can sync in both directions and embedded Orion components render correctly. Follow the steps below as the Orion integration user.

On the Orion Data Sync page, click the Connection tab.
Click Link Salesforce. A consent pop-up appears.
Click Allow to grant OrionConnect access to your Salesforce org.
Click Link Orion and complete the Orion authorization to bind your Orion identity to your Salesforce identity.
Once linked, the Connection tab will display the message Your identity is fully linked to an Orion User, no further action is necessary. If the status shows otherwise, refresh the page.

Legacy Authorization (Optional)

Legacy Authorization stores an Orion username and password in a secure internal location. Use it only when the user under whom syncs are scheduled needs the sync to run while that user is not logged in to Salesforce. For most firms, the bi-directional OAuth flow above is sufficient, and Legacy Authorization is not required.

On the Connection tab, click Show Advanced.
In the Legacy Authorization section, enter the Orion username and password and save. The connection details (Status, Org, User, Name, Email, Entity) appear once the credentials are accepted.

Setting the Default User

Enabling the Default User toggle directs every Orion API call to operate under this user’s Orion identity, which reduces the number of Orion licenses you need across your firm. The Default User toggle is exposed under the Connection tab’s Show Advanced view alongside Legacy Authorization.

On the Connection tab, click Show Advanced.
Locate the Default User toggle.
Read the yellow warning note, which states: Setting this connection as default will cause all Salesforce users without set credentials to operate as this Orion user when updates are made. Please carefully consider your security needs before enabling the below feature.
Enable the toggle if your security model accepts that all updates will run under this Orion identity.

Please note: Enabling Default User means every API call to Orion will operate under this user’s identity, regardless of which Practifi user triggered the change. Plan your firm’s audit and compliance expectations accordingly.

Configuring Data Mappings

Once the Orion connection is established, the next step is configuring how Orion fields map to Practifi fields. The Mapping tab on the Orion Data Sync page controls every field-by-field translation between the two systems. The current mappings for each of the five object pairs are documented later in this article and on the Practifi Confluence enabling pages; coordinate with Practifi Support if you need clarification on a specific field.

Opening the Mapping Tab

On the Orion Data Sync page, click the Connection tab and then click Show Advanced. The Mapping tab is hidden by default and only appears in the left tab list after clicking Show Advanced.
Click the Mapping tab.
Review the warning message: These settings are intended for advanced users. Misconfiguration can cause data synchronization to become unstable or fail.
If the mapping interface appears grayed out, click the cancel button in the top-left corner of the warning at the top of the Mapping tab. This unlocks the mapping interface for editing.

General Mapping Rules

Apply the following rules consistently across all five object mappings:

Configure each field-by-field mapping per the standard mappings documented later in this article and verified with Practifi Support.
For any field that should not be synced, set the Salesforce Field column to << NOT SYNCED FROM ORION >>.
For the Orion API Return Mapping column, set the value to << NOT SYNCED TO ORION >> for every field except those explicitly mentioned in the mapping sheet.
To improve accuracy, consider setting all rows on an object to Not Synced first, then enabling each field according to the mapping sheet.
Always click Save after every change. Save before moving to the next object tab.
Unmapped fields cannot be left blank. If a field is not synced, set it explicitly to << NOT SYNCED FROM ORION >>.

Objects to Map

The Orion integration ships with five object mappings. Configure each one in the order below:

Orion Household to Practifi Entity (Account) — Two-way sync. Sync Regulator: Sync (OASP__Sync__c).
Orion Household Member to Practifi Contact — Two-way sync. Sync Regulator: Sync (OASP__Sync__c).
Orion Account to Practifi Asset/Liability — One-way sync (Orion to Practifi).
Orion Asset to Practifi Holding — One-way sync (Orion to Practifi).
Orion Receivable to Practifi Installment — One-way sync (Orion to Practifi).

Detailed field-level mappings for each object are described in Understanding Data Mappings later in this article. If you need clarification on an individual field, contact Practifi Support.

Running the Initial Test Sync

Once your mappings are saved and the metadata package has been deployed, the initial test sync from Orion to Practifi is typically performed by the Orion Salesforce Support team server-side, against a small subset of clients. There is no Start Batch button to click in the current OrionConnect package; the work is initiated from the Orion side.

Pre-Test Sync Verification Checklist

Work through the checklist below before requesting the test sync. Sending the request before these items are in place will likely cause rework, sync errors, or unintended data overwrites in your Practifi org.

Connection is fully linked: On the Connection tab of the Orion Data Sync page, confirm the connection status reads Your identity is fully linked to an Orion User, no further action is necessary.
Default User configured (if applicable): Confirm that the Default User toggle on the Connection tab’s Show Advanced view is set as your firm intends. The yellow warning has been read and accepted.
Mappings saved for all five object pairs: On the Mapping tab (under Show Advanced), open each of Household, Household Member, Account, Asset, and Receivable and confirm the mappings have been saved. Unmapped fields are explicitly set to << NOT SYNCED FROM ORION >> rather than left blank.
Metadata package deployed: Confirm with Practifi Support that the Practifi Orion metadata package (custom fields, flows, permission sets) has been deployed via Workbench.
Flows activated: All three flows (Sync Orion Rep with Owner; Copy Orion Registration Name to Asset Name; Installments Final Amount) are activated. Flows default to inactive on deploy and must be activated manually.
Workflow rules deployed: The three workflow rules (CopyFieldsForOrion, SetOrionAssetFields, SetOrionHHFields) have been deployed via the Practifi DevOps process.
Permission sets assigned: The Orion Integration permission set is assigned to every user who needs Orion access, and the integration user has the Practifi—Administrator permission set group.
Licenses verified: The Orion integration user has both a Practifi license and an Orion Connect license assigned. Spot-check advisor users who will use Orion Connect Visualforce views.
Orion IDs populated on existing Households: The pre-sync data exercise is complete — every existing Practifi Household has its Orion ID fields populated. Skipping this step is the most common cause of duplicate Households being created during sync.
Backups in place: Take a backup of any Practifi records that could be affected by the sync. The initial sync runs from Orion to Practifi, so existing field values in Practifi can change to match Orion when the sync runs.
Practifi Support on standby: Confirm Practifi Support is aware of the test sync window and available to review the results with you.

Requesting the Test Sync

Identify a representative sample of five to ten Households for the test sync, covering your common record types (Household, Organization, etc.) and configurations.
Coordinate with your Orion representative to set Sync to Force.com to true on the sample Households only. All other Households should be set to false so they do not sync during the test.
Reach out to the Orion Salesforce Support team (sme-salesforcesupport@orion.com) to schedule the test sync. Confirm all five object mappings are saved and the checklist above is complete.
Orion will run the test sync on the sample Households to validate field-by-field behavior.
Review the synced records in Practifi at the Entity, Asset/Liability, and Holdings levels. Open the Errors tab on the Orion Data Sync page if any records failed to sync.
If the test surfaces mapping or data issues, work with Practifi Support to adjust the configuration and request a re-run from Orion.
Once the test sync looks good, work with Orion and Practifi Support to confirm cutover for the rest of your client base.

Please note: For ad-hoc syncs after the initial cutover, use the Run Now button on the Schedule tab. See Configuring the Sync Schedule for the full ongoing sync configuration.

Deploying Practifi Orion Metadata

Practifi maintains a metadata package that includes the custom fields, flows, workflow rules, and permission sets required by the integration. The Practifi Support team coordinates the deployment of this package into your org.

Requesting the Metadata Package

In your Practifi Support case, request the latest Practifi Orion metadata package.
Practifi Support will provide a deployment link or attach the package to your case.
Confirm the deployment date and method (typically Workbench-based) with Support before proceeding.

Deploying the Metadata

Open Workbench (workbench.developerforce.com) and log in as a System Administrator.
Run a deployment validation against the Practifi Orion metadata package using the Workbench deploy method.
If validation succeeds, complete the deploy.
Once the deploy completes, manually activate every flow listed below. Flows default to inactive when deployed, so this step is required — if you skip it, the integration will sync data without the supporting automations and you will see incorrect Type, Client Stage, asset name, and Installment Final Amount values.

Flows Deployed

The metadata package includes the following flows. Each flow defaults to inactive on deploy and must be activated manually:

Sync Orion Rep with Owner: Synchronizes the Orion Rep field with the Practifi Client Owner. Sets Type to Household and Client Stage to Client on synced records.
Copy Orion Registration Name to Asset Name: Sets the Asset source to Orion and the Category to Managed Funds. Constructs the asset name using Registration Name, Registration Type, and Custodian.
Installments Final Amount: Calculates the Final Amount of an Installment based on the Initial Value and Adjustment fields synced from Orion.

Workflow Rules Deployed

Salesforce no longer permits new workflow rules to be created through the UI, so the following rules must be deployed via the Practifi DevOps process. Confirm with Practifi Support that these rules have been deployed before activating the sync schedule.

CopyFieldsForOrion on the Asset/Liability object.
SetOrionAssetFields on the Asset/Liability object.
SetOrionHHFields on the Account object.

Populating Orion IDs on Existing Households

Before enabling the sync against your full client base, the Practifi Support team performs a one-time data exercise to populate the Orion ID on every existing Practifi Household record. This step prevents the sync from creating duplicate Household records when Sync to Force.com is enabled in Orion.

Request a Household ID export from your Orion representative. They will run a query in Orion that returns the Household IDs for your firm.
Have Orion drop the export into your Practifi client SharePoint site or share it through your standard file transfer method.
Practifi Support will match each Orion Household ID to the corresponding Practifi Household record and populate the Orion ID fields on those records.
Confirm every existing Household has its Orion ID populated before proceeding to test sync.

Please note: If you intend for Orion to create new Practifi Household records (for example, in a brand-new Practifi org with no historical data), you can skip this exercise. The sync will create new records in Practifi as Households flow in from Orion.

Testing Sync With Sample Data

Before enabling the sync against your full client base, run a sample sync against a small subset of households. This catches mapping issues, identifies record-type problems, and validates that data lands in Practifi as you expect.

Pick a small representative sample of households (typically five to ten) that cover your common record types and configurations.
Update the Orion ID fields on the sample Households using the formats described above.
Coordinate with Orion to mark every other Household record’s Sync to Force.com flag as false, leaving only the sample records flagged true.
Have Orion run a full sync. Only your sample records should sync into Practifi.
Review each sample record at the Entity, Asset/Liability, and Holdings levels. Confirm field values, registrations, and relationships match Orion.
If you find issues, work with Practifi Support to adjust the mapping configuration. Re-run the sample sync after each change.
Once you are satisfied with the sample results, update Orion IDs on all remaining Practifi Households and have Orion mark the rest of the Households as Sync to Force = true.

The initial sync runs from Orion to Practifi, so values currently held in Practifi may change to match what Orion sends. Take a backup of impacted records before enabling the full sync.

Configuring Page Layouts

Once data is flowing, expose Orion data on the Client Household page layout so advisors can see portfolio information without leaving Practifi.

Updating the Client Household Page Layout

In Setup, navigate to Object Manager > Entity (API: Account) > Page Layouts.
Open the Client Household page layout.
Add the Orion Status field to the Client Household page layout in a visible location. This is a field addition, not an embedded page.
Embed the Orion Links Visualforce page (API name Orion_Links) as a new tab in the Financials section.
Embed the Orion Dash Visualforce page (API name Orion_Dash) as a new tab in the Financials section. Label the tab Orion Insights — the Orion Dash page renders behind a tab labeled Orion Insights, which is the label end users have been familiar with across Practifi documentation.
Save the layout.

Please note: The Visualforce page name in the current package is Orion Dash (Orion_Dash). The user-facing tab label remains Orion Insights across the Client Household layout and end-user documentation. Document them as two separate things: the page is Orion Dash; the tab the user sees is Orion Insights.

Lightning Record Page Considerations

When activating Lightning record pages, scope the activation to the relevant record type only. For example, if your Orion clients are configured as Organization records, apply the Lightning page to the Organization record type only.

If your Orion clients are stored on the Organization record type, work with Practifi Support to configure an additional flow that preserves the record type during sync. The default Orion behavior sets the Type field to Household, which can cause record type drift on Organization clients.

Authorizing Orion Connect Views

The OrionConnect package includes Visualforce pages that let advisors view Orion data inside Salesforce using their own Orion credentials. Each user must complete this authorization step on first use, regardless of whether a Default User is configured.

From the App Launcher, search for and select Orion Connect.
Click the Authorization button.
On the consent pop-up, click Accept.
Enter the user’s Orion username and password.
Click Submit. Once accepted, the user can access Orion data through Orion Connect Visualforce pages embedded in Practifi.

Please note: An Orion license is required to authorize Orion Connect views. Users without a license should rely on the synced data already available in Practifi records.

Configuring the Sync Schedule

After mapping is complete, the metadata is deployed, Orion IDs are populated, and the sample sync has been validated, configure the recurring sync on the Schedule tab of the Orion Data Sync page.

Navigate to Setup > Visualforce Pages.
Locate OrionSync in the list and click the page name.
Click the Preview icon to open the Orion Data Sync interface in a new tab.
On the Orion Data Sync page, click the Schedule tab.
Click Add to create a new sync configuration.
Select the appropriate Database for your firm.
In the Reps picker, select the Orion reps whose Households should be included in this sync configuration.
Set the Time dropdown to the cadence that matches your firm’s needs (for example, Updates every 10 min for incremental updates or a daily cadence for full refreshes).
Configure the Schedule field to control when scheduled runs fire.
Set the Full Sync Window dropdown to the duration the full sync is permitted to run (for example, 15 min).
Save the configuration. Repeat with Add if your firm needs multiple sync configurations across different reps or cadences.
Confirm with your Orion representative that scheduled run windows occur after Orion’s daily data refresh completes.

Please note: If you schedule the sync before Orion’s daily data is finalized, your Practifi records will reflect stale numbers for the rest of the day. Coordinate timing with your Orion representative to avoid this.

Running an Ad-Hoc Sync

After cutover, the recurring sync runs on the schedule you configured. If you need to trigger an unscheduled sync (for example, to pull a new client’s data immediately after enabling Sync to Force.com in Orion), use Run Now on the Schedule tab.

On the Orion Data Sync page, click the Schedule tab.
Select the sync configuration you want to trigger.
Click Run Now to start an ad-hoc sync.
Monitor progress on the History tab.
Review the Errors tab for any per-record errors. A successful run can still contain individual record errors.
Validate a sample of synced records by comparing Practifi records to their Orion counterparts.

Please note: Address all errors found during the initial sync before relying on subsequent scheduled runs. Persistent errors signal mapping or data issues that will compound over time.

Understanding Data Mappings

The Orion integration syncs five object pairs between Orion and Practifi. The current mappings live on the Mapping tab of the Orion Data Sync page; the summary below explains the relationship and key considerations for each pair. If you need clarification on a specific field, contact Practifi Support.

Orion Household to Practifi Entity (Account)

Orion Households become Practifi Entities (Accounts) with a Household_Client record type. The Orion ID field (OASP__Orion_Id__c) is the External ID and is the matching key that prevents duplicates. Two-way sync is enabled, so demographic changes made in Practifi (name, address, phone, email, salutation) push back to Orion through the Sync Regulator field. Performance metrics (MTD, QTD, YTD, one-year, three-year, five-year, and ten-year) sync inbound only.

Orion Household Member to Practifi Contact

Orion Household Members become Practifi Contacts with a Person record type. Each Contact is linked to its Household via the Primary Entity lookup populated from the Household’s Orion ID. Two-way sync is enabled for demographic fields. Most metadata fields (Personal_ID, Salutation, Send Statement, Website) are intentionally not synced.

Orion Account to Practifi Asset/Liability

Orion Accounts become Practifi Asset/Liability records with the Asset record type. This is a one-way sync from Orion to Practifi. Mapped fields include Account Number, Registration Type, Custodian, Bill Cycle, Bill Frequency, Bill Style, Cash Value, Initial Value, Realized and Unrealized Gains, Discretionary, Trading Blocked, Trading Instructions, Performance Metrics (MTD, QTD, YTD, twelve-month, thirty-six-month), Closed Date, and Management Style.

Financial Account sync criteria: Financial Accounts only sync from Orion if they meet at least one of the following: edited in the last 30 days, hold a non-zero value, or have at least one transaction within the last 30 days. Dormant accounts with zero value and no recent activity do not appear in Practifi. This is expected behavior, not a sync error.

Orion Asset to Practifi Holding

Orion Assets become Practifi Holdings, linked to their parent Asset/Liability via the External ID. This is a one-way sync from Orion to Practifi. Mapped fields include Holding Name, Balance, Price, As At (Price Date), Units, Product Code (Ticker), Segment Name, and Class Name. Most descriptive and categorization fields on the Orion side are intentionally not synced.

Orion Receivable to Practifi Installment

Orion Receivables becomes Practifi Installments. This is a one-way sync from Orion to Practifi. Mapped fields include Initial Value, Adjustments, Date, Type, and the Installment Name. The Installments Final Amount flow calculates the Final Amount based on the Initial Value and Adjustments synced from Orion.

Two-Way Sync Summary

Object Pair	Sync Direction	Sync Regulator
Household (Account)	Two-way	Sync (OASP__Sync__c)
Household Member (Contact)	Two-way	Sync (OASP__Sync__c)
Account (Asset/Liability)	One-way (Orion to Practifi)	Two-way sync not enabled
Asset (Holding)	One-way (Orion to Practifi)	Two-way sync not enabled
Receivable (Installment)	One-way (Orion to Practifi)	Two-way sync not enabled

New Households Going Forward

After the initial sync is complete, advisors and operations staff continue to create new clients in both systems. Use the workflow below to keep new clients matched correctly between Practifi and Orion and avoid creating duplicate Households.

Create a shell Household record in Practifi with minimal identifying information (name, basic demographics).
Wait for the corresponding Household to be created in Orion. Once it exists, populate the Practifi Household’s Orion ID fields. Coordinate with Practifi Support on the field values if you have not done this for new clients before.
In Orion, navigate to Portfolio Audit > Household, right-click the Household, and select Edit Household.
Open Options > Salesforce Integration and check the Sync to Force.com box.
Wait for the next sync run. Orion will sync to the existing Practifi Household record using the matching Orion ID instead of creating a new one.

Testing and Verification

After the initial sync completes, run through the verification checklist below before declaring the integration ready for daily use.

Connection status: On the Orion Data Sync Connection tab, confirm the linked-identity message appears and the Default User toggle (under Show Advanced) is set as expected.
Permission set assignments: Confirm the Orion Integration permission set is assigned to every user who needs to interact with the integration, and the Practifi—Administrator permission set group is assigned to the integration user.
Mapping configuration: Open each of the five object mappings on the Mapping tab and confirm the standard mappings documented in this article have been applied. Save before leaving each tab.
Metadata deployment: Confirm with Practifi Support that the metadata package, including the three flows and three workflow rules, has been deployed and activated.
Existing Household IDs: Spot-check a sample of Practifi Household records to confirm both Orion ID fields are populated using the correct format.
Sync history: Open the History tab on the Orion Data Sync page and confirm the most recent run completed with a status of Succeeded.
Errors tab: Open the Errors tab on the Orion Data Sync page and confirm there are no outstanding per-record errors. Investigate any errors immediately.
Page layout components: Open a Client Household record and confirm the Orion Status field is visible and the Orion Links and Orion Dash tabs render data.
Sample record validation: Compare a sample of synced Households, Contacts, Asset/Liabilities, Holdings, and Installments against their Orion counterparts to confirm field values match.

Monitoring and Troubleshooting

After go-live, monitor the integration regularly to catch sync errors and data drift early. The Orion Data Sync page is your primary monitoring surface.

Checking Sync Status

On the Orion Data Sync page, click the History tab.
Review the most recent run. Status values are:
- Processing: The run is in progress.
- Succeeded: The run completed without major exceptions, but individual record errors are still possible. Always check the Errors tab.
- Failed: The run did not start or did not complete.
- Queued: Another run is in progress and this run is waiting.
Click any run to drill into the timing, batch counts, and per-object stats for that run.

Checking Error Logs

The Errors tab on the Orion Data Sync page lists per-record errors for every run. Review this tab daily and act on errors promptly. A Succeeded status on the History tab does not guarantee the run was clean; individual records can still fail.

Common Issues and Solutions

Issue	Possible Cause	Resolution
Permission errors during sync	The Orion integration user is missing a Practifi license or the Practifi-Administrator permission set group.	Confirm a Practifi license is assigned and the Practifi-Administrator permission set group is in place. Contact Practifi Support if the license provisioning needs to be re-run.
Mapping errors	Fields are missing from the mapping or are not set explicitly to NOT SYNCED FROM ORION.	Reopen the Mapping tab on the OrionSync page, compare against the standard mapping sheet, and explicitly set unmapped fields. Save each object mapping before moving on.
Two-way sync failures	A record with an Orion ID is missing a Rep value, so the return sync from Practifi to Orion fails.	Confirm Rep values are populated on every Practifi record that should sync back to Orion. Add a validation rule or workflow if missing Rep values are common.
Duplicate Households created	A Household in Orion has Sync to Force.com checked, but no matching Practifi Household has the corresponding Orion ID populated.	Pause the sync, populate the Orion ID fields on the matching Practifi Households, merge any duplicate records, and resume the sync.
Address overwritten with stale data	A return-sync error left the Orion address out of date. The next inbound sync overwrote the new Practifi address with the older Orion value.	Investigate the original return-sync error in the Errors tab. Once resolved, update the field again in Practifi and confirm it pushes back to Orion on the next run.
Mapping interface grayed out	Orion has applied a mapping lockdown to prevent accidental changes.	Click Show Advanced on the Connection tab to expose the Mapping tab, then click the cancel button on the top left of the warning at the top of the Mapping tab to re-enable editing.

Troubleshooting Best Practices

Check the History and Errors tabs daily during the first two weeks after go-live.
Spot-check a small sample of records each week against Orion to catch silent mapping drift.
Track recurring error patterns in your support tooling so you can address root causes instead of clearing the same error repeatedly.
Schedule sync runs during off-peak hours and after Orion’s daily data refresh completes.
Review batch sizes and concurrency settings on the OrionSync Mapping tab if runs slow down or hit timeouts.

Security and Data Privacy

User Permissions and Licensing

Users must hold both a Practifi license and an Orion license to access OrionConnect views directly. The Orion Integration permission set must be assigned to every user who needs Orion data, and the Practifi—Administrator permission set group must be assigned to the integration user that performs the sync.

Default User and Compliance

When the Default User option is enabled in OrionSync, every API call into Orion operates under that user’s identity. This reduces license overhead but means audit trails on the Orion side reflect the Default User as the actor for any Practifi-originated changes. Plan your audit and compliance expectations to match.

Data Transmission and Encryption

All communication between Practifi and Orion uses encrypted HTTPS connections. Data stored in Practifi is encrypted at rest using Salesforce’s standard encryption. Bi-directional OAuth tokens are bound to the connection user’s linked identity inside the OrionConnect package and are not exposed in plain text on configuration screens or in logs. When Legacy Authorization is used as a fallback, the username and password are stored in a secured internal location managed by the package.

Data Access Controls

Each user who wants to view Orion data through Orion Connect Visualforce pages must complete the per-user authorization step using their own Orion credentials. Without that authorization, those Visualforce pages display an error rather than rendering data. Users can still see synced Orion data on standard Practifi records through the field mappings configured on the Mapping tab.

Audit Logging

The OrionSync History and Errors tabs log every sync run and every per-record error. Practifi’s standard system logs (Setup > Debug Logs) capture deeper technical detail when troubleshooting is needed. Retain these logs in line with your firm’s compliance requirements.

Sync Direction Controls

Sync direction is configurable per object on the Mapping tab. Most objects are inbound only by default, with two-way sync limited to Households and Contacts. This default reduces the surface area for unintended data changes flowing back to Orion.

Known Limitations

Be aware of the following limitations when planning your Orion deployment:

Rep field requirement for return sync: The return sync from Practifi to Orion requires every record with an Orion ID to also have a Rep value. Records missing a Rep will not sync back, and updates made in Practifi can be silently overwritten on the next inbound run.
Sync to Force.com flag controls inbound sync: A Household and its related records (Accounts, Holdings) only sync to Practifi if the Sync to Force flag is checked in Orion. Orion can default this flag on or off; coordinate with your Orion representative on the right default for your firm.
Duplicate Household risk: If Sync to Force.com is checked on an Orion Household whose ID is not matched to an existing Practifi Household, the sync creates a new Household record. Always populate Orion IDs on existing Practifi Households before enabling sync.
Disposed holdings zero out values: Orion zeros the value of disposed holdings and their parent assets. Practifi will reflect these values as zero on the next sync, by design.
Financial Account sync criteria: Financial Accounts only sync if they have been edited in the last 30 days, hold a non-zero value, or have at least one transaction within the last 30 days. Dormant zero-value accounts are excluded.
Record type mapping is static: Orion Sync does not support dynamic record type mapping. If your clients are stored as Organizations rather than Households in Practifi, you must configure additional flows to preserve the record type during sync. Discuss this with Practifi Support before enabling sync.
One Orion Household maps to one Practifi Household by default: The default behavior is one-to-one mapping. If your firm needs Orion Client Entities grouped under a single Practifi Household, work with Practifi Support on the supporting configuration.
Workflow rules require DevOps deployment: The CopyFieldsForOrion, SetOrionAssetFields, and SetOrionHHFields workflow rules must be deployed via Practifi DevOps because Salesforce no longer permits new workflow rules to be created through the UI.
Orion license required for Connect views: Users without an Orion license cannot view Orion-package objects, fields, the Single Sign-On app, or Orion Connect Visualforce pages. Default User configuration covers outbound API calls but does not replace per-user Orion licenses for direct package access.

If you encounter issues with the Orion integration or have questions about configuration, contact Practifi Support at support@practifi.com or through your Practifi customer portal. Provide details about the issue, including the run ID from the OrionSync History tab and any error messages from the Errors tab. For questions specific to Orion (portfolio data, performance calculations, Orion platform features, or Sync to Force.com flag defaults), contact your Orion account manager or the Orion Salesforce Support team at sme-salesforcesupport@orion.com.