Migrate from Empire SUITE to HighLevel

Empire SUITE company records map directly to HighLevel Companies using a one-to-one field correspondence. Company name, address, phone number, and website URL fields transfer as-is without transformation logic. Multi-currency configuration flags and inter-company relationship indicators from Empire SUITE are preserved as custom fields on the HighLevel Company record for ongoing reference and reporting within the CRM environment.

Empire SUITE contact records representing client representatives, billing contacts, and project managers map directly to HighLevel Contacts. Core identity fields including name, email address, phone number, and role designation transfer without modification. The contact's associated company linkage is resolved during migration by matching the contact's company name against the migrated HighLevel Company record to establish proper foreign-key relationships.

Empire SUITE employees are not HighLevel users by default — they are source-system staff records. Employee number, department, and custom security role from Empire SUITE are stored as custom fields on the corresponding HighLevel Contact record so historical assignments are queryable in HighLevel.

Empire SUITE projects have no direct HighLevel equivalent. We create a Project Custom Object in HighLevel with fields for project name, status, budget, billing method (time-and-materials, fixed-price, scheduled), and revenue recognition type. Active projects may also create Opportunity records for CRM pipeline tracking.

Empire SUITE invoices do not map to any HighLevel native object. We export invoice data as CSV and import it into a custom Invoice Custom Object with invoice number, date, amount, status, and related company/contact lookups. Line-item detail is preserved as JSON in a long-text field or as a linked attachment.

Billable time entries from Empire SUITE are migrated into a Time Entry Custom Object linked to the Contact (employee) and Project Custom Object. Entry date, hours, billing rate, and project name are stored as separate fields so the data supports HighLevel workflow triggers based on time entry conditions.

Expense report records from Empire SUITE are migrated into a dedicated Expense Custom Object with separate fields for expense date, amount, category, reimbursement status, and associated project reference. This schema preserves the financial context of each expense while enabling HighLevel workflow conditions on individual expense attributes. Approval workflow flags and routing rules from Empire SUITE are not transferred — those business processes must be rebuilt as HighLevel workflow conditions or approval steps if required in the target system.

Empire SUITE department codes and inter-department transfer pricing rules are preserved as custom fields on Contact records and as Tags that can trigger HighLevel workflow routing. Department-to-department billing rates are stored as a lookup table Custom Object for reference by finance teams.

Empire SUITE's bidirectional QuickBooks sync for invoicing and bill payment has no HighLevel equivalent. We export the last sync state and advise rebuilding payment collection via HighLevel's Stripe integration. Historical QuickBooks linkage metadata is preserved as a custom field for audit purposes.

Documents attached to Empire SUITE invoices, projects, or contacts are downloaded and re-uploaded to HighLevel Files, linked to the corresponding Contact, Company, or Custom Object record. File size limits from HighLevel's upload API apply — large files may require zipping or external storage linking.