Implementation Guide / OmindTech Journal

Distinguishing Initial Data vs. Migration Projects: Boundaries of the Workspace Manager's Role

Do not let a backlog of legacy archives stall the setup of your team's workspace. Learn the boundaries of a workspace manager's independent tasks to configure users, roles, and initial data in Orkesa, and when data migration needs to be discussed within a separate scope.

A little room to read.
An operational workflow specialist stands by a modular timber organizer, separating green active files from terracotta archival boxes.

Why Is Day One of Implementation Often Stalled at the Admin's Desk?

In many service companies, the decision to streamline workflows arises from a very concrete problem: customer context, sales status, and billing records reside in separate places. Before a team member can continue work or answer a client's question, they must retrace records across multiple locations. This situation drives operational admins and implementation leads to want to quickly unify everything into a single shared workspace like Orkesa.

However, right when the new workspace is ready to be set up, a classic confusion often halts the team's momentum: does all historical legacy data need to be migrated first by the workspace manager before the team can begin working?

When a workspace manager assumes that moving the entire historical database is part of day-one configuration, the setup process risks grinding to a halt. Time runs out digging through old archives whose formats may not be consistent, while the user list, role division, and team access permissions that should be operational immediately end up delayed. Therefore, distinguishing between initial data and a migration project is a crucial step for every implementation lead.


Understanding Orkesa's Role in Service Companies

Before mapping the boundaries of workspace manager duties, we need to view the context of using Orkesa in its entirety. Orkesa is designed for service companies and business teams that need to connect customers, sales, billing, and team work in a single interconnected workflow.

In day-to-day operations, Orkesa's capabilities cover several key areas that work side by side:

  • CRM and sales pipeline to monitor the progress of business opportunities.
  • Contact and customer records to keep client information from being scattered.
  • Customer conversations that require setting up the appropriate channels.
  • Billing and collections to connect work with payment follow-up.
  • Team and operational modules configured according to the package and the access permissions of each role.

Because each module, user count, capacity, and access level follows the package used by the company, initial setup requires structural discipline before large volumes of data are entered.


What Falls Under the Independent Tasks of a Workspace Manager?

In an Orkesa implementation, workspace managers have direct control over day-one operational foundations. This task does not require an exhaustive overhaul of old archives, but rather focuses on the readiness of the work structure so the team can begin running an orderly workflow.

1. Determining the Required Modules

The first step is ensuring which modules are relevant to the team's current needs according to the selected package. Will the team immediately connect customer contacts to the sales pipeline, and then pass them on to the billing and team work modules? Clarity regarding module selection early on helps workspace managers maintain setup focus.

2. Preparing Company Data and the User List

After the modules are determined, the workspace manager sets up the basic company profile and registers the users who will be involved. In a service company, these users typically include the sales team logging leads, the operations team executing work, and admins handling billing and collections.

3. Configuring Roles and Access Permissions

Not every team member requires access to all parts of the workspace. The workspace manager is responsible for assigning roles and setting access permissions according to the responsibilities of each team member and the package terms. Clear role configuration from the outset prevents overlapping authority once customer and billing data begin to flow.

4. Entering Initial Data

This is where the most important distinction lies. Initial data is basic data prepared and configured independently by the workspace manager so the system is ready for ongoing operations. Examples include the list of active customer contacts currently being handled, the basic structure of company offerings or services, and initial information needed by the team so they do not start from a blank slate.

Initial data is oriented toward current operational readiness. Workspace managers can organize this initial data independently because its structure follows the standard workflow of the modules already set up.


When Does a Requirement Fall Under the Scope of a Migration Project?

Unlike initial data, many service companies possess piles of historical records accumulated over years in various separated places. When a company wants to migrate those legacy archives while also customizing specific workflows, that requirement no longer falls under the realm of the workspace manager's daily independent setup.

Based on Orkesa's implementation guidelines, several items explicitly need to be discussed separately according to scope:

Two-column comparison diagram between self-managed initial data and migration projects discussed under separate scopes.

Separating initial data from migration projects protects admins from sorting unmapped historical archives when launching the new workspace.

  1. Legacy Data Migration: Migrating historical records from old recording systems, which requires data structure mapping, duplicate cleanup, or format adjustments to align with the relationships between contacts, sales, billing, and team work.
  2. Custom Workflows: Business process requirements of a service company that involve specific stages beyond the baseline setup.
  3. Conversation Channel Setup and Integrations: Connecting customer conversation channels or integrations with other systems requires appropriate technical setup.
  4. Training, Onboarding Assistance, and Implementation Fees: Implementation assistance needs, team training, additional support, and implementation fees are discussed with the Orkesa team in accordance with the agreed package and implementation scope.

Separating these four items from the workspace manager's independent tasks is not a form of delay, but rather a way to ensure the implementation maintains transparent timeline expectations, responsibilities, and implementation costs.


A Practical Decision-Making Guide for Operational Admins

When you sit down with operational leadership or team leads to plan the rollout of Orkesa, use the following three filtering questions to divide the work:

  • Is this data needed today so the team can record new work and manage access permissions? If yes, put it on the initial data list managed independently by the workspace manager.
  • Does this data consist of historical cross-period archives with varying structures that require custom mapping? If yes, do not force it into day one manually without planning; log it as a data migration requirement to be discussed separately with the Orkesa team.
  • Does the team require conversation channel connections, integrations, custom workflows, or structured training sessions? If yes, include it in the discussion agenda for implementation scope and onboarding assistance with the Orkesa team according to the package.

Three-step triage workflow diagram categorizing setup needs into initial data, migration projects, or integrations.

Using diagnostic filter questions helps implementation leads establish setup priorities without overwhelming day-one workspace configuration.

With this separation, workspace managers do not shoulder the technical burden of a migration project alone, while the business team gains certainty on when the new workspace can begin to be explored and configured.


Next Steps Before Getting Started

A smooth implementation always begins with an honest understanding of task boundaries. Workspace managers focus on establishing users, roles, access permissions, and initial data according to the modules and package, while data migration, custom workflows, integrations, training, and implementation fees are discussed openly by scope with the Orkesa team.

If you are mapping out your service company's operational requirements, you can review product explanations and view workflow previews with sample data and application CRM snapshots (using test data) via orkesa.id or the product information page at omindtech.id/products/orkesa. From there, you and your team can compile a list of what is ready to be configured independently today, and what needs further discussion according to your company's implementation scope.

Written by

Tim Editorial OmindTech

Practical perspectives on the decisions behind useful digital products.

Get to know OmindTech

Join the conversation.

Read reader responses, ask a question, or share your experience.

Back to the journal