Migrate · facts captured 2026-08-24

Leave PracticePro 365 without losing the month.

Map a native Dataverse or practice export. Clients first, then work, then time. Opening WIP keeps the date it was incurred and does not hit current-period revenue. Email and calendar reconnect from Microsoft 365 or Google — they are not imported from PracticePro. Confirm counts before cutover.

Nominative guide, not a partnership. No API keys, no endpoint list, no importer internals. Those stay behind login for clients. Tax prep stays last. ficary has not earned SOC 2, ISO 27001, or a HIPAA attestation.

The move

  1. Export the client list and the books you can open.
  2. Map that file. Clients first, then work, then time.
  3. Reconnect the bank and email. Do not import mail.
  4. Opening WIP keeps the date it was incurred.
  5. Tax prep stays where it is.

Stay on PracticePro 365 when

Choose PracticePro 365 when Dynamics is already the operating system and you do not need Google as a first-class surface.

Move when

Choose ficary when the firm has to close, age unbilled work on any date, land opening WIP without booking it as this month’s revenue, and keep client files off a shared model pool.

ficary vs PracticePro 365 · PracticePro 365 alternatives · all migration guides

Practice + books

Map a native export. Confirm counts.

Write us when you are ready to leave. Do not re-key a ficary workbook.