Profitdrive//
← Agent migration

FOR AI ASSISTANTS AND THE PEOPLE THEY SUPPORT

Profitdrive Migration Agent Guide

Use this guide when helping a user prepare data for Profitdrive. Profitdrive works alongside the accounting system: your job is to make source data understandable and reviewable so it can support operational control and forward planning, not to make business decisions on the user’s behalf.

START HERE

Read https://www.profitdrive.app/en/agent/migration/guide and help me migrate my company to Profitdrive. Work through the numbered plan one substep at a time. First ask whether I already have a Profitdrive tenant. If I do, select the Core, Structured or Advanced migration scope before asking about any Settings; then use current Settings as the baseline rather than repeat onboarding. Show proposed changes before writing; once I explicitly approve an action, carry it out if you have access, then verify and report.

DIRECT AGENT RESOURCES

A human guide, plus exact files for an agent.

This page explains the process for a person. The Markdown guide gives an assistant concise operating rules; the JSON index points it to one step and one import contract at a time. They describe the same migration, in formats suited to each reader.

MIGRATION SCOPE

Choose the smallest scope that covers the firm’s real operating model.

First establish whether the tenant already exists, then select the migration scope. Existing tenants begin from current Settings only after scope selection; the agent asks only about migration-relevant gaps or planned changes, not the questions already captured during onboarding.

Core

Firm working calendar, employer on-cost, margin targets, and the standard migration sequence.

Structured

Core plus teams, locations, location-specific employer on-cost, and optional grades.

Advanced

Structured plus cost currencies, exchange rates, and the later Xero actuals decision.

OPERATING RULES

Work with the person you are helping, not around them.

  1. 01

    Obtain approval before a write — then act

    Do not upload, overwrite, submit, create or connect without the user’s explicit approval. Once they approve a specific action, carry it out if you have access, then verify and report the result.

  2. 02

    Preserve the source

    Keep the original file unchanged. Create a separate proposed import version and make every adjustment easy for the user to review.

  3. 03

    Never invent business data

    Flag missing, conflicting or ambiguous values. Ask for a decision instead of filling in a rate, date, person, deal amount or delivery assumption.

  4. 04

    Explain what changed and what happened

    Summarise row counts, fields corrected, fields still requiring review and the import outcome. Do not call a migration complete until the user can review the resulting records.

CURRENT IMPORT AREAS

Use the tenant’s current template as the authority.

People

Prepare each person with the fields the current template requires. Cost fields differ by employment type: employees require annual compensation and contractors require a day rate.

Opportunities

The bulk opportunity import creates or updates opportunity headers. It does not create the detailed delivery and margin model for an opportunity.

Deal models

Deal models are imported from the selected opportunity using two files: one for model information and one for phases and rows. Prepare these after the opportunity exists.

Templates and required fields can evolve. Download the current template from the user’s tenant before changing a file, then use this guide to apply the working rules.

PUBLIC TEMPLATES

Use the download that matches the import you are preparing.

These header-only templates give an agent a clean starting point. Before submitting a file, compare it with the current template offered inside the user’s tenant. For the working calendar, start with that tenant’s country-specific starter so public holidays are included, then review local holidays and shutdowns.

DATE POLICY

Use ISO dates in agent-prepared files.

Write calendar dates as YYYY-MM-DD and monthly SG&A dates as YYYY-MM. ISO dates are accepted across tenant formats and avoid ambiguous values such as 03/04/2026. Local AU/EU and US formats may be accepted by the tenant, but should not be generated by default.

THE HAND-OFF

Leave the user with a clear next action.

For each file, say whether it is ready for review, ready to upload, already uploaded with a confirmed result, or blocked by a question only the user can answer.