Migrate your WORKetc data

Standard contact records with name, email, phone, address, and lifecycle information. We map Contacts directly to the destination CRM contact object, preserving all standard fields and owner assignments.

Company records serve as parent entities linked to multiple contacts. We preserve Company → Contact relationships and map company-level properties to the destination's account or company object.

WORKetc's Lead records capture early-stage prospects through to conversion. We export the full lead lifecycle including status, source, and converted-flagged records, mapping to destination Lead or Contact objects as appropriate.

Deals are linked to Companies and Contacts with stage, amount, and probability fields. We preserve the deal-to-company association and stage pipeline configuration during migration.

Projects use Project Types and Stages for weighted progress tracking, which differs from simple task-based progress. We export all project records, stages, milestones, and task hierarchies, but stage weightings may require manual reconfiguration in the destination.

Support tickets link to Customers, Companies, and Projects with status, priority, and conversation threads. We export ticket records with full conversation history and attachment references.

Invoice records include line items, totals, and payment status linked to Customers and Projects. We export invoice headers and line items; payment history and linked bank transaction records require separate handling.

WORKetc supports custom fields across multiple objects via their Custom Field system. Custom field definitions and values are exported, but field types (dropdown, text, date) require mapping to equivalent destination field types.

User records include name, email, role, and permission level. Contractor portal users are a separate user type with limited access. We export both but role structures rarely map 1:1 to destination permission models.

File management in WORKetc stores documents linked to records. We export file metadata and URL references; actual file binary export depends on the destination's document storage capabilities.

KB articles and categories are stored separately from CRM records. We export article content and category assignments; rich formatting and embedded media may require post-migration review.

WORKetc workflow rules and automation triggers are not exposed via API. These must be reconstructed manually in the destination platform using the exported workflow descriptions as reference.

Web forms capture lead and contact data. We export form definitions and field mappings; the actual hosted form URLs must be replaced with destination form endpoints post-migration.