Studio Ninja Data Migration to Stelaah

Preserve meaning before moving rows.

An export is not yet a migration plan. Each source field must map to a canonical client-work object, and every open commercial record must be reconciled before cutover.

Start with active clients and future commitments. Keep the source system readable until contracts, balances, scheduled work, and imported counts have been verified.

Inventory records and exports

List available exports, attachments, document downloads, identifiers, statuses, currencies, dates, owners, and relationships. Record any source data that cannot be exported.

Define the canonical mapping

Map organizations, people, opportunities, projects, tasks, files, forms, proposals, contracts, invoices, payments, and notes to their correct Stelaah records.

Clean and preserve identifiers

Normalize obvious duplicates and invalid values while retaining the original source identifier in an import reference field or migration log.

Import one controlled sample

Use a small set containing active, completed, overdue, multi-contact, and exception cases. Validate relationships and permissions before expanding.

Reconcile active work and finance

Compare record counts, future dates, signed documents, open tasks, invoice balances, payment evidence, and client access.

Cut over with a rollback window

Choose a date, freeze source edits, complete the final delta, communicate the new workflow, and retain the source as a read-only archive until sign-off.

Final checklist

• Source export retained unchanged
• Field and status mapping approved
• Original identifiers preserved
• Controlled sample reconciled
• Active contracts and invoices checked
• Future dates and owners confirmed
• Client access tested
• Source archive and rollback window documented