Migrate your Striven data

Customers are core entities in Striven, importable via CSV/Excel with validation. They link to Sales Orders, Invoices, and Customer Portals. We migrate them 1:1, preserving contact details and associations.

Vendors map directly and feed into Purchase Orders and Bills. Striven's vendor records support type-level custom fields. We handle the import in the prerequisite phase before financial records.

Employee records are required prerequisites for accounting migration. They include time-tracking associations and role-based permissions. We migrate them in the foundational data phase.

Items represent products or services and are required prerequisites before creating Sales Orders or Purchase Orders. We map Items with their pricing, inventory quantities, and custom fields.

The GL Chart of Accounts is a hard prerequisite for any accounting migration. We sequence its import before open Invoices, Bills, or account balances. Account types and numbers map directly from the source.

Open Invoices require Customers, Items, and a populated Chart of Accounts to exist first. We migrate invoice headers and line items, but Convenience Fee and Discount configurations tied to payment methods require manual re-setup post-import.

Open Bills follow the same dependency chain as Invoices. We import Bill headers and line items, but tax codes and payment terms that differ between systems may require field-level mapping review.

Sales Orders link to Customers and Items. We migrate them with status preserved, but order types that drive custom field visibility may require type-level field mapping adjustments.

Purchase Orders require Vendors and Items to exist. We migrate PO headers and line items. Approval workflows attached to POs are not importable and must be rebuilt.

Projects exist as a module but their structure (phases, milestones, custom fields) varies. We map project headers and task hierarchies; custom field mapping per project type is required.

Tasks under Projects are migrated as child records with assignees preserved. Subtask hierarchies and dependency relationships require explicit mapping work.

Striven distinguishes global-level and type-level Custom Fields. Global fields appear on all records of a type; type-level fields are scoped to specific entity types. We must audit the custom field schema before migration to set the correct visibility and required-field behavior.

Striven Workflows are trigger/action automation rules tied to internal event listeners and email integrations. They cannot be exported or imported via the API or CSV tools. We do not migrate Workflows; customers must rebuild them in the destination system after cutover.

Fixed Assets in Striven include depreciation schedules and depreciation methods. We migrate asset records and current book values; the destination system's depreciation engine may differ and requires validation.

Document attachments are linked to entities. We migrate the association metadata but do not migrate the binary files themselves unless the customer's source system exposes a file export. Document metadata is preserved in the mapping file for manual re-attachment.