Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

TimeSolv to iManage Cloud migration

TimeSolv is a cloud accounting and billing system, and iManage Cloud is a cloud document management system. Only files and their details have a place there, so this route carries the documents and archives the rest.

FromTimeSolvCloud
  1. Documents: Carried across
  2. Matters: Carried with mapping
  3. Templates: Carried with mapping
  4. Emails: Confirmed in the analysis
  5. Calendar: Confirmed in the analysis
  6. Custom fields: Confirmed in the analysis
ToiManage CloudCloud
  1. Contacts: Kept as a readable archive
  2. Notes: Kept as a readable archive
  3. Tasks: Kept as a readable archive
  4. Time and expenses: Kept as a readable archive
  5. Billing: Kept as a readable archive
  6. Trust money: Kept as a readable archive
  7. Intake: Kept as a readable archive
Readable archiveNo place in iManage Cloud
  • 1 carried
  • 2 mapped
  • 3 to confirm
  • 7 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from TimeSolv to iManage Cloud

Each row is a kind of record TimeSolv holds, whether iManage Cloud has a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, seven kinds have no place in iManage Cloud and are archived and three kinds are confirmed in the analysis.

Records in TimeSolv and their place in iManage Cloud
RecordIn TimeSolvIn iManage CloudWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters sit under clients. They carry billing settings more than case detail.Has a place in partAs a workspace with client and matter metadata. Parties and status stay in practice management.Carried with mapping
ContactsClients, other parties and referrersHeldClients and their contacts; leads are tracked in the CRM.No placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeldNested folders and tags inside TimeSolv, or a linked Dropbox or NetDocuments account.Has a placeEach needs a workspace and valid client and matter values; its class sets default security.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeLoaded as email documents into the workspace’s email folders.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeldNotes on clients and matters.No placeFile notes can be loaded as documents on the matter.Kept as a readable archive
CalendarAppointments, court dates and deadlinesTo be confirmedNo placeConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeldProject management with phases, tasks, estimates and budgets.No placeiManage Tracker is a separate product with its own set-up.Kept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeldThe core record, entered on the web, on mobile or offline through the TimeSync app.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldNo placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeldTrust balances can be applied to approved invoices.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a place in partA fixed number of custom profile fields, each a validated list.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partDocuments can be generated from client and matter data.Has a place in partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldCRM tracks prospects through intake statuses the firm defines.No placeKept as a readable archive

What the plans mean

Carried across
iManage Cloud has a place for this kind of record. It is loaded there and checked against TimeSolv.
Carried with mapping
iManage Cloud holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
Confirmed in the analysis
We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.
Kept as a readable archive
iManage Cloud has no place for it. It is exported in a format that opens without TimeSolv and handed to the firm as a read-only archive.

The table states what the two products hold and what NewLaw plans for. It is not a promise that every record moves: that is settled against your own data in the analysis.

This kind of move

Only the documents have a place here.

iManage Cloud is a document management system: it takes files and the details that describe them. Most of what TimeSolv holds is not files. Entries, balances, settings and lists have no place in a document store, and the table above is short for that reason. What can move is any document TimeSolv produced or stored: invoices as PDFs, signed agreements, attachments, exported reports. Each is filed under the client or matter it relates to.

The useful version of this job is often an archive. A firm retiring a system wants its records readable later without keeping the subscription or the old PC. The data is exported in open formats, spreadsheets and PDFs, and filed in iManage Cloud in a workspace set aside for it, with access limited to the people who need it. That gives the firm one place to look, under the same retention rules as the rest of its documents.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of TimeSolv depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to TimeSolv is kept running until the checks on iManage Cloud are finished.

Where the data is now

When the destination is a full practice management system, leaving TimeSolv is only part of the job. TimeSolv knows who the client is, what was billed and what is owed. It does not know the court, the other side or the next deadline. Its billing records move across, and the rest of each matter has to be gathered from wherever the firm has been keeping it.

  1. A matter is a billing file

    A TimeSolv matter holds rates, billing arrangements, budgets and balances. The parties, key dates and file notes that a practice management system expects are often in Outlook, a spreadsheet or the paper file. Part of the analysis is asking where those live, and whether they are loaded with the billing data or entered as matters are next worked on.

  2. Trust here, ledger elsewhere

    Client trust balances are kept in TimeSolv, while the bank accounts and general ledger are in QuickBooks, Xero or AccountEdge. The trust listing from TimeSolv and the trust bank balance from the accounting package are agreed with each other before cutover. Only then are opening balances entered in the new system.

  3. Phases, tasks and budgets

    Matter plans split a job into phases and tasks with estimated hours and fixed fees, and time is recorded against task codes. Many destinations bill by matter with no phase beneath it. Where budgets matter to clients, the firm decides whether phases become sub-matters, activity codes or a report run from the old data.

  4. Documents in three places

    Files may be in TimeSolv’s own folders, in a linked Dropbox account or in NetDocuments workspaces. A single firm can have all three if it changed approach over the years. Each store is listed with its volume, and documents already in NetDocuments or Dropbox can often stay where they are.

  5. Many years of time entries

    The product dates from 1999, so a long-standing firm can hold a very long run of billed time in it. Loading all of it into a new system is seldom worth the effort. A common split is open matters with full detail, closed matters as a summary, and the complete history kept in the read-only copy.

More about moving off TimeSolv

Where it is going

Administrators of an iManage Cloud library have API access only, so nothing is loaded by writing to a database. For cloudimanage.com, the newer of its two cloud platforms, iManage lists a supervised import API, sync APIs and a metadata loader. Nothing can be filed loose: every document goes into a workspace, with valid client and matter values. So the client and matter lists, the workspace template and the security groups are built first.

  1. Client and matter lists first

    Custom1 and custom2 are validated lists, with each matter a child of its client. A value that is not already in the list cannot be assigned to a document. The lists are loaded from the practice management system or the old document store before any content, closed matters with documents included.

  2. One workspace per matter

    Each matter gets a workspace generated from a template, so the template is designed before migration: its tabs, its folders, which are created up front and which on demand. Old folder trees rarely match it. The mapping says where each old folder lands and what happens to folders with no equivalent.

  3. Authors must be known users

    Author and operator are profile fields tied to users of the library. Documents written by people who left years ago need a decision: recreate those people as inactive users, or assign a placeholder author. That choice affects searching by author for as long as the firm uses the system.

  4. Hybrid security

    iManage calls its security model hybrid: where a user’s groups disagree, the most permissive access applies unless one of them is denied. On cloudimanage.com that model cannot be changed. Default security is normally set on the workspace and inherited below it. Restricted matters from the old system are loaded with their access list already in place.

  5. New numbers, original dates

    Documents are numbered by iManage as they are loaded, so old numbers do not carry over as numbers. On cloudimanage.com the file date setting is fixed to the file’s own date, and on imanage.work it can be set either way. Which dates display is checked on the trial load. The old reference can be carried in a custom field or the description where the firm wants to search by it.

More about moving into iManage Cloud

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in iManage Cloud on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what TimeSolv holds and how it is organised, then agree with you where each kind of record will sit in iManage Cloud. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into iManage Cloud and checked against TimeSolv: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in TimeSolv, a final pass over a weekend picks up what changed since the trial. TimeSolv is kept read only as the fall-back record.

Fixed price, agreed after the analysis. How NewLaw moves legal data

Start

Start this migration

Tell us what is in TimeSolv and roughly how much of it. The first step is the analysis, and the price is fixed once it is done.

Step 1 of 5

Step 1 of 5: Start with the route

Moving fromTimeSolv
Moving toiManage Cloud

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what TimeSolv holds

    What is in it, how its records link, and where each piece would sit in iManage Cloud. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. A fixed price in writing

    Set after the analysis, so it reflects what is in your data. You have it before any work starts.

Beyond the data

Setting up iManage Cloud

Loaded data is not yet a working system. This is what NewLaw sets up in iManage Cloud, beyond the migration, so that people can work in it from the first day.

Setting up iManage Cloud is mostly design work done before any user logs in: how many libraries, what a workspace looks like, which profile fields are captioned for what, and who can see which matters. Then come the links that keep it running day to day, such as creating a workspace when a matter is opened in the practice management system, and the add-ins on each desk.

Set-up decisions in iManage Cloud

  • Library structure and captions for client, matter and other fields
  • Workspace templates, folder names and Flexible Folders rules by practice area
  • Document classes, subclasses and the profile fields each one requires
  • Roles, groups, default security and walls for restricted matters
  • Workspace creation fed from the practice management system’s matter list
  • Work Desktop, Outlook email filing and Mobility on each device, with training

Questions

TimeSolv to iManage Cloud: what firms ask

We use TimeSolv with QuickBooks. Which one is the source for debtor balances?

TimeSolv, because that is where invoices are raised and payments applied by matter. QuickBooks holds the same totals at firm level once synced. The two are compared in the analysis. A difference usually points to a payment entered on one side only, and it is fixed before the trial load.

Will our unbilled time come across?

Unbilled time and expenses are the records most worth moving, since they are money not yet invoiced. They are loaded against the right matter and timekeeper with their original dates and narratives. Running a final billing cycle in TimeSolv first leaves less work in progress to carry.

We are on the Pro edition, not Legal. Is the move any different?

The records are the same kind: clients, the jobs under them, time, expenses and invoices. Extraction and checking are planned the same way. What changes is the destination, since a system built for law firms will expect matter types and trust rules that a consultancy or accounting practice never needed.

Do trust balances in TimeSolv have a place in iManage Cloud?

No. iManage Cloud does not keep trust ledgers. Trust records from TimeSolv are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.

What happens to records iManage Cloud has no place for?

On this route that is contacts, notes, tasks, time entries, billing records, trust ledgers and intake records. They are exported from TimeSolv in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

What has to be decided before TimeSolv data is loaded into iManage Cloud?

Matters and templates are carried with mapping, so each mapping is agreed with you first. Emails, calendar entries and custom fields are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

Where to start

Before and after the move.

Choosing the system comes before a migration. Setting it up and putting AI to work come after.

How we do itDiscovery to rollout, step by step

TimeSolv and iManage Cloud are the names and marks of their owners, used here only to identify the two systems.

Moving from TimeSolv to iManage Cloud?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.