Migrate · facts captured 2026-08-25

Leave FloQast without losing the month.

If FloQast still closes a file you keep, finish that month there. Export the books. Map the CSV. Do not claim we replace close-on-ERP.

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. Finish the in-flight close on the ERP FloQast sits on.
  2. Export the books. Map the CSV in Settings → Migration.
  3. Reconnect the bank. Do not re-key.
  4. New leftovers land in the ficary inbox. That is the close loop here.

Stay on FloQast when

Choose FloQast when a controller team is closing an ERP they will keep and needs reconciliations, flux, or SOX evidence on that file.

Move when

Choose ficary when an owner or a CAS firm needs leftovers, as-of WIP, and work on one product — not another close desk on Intuit or Oracle.

ficary vs FloQast · FloQast 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.