Data Migration

• Onboarding·Data Migration

  How long does onboarding take?

  It depends on the size of your portfolio and the state of your current environment, but a landlord under 100 units is typically live in under 30 days, and a mid-size operator around 500 units in four to six weeks. What moves that timeline most is whether your bank reconciliations, rent roll and renewal management are up to date going in. Our team assesses where you actually stand before quoting you a date, because no two portfolios are alike.

• Onboarding·Data Migration

  How do I get my data out of my current system?

  Our team has built migration playbooks for Hopem, Building Stack, QuickBooks, Yardi Breeze, PlexFlow and Proprio, and works with your team to extract data properly from your incumbent system and map it into the Kompas database using our migration tool. We also use the move to scrutinize the data coming out of your old system for accuracy, completeness and validity, which is usually the first time anyone has looked at it closely in years.

• Onboarding·Data Migration

  When do we actually go live?

  Go-live is scheduled at the start of the month so your books cut over cleanly, with a proper cut-off between the old system and the new one. That timing is not administrative preference — a mid-month cutover leaves a partial month split across two sets of records, which is exactly the mess a migration is supposed to avoid. Everything before the cut-off stays in your old system's history; everything after it is in Kompas.

• Onboarding·Data Migration

  Do you have a migration playbook for Hopem?

  Yes — Hopem is one of the systems our team has built a documented migration playbook for, alongside Building Stack, QuickBooks, Yardi Breeze, PlexFlow and Proprio. That means the extraction and the mapping into the Kompas database follow a path we have walked before rather than being figured out on your data. A CPA onboarding lead runs the migration and validates what comes across.

• Onboarding·Data Migration

  Do you have a migration playbook for Building Stack?

  Yes — Building Stack is one of the systems we have a documented migration playbook for. Operators moving off it are often running a separate accounting file alongside, most commonly QuickBooks, and the migration consolidates both into one set of books rather than recreating the split. Our team extracts from the incumbent system, maps into Kompas, and validates the result before go-live.

• Onboarding·Data Migration

  Can you migrate our books off QuickBooks?

  Yes — QuickBooks is one of the systems our team has a migration playbook for, and it is the most common accounting file we consolidate. Because Kompas is accounting-first, the general ledger you move into is the same one your leases, rent, maintenance and payables post to, so the QuickBooks file does not get replaced by a second system running beside a property management tool. A CPA onboarding lead handles the move.

• Onboarding·Data Migration

  Do you have a migration playbook for Yardi Breeze, Hopem or Proprio?

  Yes — Yardi Breeze, PlexFlow and Proprio are all systems our team has built documented migration playbooks for, along with Hopem, Building Stack and QuickBooks. If your system is not on that list, the migration still runs the same way: extraction from the incumbent, mapping into the Kompas database through our migration tool, and validation by the CPA leading your onboarding.

• Onboarding·Data Migration

  What if my current data is a mess?

  That is expected, and the migration is where it gets addressed. Our team scrutinizes the data coming out of your old system for accuracy, completeness and validity rather than copying its problems into a new platform, and flags what needs a second look before it goes live. Being behind on bank reconciliations or rent roll maintenance will lengthen the timeline, which is why the assessment happens before a date is quoted.

• Onboarding·Data Migration

  Does my historical data come across, or do I start from scratch?

  Migration starts with your opening balances, which move over by trial balance so your books start clean in Kompas rather than carrying years of formatting quirks from your old system. Your chart of accounts, bank setup and entity structure carry over exactly as they need to for your portfolio. Your previous system's detailed history remains where it is, which is why the cut-off at the start of a month matters.

• Onboarding·Data Migration

  How disruptive is switching platforms, really?

  The honest answer is that it costs your team two to three hours for the process review, several hours a week for two to three weeks during migration, and up to six hours of training. Go-live at the start of a month keeps your books from being split across two systems mid-period, and a CPA leads the whole thing. The friction is real, which is why the structure exists rather than a promise that it will be effortless.