Skip to content

Migration

What is Migrated

Here's what we'll actually be migrating from ProfitSystem to BridalLive

  1. All tickets with a balance, or a pickup inventory item not picked up, or an outstanding purchase order. Old zero balance tickets won't be imported.

  2. We'll import the customers and events for those tickets. We won't import past customers or past events that are completed.

  3. We'll import future appointments along with appointment types.

  4. We'll also import your retail inventory with size charts and color charts. We'll also get your employee list, vendors, and categories. If you want us to only import items with QOH > 0, please let us know.

Cleaning up the data

Pickup inventory

For Pickup Inventory, you can run the Pickup Inventory report and use a Age date range of 1/1/2000-12/31/2025.

Un-issued Purchase Orders

For Un-issued Purchase Orders, you can go to the Purchase Orders report and select the option for Un-Issued PO Items, set the event date range to 1/1/2000-12/31/2026.

Un-Received Purchase Orders

For Un-Received Purchase Orders, you can go to the Purchase Orders report and select the option for Issued PO's, set the event date range to 1/1/2000-12/31/2026 and make "Include items received" unchecked.

Customers with Balances

Please run the Customers with Balances report for each store and delete any old, out of date tickets with balances.

You can delete old un-issued PO items and also un-received POs that have been issued, as well as old pickup inventory items. If you have a PO with no line items, you can simply delete it from the PO Maint form.

Delete any old, out of date tickets with balances.

If you want to delete old, unused styles/sizes/colors, please feel free to do that as well.

If you want us to only import items with QOH > 0, please let us know.

This video shows the process to clean up the data.

https://youtu.be/xf3j3dHEZl0

Migration Notes

  • The users, departments, vendors, and appointment types will only be migrated from ProfitSystem into BridalLive if they are missing in BridalLive. So, the first migration will typically create those items, and they won't be created on subsequent migrations.

  • If the username migrated from ProfitSystem is "Susan", it will show up in BridalLive as Susan-3535af43. This is because BridalLive requires usernames to be unique for all BridalLive stores. The -3535af43 added to the username means that user is specific to your store. Don’t change this or rename users until after the final migration.

  • When we import the users, we will generate new passwords. The existing passwords are often not complex enough for BridalLive. We’ll send over a list of usernames imported, along with the old and new passwords.

  • Categories in EveywhereBridal are migrated as Departments using the department code as the identifier.

  • Vendors are migrated using the vendor code as the identifier.

  • Appointment types are matched on the appointment type description compared to the appointment type in ProfitSystem.

With this in mind, you can use the migrated data for training or testing. You don't want to change the migrated user names, department codes, vendor codes or appointment types.

Technical Details of the Migration

  • The store style becomes the store item name in BridalLive.

  • The vendor style becomes the vendor item name in BridalLive.

  • The PO number shown in BridalLive is assigned by BridalLive and can't be changed. So, the PO number from ProfitSystem is stored in the PO notes.

  • The ticket number from ProfitSystem is stored in the transaction notes.

  • If a ticket uses styles that are not present in the inventory, the migration will automatically create that style in the inventory so it can be linked to the BridalLive transaction item.

  • When importing a ticket, the event and customer for the ticket will be imported. All the members of the event will be imported as well, but not their tickets if they don't have a balance, or a pickup item, or an item on special order.

  • Future prospects that have not become customers are imported. The bride and groom are imported as separate contacts.

  • Saved credit cards are not migrated

  • A primary contact is created for each School (prom) type event and all the members of the School event are added as members in BridalLive.

  • Prom/school type events are set up as Event Locations in BridalLive. If sales are registered for the prom/school, they'll show as registered in the Prom Registry in BridalLive.