An Epic account merge streamlines your digital identity by combining multiple logins into a single, coherent profile. This process reduces friction, improves security, and keeps your data synchronized across products.
Below you will find a structured overview, detailed operational guidance, and real user questions to help you plan and execute a smooth merge.
| Account Type | Current Status | Intended Status After Merge | Priority |
|---|---|---|---|
| Personal Trial | Standalone, limited seats | Merged into Organization Pro | High |
| Organization Admin | Active, full permissions | Retains admin role post-merge | High |
| Legacy Billing Contact | Separate auth system | Unified identity, single sign-on | Medium |
| API Integration User | Service key based | Migrated to OAuth app role | Medium |
Preparing Data and Permissions
Inventory Active Identities
Start by listing every email, username, and external ID that currently accesses your Epic services. Verify last login dates and note any dependencies such as custom scripts or third party tools.
Review Role and License Assignments
Confirm that roles, permissions, and licenses are up to date before the merge. Align them with the intended post merge structure to avoid disruption in access.
Executing the Merge Workflow
Validation and Pre Checks
Run conflict detection tools to identify duplicate profiles, overlapping permissions, or mismatched billing records. Resolve conflicts early to reduce rollback scenarios.
Final Merge and Verification
Initiate the merge during a low activity window, monitor progress in real time, and confirm that data, roles, and integrations behave as expected immediately afterwards.
Post Merge System Integrity
Data Consistency Checks
Audit critical datasets, audit logs, and reporting dashboards to ensure continuity. Address anomalies quickly to maintain stakeholder confidence.
Communication and Documentation
Notify impacted users about the new unified identity, share updated login procedures, and update internal documentation to reflect the merged account topology.
Integration and Access Management
Single Sign On Configuration
Update SSO settings to point to the new primary identity, ensuring that authentication flows remain seamless for employees and partners.
API and Automation Updates
Revalidate API tokens, webhook endpoints, and integration keys against the new account ID to prevent service interruptions in automated workflows.
Operational Best Practices
- Complete a full inventory of identities and integrations before starting the merge.
- Run simulated merges in a staging environment to uncover edge cases.
- Schedule the final merge during a low activity maintenance window.
- Communicate clear timelines and expected outcomes to all stakeholders.
- Monitor key systems intensively in the first 24 to 72 hours post merge.
FAQ
Reader questions
Will merging accounts affect my historical activity logs?
Historical activity logs are preserved and linked to the merged profile, ensuring continuity of audit trails and compliance records.
Can I reverse an account merge if something goes wrong?
You can initiate a rollback within the allowed timeframe by following the documented revert procedure, which recreates the prior accounts where feasible.
What happens to custom permissions assigned to the old accounts?
Custom permissions are recalibrated based on the new role map, with a compatibility check that flags potential over privileged access for review.
Will third party integrations automatically recognize the merged account?
Third party integrations require manual re authentication and minor configuration updates to recognize the new unified identity.