Migrate your BigTime data

Projects are the central organizing entity in BigTime. We migrate Projects with all standard fields (status, dates, budget, client assignment) plus any active Custom Fields. Archived Projects are migrated as inactive records to preserve historical context without cluttering the destination.

Staff records including name, role, department, billable rate, and cost rate are migrated. We map BigTime's Staff permissions to destination Role or User records, preserving who was assigned to which project.

Clients are the billing entity in BigTime. We carry over Client records with contact details, billing address, and payment terms. Where the destination uses a different CRM terminology (Accounts, Contacts), we merge or split as required by the target schema.

Time entries are migrated with project association, staff member, date, hours, billable/non-billable flag, and optionally the task-level detail. We flag any time entries already invoiced versus Work-in-Progress so the destination does not double-count billing.

Expense records include project association, expense code, amount, date, vendor, and receipt attachment references. We map BigTime's expense codes to destination categories during migration.

Invoices and invoice drafts migrate with line items tied to time entries or expenses. Already-sent or paid invoices are migrated as historical records with a closed status; draft invoices require special handling to avoid triggering billing on the destination system prematurely.

Custom Fields on Projects are fully supported but require field-level mapping since value types vary (text, dropdown, checkbox, monetary, URL). We preserve the field label and all populated values, converting types where the destination schema requires it.

Staff assignments to projects and scheduled hours migrate as Resource Allocations. Where the destination uses a different scheduling model (e.g., sprints or capacity planning), we map allocations to the closest equivalent object and flag gaps in translation.

BigTime's Scheduled vs. Actual report captures planned hours/cost/revenue against tracked values. We migrate these as a linked dataset rather than a single object, preserving variance calculations as custom fields on the destination Project.

File attachments on Projects, Expenses, and Time Entries are migrated as references or linked blobs where the destination supports attachments. File metadata (filename, type, size, uploader) is preserved; inline images in rich-text fields require format conversion.

Tags applied to Projects or Expenses migrate as label or category strings. Where the destination uses a hierarchical taxonomy, we flatten tags into comma-separated lists and flag for manual reorganization if needed.

Integration configuration records (OAuth tokens, sync rules, field mappings for QuickBooks and Salesforce) do not migrate because they are platform-specific credentials and endpoint configurations that have no equivalent in other systems. We document which integrations were active so the customer can reconfigure them post-migration.

The Data Warehouse feature is a connection credential for BI tools (Power BI via Delta Sharing) and does not represent business data itself. We do not migrate this credential; we migrate the underlying data through our standard export pipeline instead.