If you run Logo, Mikro, Eta, Netsis, Luca or Zirve, your business carries years of critical data. Moving to Birasyo isn't about abandoning that data — it's about bringing it to a modern platform and layering AI and cloud capabilities on top. The plan below reflects the average customer migration we have delivered in 2024-2026.
Day 1 — Discovery
The first day answers the question: what data comes over? Working with a dedicated onboarding consultant you assemble the following exports from your current software: customer/supplier cards, products and stock cards, opening balances (payables, receivables, inventory), the last 24 months of invoices and dispatch notes, optional payroll records, and your chart of accounts.
The critical success factor is having your CPA (SMMM) in the same meeting. Your CPA validates the chart of accounts, VAT rate mapping, and the cutover date; we translate that into migration parameters.
Day 2 — Sandbox Trial Run
A dedicated sandbox tenant is spun up before we touch production. Within 24 hours the full data load lands there, and we run reconciliation:
- Customer ledgers are compared line by line against the old system
- Stock quantities are verified against a physical count
- Chart-of-accounts mapping is checked (each legacy account → Birasyo account)
- Opening balances are tallied against your trial balance
Any mismatch is fixed and the load is re-run. This step is included in the standard onboarding package — no extra fees.
Day 3 — Parallel Running
Once the sandbox passes QA, we cut a production tenant. You run Birasyo in parallel with your legacy system for 1-2 weeks, issuing identical invoices in both and reconciling at period close. Parallel running is the single most important trust-building step for the team.
Birasyo activates your free CPA seat during this phase. Your accountant logs in with their own credentials, pulls their reports, and files declarations as they normally would.
Day 4 — Training and Role Assignment
Beyond the Turkish video library, we run live online training targeted at roles:
- Accounting: invoices, dispatch, e-Ledger, tax declarations
- Sales / field: quotes, orders, dispatch, collections
- Management: dashboards, KPIs, approval workflows
- CPA: the dedicated CPA panel, audit trails
Roles and permissions (RBAC) are finalised the same day.
Day 5 — Full Cutover
On period close your new system becomes the single source of truth. Legacy data stays as a read-only archive accessible to your CPA for audit purposes, typically for 10 years. For the first 30 days your onboarding consultant holds a daily 15-30 minute check-in — anything that comes up is resolved same-day.
Three Common Misconceptions
"My 10 years of history will be lost."
No. Full transactional history is migrated; an archive export of the legacy system is also preserved. Your CPA has audit access for 10+ years.
"Rollout takes months."
Standard rollout is 5 business days. Complex customisations (SAP integration, custom reporting, bespoke workflows) are scoped as fixed-price packages — no surprise invoices.
"Is my data leaving the country?"
Data is encrypted and stored on Microsoft Azure Europe, with optional relocation to Azure Türkiye. We are registered with Türkiye's Personal Data Protection Authority (VERBİS) and provide a GDPR Data Processing Agreement to EU customers. See the Security page for details.
A migration plan is company-specific. Request a demo to get a consultant assigned and a bespoke timeline within one business day.