Esc

↑↓ move↵ openIndex · Pagefind
Data / Migration guide

Migration guide

A step-by-step plan for moving your company to os.construction, in the order that works, from company setup and people to projects, open items, schedules, accounting balances and CRM contacts, then verification and cutover.

On this page

Moving to os.construction is a sequence: set up the company, bring people in, create projects, then load open work, schedules and opening balances, check them against your old system, and cut over. This page lays out that order and points to the screen for each step. Most of it is done by a company admin.

Want a dated plan for your own company first? Try the free migration planner.

What comes in, and how

What Where it goes How it comes in
Company lists: stages, types, regions, offices, trades, departments Company Admin Entered by hand. See Company settings.
Your staff Company members Invitations, or SCIM from your identity provider. See Invite your team.
Projects Projects Created in the app, from standard defaults or a template project. See Your first project.
Project directory, RFIs, submittals, punch items, observations, daily logs, documents, prime contracts, commitments A project The Migration page, from one supported project management system. See Run an import.
Project cost codes and budgets A project’s Admin and Budget tools Cost codes come from the project’s starting defaults or a template project, and can be edited; budgets are entered in the Budget tool. Not part of the Migration import.
Schedules A project’s Schedule tool P6 XER, P6 XML or Microsoft Project XML file import. See Import from P6 and Microsoft Project.
Chart of accounts, vendors, customers, cost codes, open AP and AR, opening trial balance, journals, payroll year-to-date Company Accounting Accounting Imports, reviewed and approved before anything posts. See Accounting Imports.
CRM contacts Company CRM Import company contacts, a reviewed CSV import. See CRM.

Drawings, specifications and photos aren’t imported by the Migration page; upload current sets in the project’s Drawings, Specifications and Photos tools. For the full list of what the project import covers, see Importing from your current stack.

Before you start

  • Pick a cutover date. Usually a month-end, after that month’s billing and cost are final in the old system. Your opening balances, open AP and AR and open items are all “as of” this date.
  • Pull reports from the old system for that date: open item logs (RFIs, submittals, punch), commitment and contract logs, job cost detail, AP and AR agings and the trial balance. You’ll reconcile against them.
  • Decide about the sample data. Trial workspaces start with the Riverside sample company, including sample accounting books. Opening balances can only be imported into an empty ledger, and anything you add inside a sample project is removed along with the sample. Remove the sample before you load your own books and jobs: Company Admin → Sample data → Remove sample data. See Company settings.

The plan

  1. Set up the company

    In Company Admin, fill in the lists every project draws from: Project Stages, Project Types, Project Regions, Offices, Trades and Departments. Review the Permission Templates and adjust them before anyone else joins. See Company settings and Set up permission templates.

  2. Bring in your people

    Invite your staff from Company Admin → Invitations, or connect your identity provider under Company Admin → SCIM. Make your other administrators company admins in Members. See Invite your team and SCIM provisioning.

  3. Create your projects

    Create each active job with New project on the Projects page or in Company Admin → Projects. Under Start from, Standard defaults gives a starter CSI cost code set; Copy an existing project copies a template project’s cost codes, team permissions and tool settings (no records). Then adjust each project’s cost codes in its Admin tool → Cost Codes. See Your first project and Cost codes and budgets.

  4. Import open project records

    On the Migration page (app.os.construction/companies/<your company>/migration), create a job per project: choose the source, the target project and the scopes, and start with Dry run (count only, no writes). When the counts match the old system, create a Live (import into project) job and run it. The directory is imported first, so RFIs, submittals and commitments point at the right people and companies. See Run an import.

    If your system isn’t supported by the Migration page, enter open items in each tool by hand, starting with the Directory.

  5. Add outside people to projects

    Imported directory people and companies land in each project’s Directory. Give each person who should sign in a Project Permissions Template, and invite or add anyone missing. See Invite your team.

  6. Load budgets

    Enter each project’s budget in the Budget tool against its cost codes, as of the cutover date.

  7. Import schedules

    In each project’s Schedule tool, use Import file with a P6 XER, P6 XML or Microsoft Project XML file. Review what was read, then adopt it into the native planner. See Import from P6 and Microsoft Project.

  8. Import accounting balances

    In Accounting Imports, in this order: the chart of accounts, vendors, customers and cost codes; then open AP and open AR as of the cutover date; then the opening trial balance for the same date. The preview compares each control account with its open documents, and any difference blocks the import. Add employee payroll year-to-date before the first payroll run. See Accounting Imports and Imports and integrations.

  9. Import CRM contacts

    In the company CRM, open Import company contacts, select a UTF-8 CSV (up to 200 contacts per file), map the External ID, First name and Last name columns, review every row, and create the contacts. See CRM.

Verify before you go live

Check each area against the reports you pulled for the cutover date.

  • Project records: on each Migration job, compare Fetched, Created, Updated, Skipped and Failed with the old system’s counts, and read every failure in the Run log. Fix the cause (often a missing person or company) and re-run the same job; it updates what it already created instead of duplicating it.
  • Open items: spot-check open RFIs, submittals and punch items, their ball-in-court and due dates, job by job.
  • Contracts: compare prime contract and commitment values with your contract logs.
  • Budgets: compare each project’s budget totals with job cost detail.
  • Books: each accounting import reconciles to source control totals before approval. After applying, compare the trial balance and AP and AR agings with the old system.
  • Access: have one person per permission template sign in and confirm they see what you expect.

Cut over

  1. Freeze the old system

    At the cutover date, stop entering new work in the old system once that period’s billing and cost are final.

  2. Run the final imports

    Re-run each live Migration job to pick up anything that changed since the last run, and apply the accounting imports as of the cutover date.

  3. Start new work in os.construction

    New RFIs, daily logs, commitments, bills and invoices go into os.construction from here on.

  4. Keep the old system read-only

    Keep it for history you didn’t bring over, at least until your first close in os.construction is done.

Keep exploring

Related across os.construction

Run it on your own project.

Start a 14-day free trial. Want a say in what ships next? Join the founding program.

Your role (optional)

14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →

Ask the OS

Reading this page

Ask anything about this page. Answers use what you're reading as context.

Suggested

    AI · may be imperfect · sample data where shown

    Open file