BC Solutions is an independent Yardi consulting firm that plans and runs data migrations into Yardi Voyager and Yardi Breeze. Whether your data lives in MRI, RealPage, Sage 300 CRE, Skyline or an older Yardi database, we map your chart of accounts and entities, then clean and load the data and tie balances back to the old system before you go live.
Moving to Yardi From
Each of these projects moved a working portfolio into Yardi with its balances and history intact, and no two of them started from the same place. The source system, the portfolio and the deadline changed every time, but the goal didn't: a first month-end in Yardi that closes cleanly, with numbers the accounting team already recognizes.
Migrated a Queens, Brooklyn and Manhattan portfolio from MRI to Voyager, then stayed on for three years of support, from bank reconciliations to custom reporting.
Read the Case StudyGot a struggling commercial implementation back on track, moving 17+ retail properties off MRI with full lease data, CAM recovery setup and historical trial balances.
Read the Case StudyMoved one of the last Yardi DOS installations to Yardi Breeze Premier in the cloud, carrying decades of legacy data into the new system.
Read the Case StudyMoved a multifamily operator from Breeze to Voyager across California, Texas and Colorado, deploying 17 ancillary products along the way.
Read the Case StudyThe BC Solutions team migrated us from MRI to Voyager and trained our team to get the most from Yardi. Since implementation, they have been a valuable partner, helping us with bank reconciliations, divestments, and changes to our internal structure.
A migration moves your records into the Yardi setup your Yardi Voyager implementation creates, and it has to prove they arrived intact before anyone closes a month on them. The table below covers the areas most migrations touch and how we check each one, though the exact list gets settled during scoping.
| Data area | What moves | How we check it |
|---|---|---|
| Chart of accounts and entities | Account structure, entities, properties and charge codes, mapped to the setup your team will use in Yardi | Mapping review with your accounting team, then a trial balance by entity after each test load |
| Properties, units and leases | Property, unit and lease records, including rent schedules and key lease terms, for multifamily and commercial portfolios | Rent roll compared with the old system, property by property |
| Tenant and resident balances | Open charges, prepayments and security deposits for each tenant or resident | Receivables aging and deposit totals tied out to the old system |
| General ledger history | Opening balances plus the history you decide to keep, with older detail often archived | Trial balances compared for each period you bring over |
| Vendors and payables | Vendor records and the open invoices you'll pay after cutover | Open payables reconciled before the first check run in Yardi |
| Bank accounts | Bank accounts and their reconciliation starting points | Book balances matched to the last reconciled statement |
| Commercial recoveries | Recurring charges, CAM pools and recovery setup for commercial leases | Recovery setup reviewed against lease terms before the first reconciliation |
| Reports | The financial and operational reports your owners, lenders and staff rely on | Old and new versions compared side by side before go-live |
How much history to bring is a judgment call. More history means more mapping and more testing, but too little leaves your team digging through the old system every time an auditor or lender asks a question. For Woodfield Development, we worked through historical data conversions in Yardi Voyager while aligning investment accounting and construction job cost.
We run migrations in six phases, the same sequence our MRI-to-Yardi migration playbook walks through in detail. Scoping sets a cutover date around your month-end close, and every phase after it is there to protect that date, because a migration that slips past a close usually means running two systems for another month.
We inventory your data, decide what moves and what gets archived, and set the cutover date around your close.
We pull data from the old system and review it for duplicates, gaps and formatting problems before anything loads.
Accounts, entities, properties and charge codes are mapped to the Yardi structure your team will actually use.
Opening balances, open items, deposits and bank reconciliation starting points carry over, so your first close in Yardi works.
Test loads are compared with reports from the old system, then your team works real transactions before go-live.
We train your staff, support the first month-end and stay available afterward.
Every platform stores its data a little differently, so the right starting point depends on what you're leaving behind. If you're planning a move, begin with the guide for your current system, since most of them walk through what to map into Yardi and what to test before you go live.
Module mapping, data checklists and a timeline framework for moving from OneSite to Voyager.
Read the checklist MRIWhat an MRI-to-Yardi move involves, drawn from 23-property and 2M sq ft portfolio conversions.
Read the guide Sage 300 CREAccounting, job cost, vendors, leases and reports for Sage 300 CRE (Timberline) users.
Read the guide SkylineProperties, leases, tenants and charges for teams moving off SS&C Skyline.
Read the guide SpectraProperties, tenants, leases and go-live readiness for Spectra users.
Read the guide EntrataAccounting, resident operations, reporting and migration readiness, side by side.
Compare the platforms AppFolioBreeze, Voyager and AppFolio compared, including migration readiness.
Compare the platforms Senior LivingCensus management, care-level billing and implementation planning for senior living communities.
Read the guideMigrations start for different reasons, and each one changes where the risk sits. These are the situations we hear about most often, each paired with a client who's been through it, so you can see what the work looked like in practice before you decide whether you need help with yours.
Moving off MRI, RealPage, Sage or an in-house system means translating years of setup into Yardi's structure, and the old system's habits don't always have a direct equivalent. Planning the cutover around your month-end close, with time for at least one full test load, keeps the first month in Yardi from turning into a cleanup project.
Acquisitions bring someone else's database with them, usually on a deadline set by the closing date rather than by anyone's project plan. Each seller's data arrives in its own shape, which is why the mapping matters as much as the load itself. For Laramar Group, which has grown through acquisitions, our property onboarding work across several markets has included Y2Y mapping and data migrations.
As portfolios grow, some operators move from Breeze to Voyager for a broader set of modules, and that move is a migration in its own right. HK Property Management made it across 12 communities in about three months, and we deployed 17 ancillary products along the way, which is the kind of scope that's easier to plan than to improvise.
If a migration has stalled or the numbers won't tie out, an outside review can usually find where it went wrong and get it moving again. When Carolina Holdings' Voyager Commercial implementation was struggling, we stepped in and got it back on track, moving 17+ retail properties off MRI with their historical trial balances.
Your owners and lenders expect the same reports after go-live as they got before it, and they won't wait for a new system to settle in. For Trinity, we built 14+ custom Spreadsheet Server reports that kept critical financial reporting available through a major Yardi platform migration, so the numbers people relied on were still there while everything underneath them changed.
A migration only pays off if your staff can close the month in Yardi without calling for help every day. Training and first-close support are part of how we run every project, and the work often continues well past go-live, as it did for Pistilli Management, which kept us on for three years.
Alex Doggett
Senior Consultant
Led the Carolina Holdings and Meadows Commercial migrations.
Missy Ham
Director of Technical Consulting
Led our reporting work for Trinity through its platform migration and contributed to our MRI-to-Yardi migration playbook.
Rick Hunt
Senior Consultant
Custom report writer and data migration specialist.
Most migrations bring over your chart of accounts and entities along with your property and lease records and the open balances that go with them. Bank accounts come across too, plus as much general ledger history as you decide to keep, while older transaction detail is often archived instead. We settle the list during scoping, before any data moves.
Enough to run the business and answer the questions your auditors and lenders will ask, but not so much that mapping and testing drag on for months. Many operators bring opening balances plus a few years of history, then archive older detail somewhere the team can still reach it. We'll help you make that call during scoping, before it affects the schedule.
It depends mostly on portfolio size and how much history you bring, and the source system matters too. For reference, HK Property Management's move from Breeze to Voyager ran from May to July 2024, while Meadows Commercial's migration from DOS to Breeze Premier ran from June to December 2025. We'll build the schedule around your month-end close.
We compare reports from the old system with the same reports in Yardi, starting with the trial balance for each entity, the rent roll and the receivables aging. Any difference gets traced to a mapping or data issue and fixed before the next test load, and once the numbers match, your team tests real transactions before go-live.
Yes. When Yardi's implementation team is involved, BC Solutions works alongside it and your staff as an independent consulting firm. We concentrate on your data and reports, and on getting your team comfortable running the system after go-live, so nobody's left guessing who owns which part of the work.
An implementation sets Yardi up to run your business, from configuration and workflows to security and training. A data migration moves your existing records into that setup and proves they arrived intact. Most projects need both, and the migration often sets the pace, because every mapping decision depends on how Yardi is configured.
Tell us where your data lives today and when you need to be live. We'll map out what the migration involves and how long it should take, and if one of our guides already covers everything you need, we'll say so.
