I'm Rickey Burns, PMP. I help organizations bring people, technology, and processes together through complex acquisitions—without losing sight of the people doing the work.
01 MEASURABLE IMPACT
Results that reflect delivery, business scale, and a commitment to completing what I set out to do.
02 THE JOURNEY
I didn't start out managing integrations from behind a desk. I've done the hands-on work, solved the technical problems, managed the cutovers, and eventually became accountable for the delivery team.
03 CONTINUOUS IMPROVEMENT
We took a six-month integration playbook and streamlined it to three months—making the process easier to execute while keeping teams aligned and operations moving.
SHORTER
INTEGRATION CYCLE
04 SELECTED INTEGRATIONS
Three examples of the geographic complexity, team coordination, and business continuity involved in my integration experience.
05 HOW I LEAD
06 THE TECHNICAL DEPTH
From agency systems and SQL migrations to endpoint deployments and go-live coordination. My experience spans hands-on technical work and leading specialized teams.
The distinction matters: I've configured and supported systems firsthand, and I've led migrations involving additional platforms. This is the technology and delivery landscape I've worked in—not a claim that I'm a developer or administrator of every product listed.
Led transitions into enterprise agency platforms, with practical knowledge of acquired agencies' legacy environments.
Platform experience spans migration, implementation, support, and delivery coordination; responsibilities differed by product.
Explore the insurance technology work ↓Worked across SQL Server, legacy databases, SaaS applications, and custom systems during acquisition integrations.
A mix of direct systems experience and accountable migration delivery.
Started with site-level technology integration: workstations, hardware, network-connected devices, user readiness, and bringing acquired offices into a corporate environment.
Turned complex integration commitments into visible plans and decisions for executives, technical teams, and business stakeholders.
Coordinated requirements, conversion preparation, testing, deployment, cutover, and post-transition support while agencies continued serving clients.
Connected agency users, trainers, analysts, engineers, PMs, vendors, and executives. Kept the team informed and helped resolve adoption barriers before they became bigger problems.
INSURANCE TECHNOLOGY HANDS-ON + DELIVERY
Insurance technology has been the center of my integration work. I know what it takes to untangle legacy systems, move data, prepare users, and bring multiple agencies into a shared operating environment.
Led application and data migrations into Applied Epic. Connected the conversion plan to source-system discovery, field mapping, validation, cutover readiness, and the business teams who would use the new environment.
Hands-on systems engineering included migrating, configuring, integrating, and troubleshooting legacy agency and document-management applications, their databases, and the infrastructure they depended on. Not every acquired agency started from the same place.
Coordinated migrations and transitions involving related customer-service, digital-workflow, and benefits platforms. That meant planning how applications, data, staff training, and daily agency operations would work together after go-live.
From hands-on engineering to end-to-end technical delivery. These are environments I worked with directly—not simply technologies listed on a project plan.
SQL Server queries, database backup/restore, migrations, data mapping, cleanup, and validation.
AWS, Azure, Windows Server, Active Directory, VMware, Hyper-V, Citrix/RDS, file shares, permissions, and backups.
Current/future-state diagrams, application dependencies, retain/replace analysis, cutover runbooks, IIS, Linux, VPN, and DHCP.
07 THE FULLER STORY
The job titles changed as the scope grew. What stayed constant was ownership of the people, technology, and details that make an integration work.
Moved from managing individual conversions to accountability for the integration delivery function, leading two project managers, three engineers, and cross-functional trainers, analysts, business stakeholders, and vendors.
Led application and data transitions for acquired organizations, coordinating conversion work and the people needed to make the new tools usable.
Combined systems knowledge with project ownership, connecting what the existing technology could do with what a newly acquired agency needed on day one.
This is where integration became real: arriving on site, setting up technology, solving employee problems, and making sure people could get back to work.
08 HOW I WORK
My approach is grounded in doing the technical work first, then learning how to make it repeatable across teams and multiple acquired organizations.
Listen to agency users and leaders. Identify systems, data, hardware, critical workflows, and business dependencies before making promises.
Connect accountable owners, milestones, decision points, risks, vendors, training, and the teams responsible for each handoff.
Coordinate conversions, testing, deployments, communications, and go-live readiness while keeping operations moving.
Resolve open issues, stabilize the new environment, capture what worked, and improve the next integration instead of repeating the same problems.
09 BACKGROUND & CREDENTIALS
Project Management Professional (PMP) · Project Management Institute
Western Governors University · Graduate information technology studies in progress
Earlier service: United States Army · Personnel administration
This site tells the fuller story. If you need a résumé for a hiring process, I'm happy to share the most relevant version.
Request my résuméAPPLICATIONS I'VE BUILT FROM A PROBLEM TO A WORKING TOOL
Two projects that show the other side of my experience: translating messy, real-world needs into working software that people can actually use.
Designed and built a browser-based knowledge hub to make scattered agency information understandable and useful during integration work. It brought together profile details, technology inventories, operating practices, and acquisition history in one place.
Internal work: source records and company data are not published.
Built a local-first, multi-course study application designed around short sessions, real feedback, and easy movement between desktop and phone. It turns objectives, missed questions, and visual practice into a focused study flow.
Personal project with local-first data and optional cross-device sync.
What these projects say about how I work: I can translate business or learning problems into usable interfaces, organize messy information, and take a working application through testing and refinement—not just write the plan.
THE ONE-PAGE VERSION
A visual summary of my progression, integration experience, and the business outcomes that matter most.
Get the executive case study
1 PAGE · PDF
LET'S CONNECT
I'm always interested in conversations about integration leadership, technology transformation, and building teams that deliver.